Menu
▾
▴
Re: [SignServer-develop] JDBC problem
|
From: Jordi B. U. <jb...@ne...> - 2016-05-19 07:26:58
|
Hi Marcus,
I did, and I retried it again. I see this in the log:
01:50:57,817 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "signserverds")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"org.wildfly.data-source.signserverds is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]",
"jboss.driver-demander.java:/SignServerDS is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]"
]}
01:50:57,823 INFO [org.jboss.as.controller] (management-handler-thread - 1) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.data-source.reference-factory.signserverds (missing) dependents: [service jboss.naming.context.java.SignServerDS]
service jboss.data-source-config.signserverds (missing) dependents: [service org.wildfly.data-source.signserverds]
service jboss.jdbc-driver.org_mariadb_jdbc_Driver (missing) dependents: [service jboss.driver-demander.java:/SignServerDS, service org.wildfly.data-source.signserverds]
WFLYCTL0186: Services which failed to start: service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
When it tries to deploy the application, server start I also see these errors:
01:37:44,049 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly-10.0.0.Final/standalone/deployments
01:37:44,054 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "signserver.ear" (runtime-name: "signserver.ear")
01:37:44,074 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoSuchMethodError: org.apache.xml.security.utils.I18n.init(Ljava/util/ResourceBundle;)V
at org.apache.wss4j.common.crypto.WSProviderConfig.initializeResourceBundles(WSProviderConfig.java:199)
at org.apache.wss4j.common.crypto.WSProviderConfig.init(WSProviderConfig.java:90)
at org.jboss.wsf.stack.cxf.config.CXFStackConfig.<init>(CXFStackConfigFactory.java:62)
at org.jboss.wsf.stack.cxf.config.CXFStackConfigFactory.getStackConfig(CXFStackConfigFactory.java:47)
at org.jboss.ws.common.management.AbstractServerConfig.setStackConfig(AbstractServerConfig.java:361)
at org.jboss.ws.common.management.AbstractServerConfig.create(AbstractServerConfig.java:339)
at org.jboss.as.webservices.config.ServerConfigImpl.create(ServerConfigImpl.java:70)
at org.jboss.as.webservices.service.ServerConfigService.start(ServerConfigService.java:70)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
... 3 more
01:37:44,396 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
01:37:44,393 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
01:37:44,393 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
01:37:44,402 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
01:37:48,789 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xercesImpl.jar in /content/signserver.ear/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
01:37:48,791 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xml-apis.jar in /content/signserver.ear/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
01:37:48,791 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry serializer.jar in /content/signserver.ear/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
01:37:48,795 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry xml-apis.jar in /content/signserver.ear/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
01:37:48,811 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb-SignServerWS.jar")
01:37:48,811 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb-AdminWS.jar")
01:37:48,812 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "signserver.war")
01:37:48,812 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb-ValidationWS.jar")
01:37:48,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "cesecore-ejb-6.1.1.jar")
01:37:48,814 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-war-Healthcheck.war")
01:37:48,815 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-war-Doc.war")
01:37:48,813 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb-ClientWS.jar")
01:37:48,829 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: "SignServer-ejb.jar")
01:37:48,859 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.ws.config" => "org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
Caused by: java.lang.NoSuchMethodError: org.apache.xml.security.utils.I18n.init(Ljava/util/ResourceBundle;)V"}}
01:37:48,933 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "signserver.ear" (runtime-name : "signserver.ear")
01:37:48,936 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.ws.config: org.jboss.msc.service.StartException in service jboss.ws.config: Failed to start service
01:37:49,114 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management
01:37:49,115 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990
01:37:49,115 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started (with errors) in 11404ms - Started 287 of 589 services (11 services failed or missing dependencies, 376 services are lazy, passive or on-demand)
It looks like there is some problem with jar references. All the ones that were copied and referenced during installation process are giving errors.
This is what I did:
cp -P /opt/signserver/lib/ext/xmlsec-1.5.8.jar /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/apache/santuario/xmlsec/main/
vi /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/apache/santuario/xmlsec/main/module.xml
<resource-root path="xmlsec-1.5.8.jar"/>
cp /opt/signserver/lib/ext/xalan-2.7.2.jar /opt/signserver/lib/ext/serializer-2.7.2.jar /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/apache/xalan/main/
vi /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/apache/xalan/main/module.xml
<resource-root path="serializer-2.7.2.jar"/>
<resource-root path="xalan-2.7.2.jar"/>
wget https://downloads.mariadb.com/enterprise/698m-9ksy/connectors/java/connector-java-1.4.4/mariadb-java-client-1.4.4.jar
mkdir -p /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/mariadb/main/
cp -P /opt/mariadb-java-client-1.4.4.jar .
vi module.xml
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.mariadb">
<resources>
<resource-root path="mariadb-java-client-1.4.4.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
</dependencies>
</module>
Thanks,
Jordi
De: Marcus Lundblad [mailto:mar...@pr...]
Enviado el: jueves, 19 de mayo de 2016 9:18
Para: Jordi Blasi Uribarri; sig...@li...
Asunto: Re: [SignServer-develop] JDBC problem
ons 2016-05-18 klockan 15:08 +0000 skrev Jordi Blasi Uribarri:
Hi,
Hi Jordi!
I am trying to install sign server on a freshly installed fedora box. I have followed the install procedure described on the web as close as possible but I am finding problems to deploy the signserver on the app server.
I have installed it on wildfly 10 and mariaDB.
What I am seeing is that there is a problem with the jdbc driver configuration. On the server.xml log I can see this:
2016-05-19 04:26:29,475 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "signserverds")
]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"org.wildfly.data-source.signserverds is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]",
"jboss.driver-demander.java:/SignServerDS is missing [jboss.jdbc-driver.org_mariadb_jdbc_Driver]"
]}
2016-05-19 04:26:29,482 INFO [org.jboss.as.controller] (management-handler-thread - 3) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.data-source-config.signserverds (missing) dependents: [service org.wildfly.data-source.signserverds]
service jboss.jdbc-driver.org_mariadb_jdbc_Driver (missing) dependents: [service jboss.driver-demander.java:/SignServerDS, service org.wildfly.data-source.signserverds]
I have created the module.xml file and moved the jar file.
mkdir -p /opt/wildfly-10.0.0.Final/modules/system/layers/base/org/mariadb/main/
cp -P /opt/mariadb-java-client-1.4.4.jar .
vi module.xml
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.mariadb">
<resources>
<resource-root path="mariadb-java-client-1.4.4.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
</dependencies>
</module>
I also have run on the jboss-cli the following commands:
/subsystem=datasources/jdbc-driver=com.mysql.jdbc.Driver:add(driver-name=com.mysql.jdbc.Driver,driver-module-name=com.mysql,driver-xa-datasource-class-name=com.mysql.jdbc.jdbc.jdbc2.optional.MysqlXADataSource)
:reload
data-source add --name=signserverds --driver-name="org.mariadb.jdbc.Driver" --connection-url="jdbc:mysql://127.0.0.1:3306/signserver" --jndi-name="java:/SignServerDS" --use-ccm=true --driver-class="org.mariadb.jdbc.Driver" --user-name="xxx" --password="xxx" --validate-on-match=true --background-validation=false --prepared-statements-cache-size=50 --share-prepared-statements=true --min-pool-size=5 --max-pool-size=150 --pool-prefill=true --transaction-isolation=TRANSACTION_READ_COMMITTED --check-valid-connection-sql="select 1;"
Did you do a :reload (or restart the application server) after issuing the "data-source add" command?
//Marcus
In the Web interface of wildfly I have not seen any reference to this connection.
What I am doing wrong?
Thanks in advance.
Jordi
________________________________
Jordi Blasi Uribarri
Área I+D+i
jb...@ne...<mailto:jb...@ne...>
Oficina Bilbao
[http://www.nextel.es/wp-content/uploads/Firma_Nextel_2015.png]
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
SignServer-develop mailing list
Sig...@li...<mailto:Sig...@li...>
https://lists.sourceforge.net/lists/listinfo/signserver-develop
|
