Menu
▾
▴
signserver-develop
|
From: Marcin F. <mar...@en...> - 2015-05-26 21:29:08
|
Hello, I try to run signserver but each time, the implementation ends like this: 22:57:14,581 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /signserver/AdminWSService 23:13:47,327 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [1000 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment. 23:13:47,328 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "signserver.ear" was rolled back with failure message Operation cancelled 23:13:47,381 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ClientWS.jar".ClientWS 23:13:47,386 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/ClientWSService,endpoint=ClientWS 23:13:47,387 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-SignServerWS.jar".SignSer verWS 23:13:47,389 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/SignServerWSService,endpoint=SignServerWS 23:13:47,409 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ValidationWS.jar".Validat ionWS 23:13:47,409 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/ValidationWSService,endpoint=ValidationWS 23:13:47,412 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-AdminWS.jar".AdminWS 23:13:47,413 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/AdminWSService,endpoint=AdminWS 23:13:47,542 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.port-component-link Regards, Martin |
|
From: Marcin F. <mar...@en...> - 2015-05-26 21:27:33
|
Hello, I try to run signserver but each time, the implementation ends like this: 22:57:14,581 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /signserver/AdminWSService 23:13:47,327 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [1000 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment. 23:13:47,328 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "signserver.ear" was rolled back with failure message Operation cancelled 23:13:47,381 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ClientWS.jar".ClientWS 23:13:47,386 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/ClientWSService,endpoint=ClientWS 23:13:47,387 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-SignServerWS.jar".SignSer verWS 23:13:47,389 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/SignServerWSService,endpoint=SignServerWS 23:13:47,409 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ValidationWS.jar".Validat ionWS 23:13:47,409 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/ValidationWSService,endpoint=ValidationWS 23:13:47,412 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-AdminWS.jar".AdminWS 23:13:47,413 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/AdminWSService,endpoint=AdminWS 23:13:47,542 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.port-component-link Regards, Martin |
|
From: Marcin F. <mar...@en...> - 2015-05-28 09:26:03
|
Hello, I installed signserver a few times accordance with http://signserver.org/manual/installguide.html and each time the deployment is stopped at the same time . Linux dist.: Centos 6.6 Jboss: 7.1 finall Signserver: 3.6.2 Hello, I try to run signserver but each time, the implementation ends like this: 22:57:14,581 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /signserver/AdminWSService 23:13:47,327 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [1000 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment. 23:13:47,328 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "signserver.ear" was rolled back with failure message Operation cancelled 23:13:47,381 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ClientWS.jar".ClientWS 23:13:47,386 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/ClientWSService,endpoint=ClientWS 23:13:47,387 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-SignServerWS.jar".SignServerWS 23:13:47,389 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/SignServerWSService,endpoint=SignServerWS 23:13:47,409 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ValidationWS.jar".ValidationWS 23:13:47,409 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/ValidationWSService,endpoint=ValidationWS 23:13:47,412 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.endpoint."signserver.ear"."SignServer-ejb-AdminWS.jar".AdminWS 23:13:47,413 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-1) remove: jboss.ws:context=signserver/AdminWSService,endpoint=AdminWS 23:13:47,542 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015540: Stopping service jboss.ws.port-component-link Regards, Martin ------------------------------------------------------------------------------ _______________________________________________ SignServer-develop mailing list Sig...@li... https://lists.sourceforge.net/lists/listinfo/signserver-develop |
|
From: Markus K. <ma...@pr...> - 2015-05-28 09:37:27
|
On 05/28/2015 11:29 AM, Marcin Fabiańczyk wrote: > Hello, > > I installed signserver a few times accordance with > http://signserver.org/manual/installguide.html and each time the > deployment is stopped at the same time. > > Linux dist.: Centos 6.6 > Jboss: 7.1 finall > Signserver: 3.6.2 > > ------------------------------------------------------------------------ > > Hello, > > > I try to run signserver but each time, the implementation ends like this: > > > > 22:57:14,581 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: > Registering web context: /signserver/AdminWSService > > 23:13:47,327 ERROR [org.jboss.as.server.deployment.scanner] > (DeploymentScanner-threads - 2) JBAS015052: Did not receive a response > to the deployment operation within the allowed timeout period [1000 > seconds]. Check the server configuration file and the server logs to > find more about the status of the deployment. > > 23:13:47,328 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) > JBAS015870: Deploy of deployment "signserver.ear" was rolled back with > failure message Operation cancelled > > 23:13:47,381 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ClientWS.jar".ClientWS > > 23:13:47,386 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/ClientWSService,endpoint=ClientWS > > 23:13:47,387 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-SignServerWS.jar".SignServerWS > > 23:13:47,389 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/SignServerWSService,endpoint=SignServerWS > > 23:13:47,409 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ValidationWS.jar".ValidationWS > > 23:13:47,409 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/ValidationWSService,endpoint=ValidationWS > > 23:13:47,412 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-AdminWS.jar".AdminWS > > 23:13:47,413 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/AdminWSService,endpoint=AdminWS > > 23:13:47,542 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service jboss.ws.port-component-link > > Hi Martin, The timeout and failure to start JBoss indicates a problem with the configuration of JBoss. One cause for a situation like this is if the data source or driver has not been properly registered in JBoss. In that case there is usually possible to find a small error message about it somewhere in the server.log. Regards, Markus PrimeKey PrimeKey Solutions offers a commercial EJBCA & SignServer support subscription and training. Please see www.primekey.se or contact in...@pr... for more information. https://www.primekey.se/Services/Support/ https://www.primekey.se/Services/Training/ |
|
From: Marcin F. <mar...@en...> - 2015-05-28 09:44:27
|
Hello Markus, I changed the timeout to 1200 seconds and it did not resolve the issue. I used mysql-connector-java-5.1.17 ----- Oryginalna wiadomość ----- Od: "Markus Kilås" <ma...@pr...> Do: sig...@li... Wysłane: czwartek, 28 maj 2015 11:37:15 Temat: Re: [SignServer-develop] Problem with the implementation of Signserver. On 05/28/2015 11:29 AM, Marcin Fabiańczyk wrote: > Hello, > > I installed signserver a few times accordance with > http://signserver.org/manual/installguide.html and each time the > deployment is stopped at the same time. > > Linux dist.: Centos 6.6 > Jboss: 7.1 finall > Signserver: 3.6.2 > > ------------------------------------------------------------------------ > > Hello, > > > I try to run signserver but each time, the implementation ends like this: > > > > 22:57:14,581 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: > Registering web context: /signserver/AdminWSService > > 23:13:47,327 ERROR [org.jboss.as.server.deployment.scanner] > (DeploymentScanner-threads - 2) JBAS015052: Did not receive a response > to the deployment operation within the allowed timeout period [1000 > seconds]. Check the server configuration file and the server logs to > find more about the status of the deployment. > > 23:13:47,328 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) > JBAS015870: Deploy of deployment "signserver.ear" was rolled back with > failure message Operation cancelled > > 23:13:47,381 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ClientWS.jar".ClientWS > > 23:13:47,386 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/ClientWSService,endpoint=ClientWS > > 23:13:47,387 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-SignServerWS.jar".SignServerWS > > 23:13:47,389 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/SignServerWSService,endpoint=SignServerWS > > 23:13:47,409 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ValidationWS.jar".ValidationWS > > 23:13:47,409 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/ValidationWSService,endpoint=ValidationWS > > 23:13:47,412 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-AdminWS.jar".AdminWS > > 23:13:47,413 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/AdminWSService,endpoint=AdminWS > > 23:13:47,542 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service jboss.ws.port-component-link > > Hi Martin, The timeout and failure to start JBoss indicates a problem with the configuration of JBoss. One cause for a situation like this is if the data source or driver has not been properly registered in JBoss. In that case there is usually possible to find a small error message about it somewhere in the server.log. Regards, Markus PrimeKey PrimeKey Solutions offers a commercial EJBCA & SignServer support subscription and training. Please see www.primekey.se or contact in...@pr... for more information. https://www.primekey.se/Services/Support/ https://www.primekey.se/Services/Training/ ------------------------------------------------------------------------------ _______________________________________________ SignServer-develop mailing list Sig...@li... https://lists.sourceforge.net/lists/listinfo/signserver-develop |
|
From: Marcin F. <mar...@en...> - 2015-05-28 10:41:20
|
Hello, Change java connector to 5.1.30 solved the problem Thanks, Martin ----- Oryginalna wiadomość ----- Od: "Marcin Fabiańczyk" <mar...@en...> Do: "Markus Kilås" <ma...@pr...> DW: sig...@li... Wysłane: czwartek, 28 maj 2015 11:48:17 Temat: Re: [SignServer-develop] Problem with the implementation of Signserver. Hello Markus, I changed the timeout to 1200 seconds and it did not resolve the issue. I used mysql-connector-java-5.1.17 ----- Oryginalna wiadomość ----- Od: "Markus Kilås" <ma...@pr...> Do: sig...@li... Wysłane: czwartek, 28 maj 2015 11:37:15 Temat: Re: [SignServer-develop] Problem with the implementation of Signserver. On 05/28/2015 11:29 AM, Marcin Fabiańczyk wrote: > Hello, > > I installed signserver a few times accordance with > http://signserver.org/manual/installguide.html and each time the > deployment is stopped at the same time. > > Linux dist.: Centos 6.6 > Jboss: 7.1 finall > Signserver: 3.6.2 > > ------------------------------------------------------------------------ > > Hello, > > > I try to run signserver but each time, the implementation ends like this: > > > > 22:57:14,581 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: > Registering web context: /signserver/AdminWSService > > 23:13:47,327 ERROR [org.jboss.as.server.deployment.scanner] > (DeploymentScanner-threads - 2) JBAS015052: Did not receive a response > to the deployment operation within the allowed timeout period [1000 > seconds]. Check the server configuration file and the server logs to > find more about the status of the deployment. > > 23:13:47,328 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) > JBAS015870: Deploy of deployment "signserver.ear" was rolled back with > failure message Operation cancelled > > 23:13:47,381 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ClientWS.jar".ClientWS > > 23:13:47,386 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/ClientWSService,endpoint=ClientWS > > 23:13:47,387 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-SignServerWS.jar".SignServerWS > > 23:13:47,389 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/SignServerWSService,endpoint=SignServerWS > > 23:13:47,409 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ValidationWS.jar".ValidationWS > > 23:13:47,409 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/ValidationWSService,endpoint=ValidationWS > > 23:13:47,412 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service > jboss.ws.endpoint."signserver.ear"."SignServer-ejb-AdminWS.jar".AdminWS > > 23:13:47,413 INFO > [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service > thread 1-1) remove: > jboss.ws:context=signserver/AdminWSService,endpoint=AdminWS > > 23:13:47,542 INFO [org.jboss.as.webservices] (MSC service thread 1-1) > JBAS015540: Stopping service jboss.ws.port-component-link > > Hi Martin, The timeout and failure to start JBoss indicates a problem with the configuration of JBoss. One cause for a situation like this is if the data source or driver has not been properly registered in JBoss. In that case there is usually possible to find a small error message about it somewhere in the server.log. Regards, Markus PrimeKey PrimeKey Solutions offers a commercial EJBCA & SignServer support subscription and training. Please see www.primekey.se or contact in...@pr... for more information. https://www.primekey.se/Services/Support/ https://www.primekey.se/Services/Training/ ------------------------------------------------------------------------------ _______________________________________________ SignServer-develop mailing list Sig...@li... https://lists.sourceforge.net/lists/listinfo/signserver-develop ------------------------------------------------------------------------------ _______________________________________________ SignServer-develop mailing list Sig...@li... https://lists.sourceforge.net/lists/listinfo/signserver-develop |
|
From: Markus K. <ma...@pr...> - 2015-05-28 18:45:34
|
On 28 May 2015 12:45:08 CEST, "Marcin Fabiańczyk" <mar...@en...> wrote: > >Hello, > >Change java connector to 5.1.30 solved the problem > >Thanks, >Martin > >----- Oryginalna wiadomość ----- >Od: "Marcin Fabiańczyk" <mar...@en...> >Do: "Markus Kilås" <ma...@pr...> >DW: sig...@li... >Wysłane: czwartek, 28 maj 2015 11:48:17 >Temat: Re: [SignServer-develop] Problem with the >implementation of Signserver. > >Hello Markus, > >I changed the timeout to 1200 seconds and it did not resolve the issue. >I used mysql-connector-java-5.1.17 > > > >----- Oryginalna wiadomość ----- >Od: "Markus Kilås" <ma...@pr...> >Do: sig...@li... >Wysłane: czwartek, 28 maj 2015 11:37:15 >Temat: Re: [SignServer-develop] Problem with the implementation >of Signserver. > >On 05/28/2015 11:29 AM, Marcin Fabiańczyk wrote: >> Hello, >> >> I installed signserver a few times accordance with >> http://signserver.org/manual/installguide.html and each time the >> deployment is stopped at the same time. >> >> Linux dist.: Centos 6.6 >> Jboss: 7.1 finall >> Signserver: 3.6.2 >> >> >------------------------------------------------------------------------ >> >> Hello, >> >> >> I try to run signserver but each time, the implementation ends like >this: >> >> >> >> 22:57:14,581 INFO [org.jboss.web] (MSC service thread 1-1) >JBAS018210: >> Registering web context: /signserver/AdminWSService >> >> 23:13:47,327 ERROR [org.jboss.as.server.deployment.scanner] >> (DeploymentScanner-threads - 2) JBAS015052: Did not receive a >response >> to the deployment operation within the allowed timeout period [1000 >> seconds]. Check the server configuration file and the server logs to >> find more about the status of the deployment. >> >> 23:13:47,328 INFO [org.jboss.as.server] (DeploymentScanner-threads - >1) >> JBAS015870: Deploy of deployment "signserver.ear" was rolled back >with >> failure message Operation cancelled >> >> 23:13:47,381 INFO [org.jboss.as.webservices] (MSC service thread >1-1) >> JBAS015540: Stopping service >> >jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ClientWS.jar".ClientWS >> >> 23:13:47,386 INFO >> [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service >> thread 1-1) remove: >> jboss.ws:context=signserver/ClientWSService,endpoint=ClientWS >> >> 23:13:47,387 INFO [org.jboss.as.webservices] (MSC service thread >1-1) >> JBAS015540: Stopping service >> >jboss.ws.endpoint."signserver.ear"."SignServer-ejb-SignServerWS.jar".SignServerWS >> >> 23:13:47,389 INFO >> [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service >> thread 1-1) remove: >> jboss.ws:context=signserver/SignServerWSService,endpoint=SignServerWS >> >> 23:13:47,409 INFO [org.jboss.as.webservices] (MSC service thread >1-1) >> JBAS015540: Stopping service >> >jboss.ws.endpoint."signserver.ear"."SignServer-ejb-ValidationWS.jar".ValidationWS >> >> 23:13:47,409 INFO >> [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service >> thread 1-1) remove: >> jboss.ws:context=signserver/ValidationWSService,endpoint=ValidationWS >> >> 23:13:47,412 INFO [org.jboss.as.webservices] (MSC service thread >1-1) >> JBAS015540: Stopping service >> >jboss.ws.endpoint."signserver.ear"."SignServer-ejb-AdminWS.jar".AdminWS >> >> 23:13:47,413 INFO >> [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service >> thread 1-1) remove: >> jboss.ws:context=signserver/AdminWSService,endpoint=AdminWS >> >> 23:13:47,542 INFO [org.jboss.as.webservices] (MSC service thread >1-1) >> JBAS015540: Stopping service jboss.ws.port-component-link >> >> > >Hi Martin, > >The timeout and failure to start JBoss indicates a problem with the >configuration of JBoss. > >One cause for a situation like this is if the data source or driver has >not been properly registered in JBoss. In that case there is usually >possible to find a small error message about it somewhere in the >server.log. > > > >Regards, >Markus >PrimeKey > >PrimeKey Solutions offers a commercial EJBCA & SignServer support >subscription and training. Please see www.primekey.se or contact >in...@pr... for more information. >https://www.primekey.se/Services/Support/ >https://www.primekey.se/Services/Training/ > > > >------------------------------------------------------------------------------ >_______________________________________________ >SignServer-develop mailing list >Sig...@li... >https://lists.sourceforge.net/lists/listinfo/signserver-develop > >------------------------------------------------------------------------------ >_______________________________________________ >SignServer-develop mailing list >Sig...@li... >https://lists.sourceforge.net/lists/listinfo/signserver-develop Great, Thanks for letting us know. BR, Markus -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. |
Thanks for helping keep SourceForge clean.
X