I've migrated from 4.0 to 4.3, I am getting validation issues on the data source. Anyone seen that before? I assume it is a liquibase issue where the hash is different for the change.
notary_1 | [ERROR] 20:52:25+0000 [main] internal.NodeStartupLogging. - Could not create the DataSource: Validation Failed:
notary_1 | 1 change sets check sum
notary_1 | migration/node-services.changelog-init.xml::add-new-persistence-table::R3.Corda was: 8:cb3302a80bf346270e0d8f3509c64a9b but is now: 8:d1dd927506a41884e2d451b3d4e3c6b0
notary_1 | : Could not create the DataSource: Validation Failed:
notary_1 | 1 change sets check sum
notary_1 | migration/node-services.changelog-init.xml::add-new-persistence-table::R3.Corda was: 8:cb3302a80bf346270e0d8f3509c64a9b but is now: 8:d1dd927506a41884e2d451b3d4e3c6b0
notary_1 | [errorCode=1sgw0t1, moreInformationAt=https://errors.corda.net/OS/4.3-RC01/1sgw0t1]
For anyone who finds this in the future, it looks like 1174 solved his issue by upgrading the version of docker he was using.
Link to the github issue here: https://github.com/corda/corda/issues/6016
Related
Export metrics to dynatrace using Micrometer.io
gradle dependency 'io.micrometer:micrometer-registry-dynatrace:latest.release'
version - (1.1.3)
Causing Exception -> Error {"error":{"code":400,"message":"Could not map JSON at 'series[33].dataPoints' near line 1 column 4071"}} {}
metrics:
export:
dynatrace:
device-id: xxxxx
uri: https://xxxx/e/xxxxx/api/v1/entity/infrastructure/custom
api-token: xxxxxxx
enabled: true
technology-type: java
step: 1m
I have found the issue with latest micrometer release(1.1.3). While forming Json data from the metrics its throwing exception i went one minor version(1.1.1) older it worked fine. Should open the bug for this.
Error
{"error":{"code":400,"message":"Could not map JSON at 'series[33].dataPoints' near line 1 column 4071"}} {}
We are getting this error while its trying to convert the CPU metrics to json
I'm using flyway-ant 4.0.
I could see sql stmts and update count , while using -X option in command line mode.
How to get "'updated row count'" in ant debug mode?
Based on this issue from their repo, code supposed to work and is part of Flyway 4.0.
You will get affected rows counts in the log file, the contents would be alike:
2016-01-24 22:40:23.417 DEBUG [ main] o.f.core.internal.dbsupport.SqlScript : Executing SQL: update employees set i=5 where name='test1'
2016-01-24 22:40:25.145 DEBUG [ main] o.f.c.internal.dbsupport.JdbcTemplate : Update Count: 1
2016-01-24 22:40:25.145 DEBUG [ main] o.f.core.internal.dbsupport.SqlScript : Executing SQL: delete from employees where i=2
2016-01-24 22:40:25.797 DEBUG [ main] o.f.c.internal.dbsupport.JdbcTemplate : Update Count: 1
Note, that Flyway logs the update count as soon as at least one row was affected.
Please, reference the issue provided for more information, or please, provide more details on what you are doing and what you are getting in result.
2016-02-01 15:02:19,152 | ERROR | FelixStartLevel | BootFeaturesInstaller | 20 - org.apache.karaf.features.core - 3.0.5 | Error installing boot features
java.lang.Exception: Could not start bundle mvn:com.fasterxml.jackson.module/jackson-module-scala_2.11/2.6.2 in feature(s) de-support-0.0.0, swagger-2.11-6.1.0: Unresolved constraint in bundle com.fasterxml.jackson.module.jackson.module.scala [274]: Unable to resolve 274.0: missing requirement [274.0] osgi.wiring.package; (&(osgi.wiring.package=com.fasterxml.jackson.module.paranamer)(version>=2.6.0)(!(version>=3.0.0)))
I am getting above exception, while starting karaf even after providing
<bundle>mvn:com.fasterxml.jackson.module/jackson-module-scala_2.11/2.6.2</bundle>
in features.xml file.
You're getting this message because one of your bundles imports the package com.fasterxml.jackson.module.paranamer but you have not included a bundle in your feature which exports this package. A search for com.fasterxml.jackson.module.paranamer brings up the pom for Jackson Paranamer which shows that it exports the package that you need (look at the osgi.export property). So add:
<bundle>mvn:com.fasterxml.jackson.module/jackson-module-paranamer/2.6.2</bundle>
to your feature in your features.xml
Two of us made a migration script in different GIT branches. Now, I've pulled origin development branch, and I've corrected GIT merge issues, and renamed my migration script to be the last. So, the new initialization of DB and migration of DB from version of develop branch would be fine.
However, I've got a lot of data in my local testing DB, so I've manually applied new migration scripts that I've pulled in GIT. However, I can't make flyway think, that everything is okay.
So, How can I fake migrations?
When I try to migrate, I get following error:
[ERROR] Failed to execute goal org.flywaydb:flyway-maven-plugin:3.2.1:migrate (default-cli) on project db: org.flywaydb.core.api.FlywayException: Validate failed. Migration Description mismatch for migration 1.118
[ERROR] -> Applied to database : AAA
[ERROR] -> Resolved locally : BBB
[ERROR] -> [Help 1]
You will have to manually update Flyway's metadata table (called schema_version by default)
We are in the Process of migrating jboss 4.3 to jBoss 5.1 We are using EJB 1.1 in the current systems.We fixed a lot of issues to make the server up and finally we are not able to see the Home Page due to Db connection.We are getting Below error:
[org.hibernate.connection.DatasourceConnectionProvider] (main) Using datasource: java:/oradbds
2012-10-11 18:27:59,493 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] (main) Throwable while attempting to get a new connection: null
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: ORA-01017: invalid username/password; logon denied
)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:225)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:195)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:639).
I Guess error may be due to Db connection related Jar like ojdbc14.jar which is incompatible for jboss5.1.
Let me know if you need some more info . Please provide a solution.
first of all: which JDK do you use? IMHO you should use JDK 6 and ojdbc6.jar. Why do you want to use your old EJB 1.1 based app?
It seems that the DB-credentials are not correct ...
Best Regards,
Sascha