Problem/Issue: I am trying to read data from splunk in a spring application(splunk java sdk) using spring integration. I received an error "Server chose unsupported or disabled protocol: SSLv3" while deploying the code in a TCserver. This worked fine in local environment/builds/servers.
The current version I have for spring-integration-splunk is 1.1.0.M2. I understand that old splunk version(1.1.0) has this issue and it's fixed in latest versions. But, when I try to upgrade the spring-integration-splunk dependency with latest version(1.1.0.RELEASE), The dependency pulls splunk 1.3.0 jar which is not available in Maven. And I got this error
"Failed to read artifact descriptor for com.splunk:splunk:jar:1.3.0"
Is there an alternative or solution to this problem. (Either by adding a fix in the code or by changing the dependencies)?
Related
I have created a war file of birt-runtime-4.12.0-20221128 as in the instructions for POJO deploymnet. I am running weblogic 14.1.1 and I can successfully deploy it. Weblogic is running Java Version: 1.8.0_331. Is this sufficient?
When I browse to the following path: http://localhost:7001/birt/index.jsp
I get the following error: Error 404--Not Found
Any suggestions on how to make it work?
I tried building it many times and many ways and this is the only way that it successfully deployed but doesnt work.
Sorry, but BIRT 4.12 needs Java >= 11.
Any contract I successfully build that has a dependency to elrond-wasm 0.19.1 fails to deploy
Is there any known issue regarding this or am I the only one facing this?
Trying to build on the older 0.18.2 works but a lot of the contract code has to be changed in order to achieve a build.
Most examples I have tried to build and deploy from the Elrond Github Rust examples repository fail when deployed with the same error.
Although the one found at https://github.com/ElrondNetwork/ping-pong-smart-contract that is using these dependencies:
[dependencies.elrond-wasm]
version = "0.18.2"
features = ["derive"]
[dependencies.elrond-wasm-node]
version = "0.18.2"
optional = true
[dev-dependencies.elrond-wasm-debug]
version = "0.18.2"
works great. Build and deploy work flawlessly.
If you are trying to deploy on the devnet this will fail because it hasn't been updated to 0.19 yet, so you still have to use 0.18.x there.
Also note that 0.19.1 wasn't officially released yet, so that will most likely fail on mainnet and devnet as well.
So either way the solution as you have already described is to downgrade your elrond-wasm versions to 0.19.0 or 0.18.2, depending on the net on which you want to deploy.
I have a java webapp on heroku. It runs perfectly on the cloud. But when run locally it appears to use a stale resource. My jar is called nymmbl1-1.0.jar. I have 100% verified the resource is correct in target\nymmbl1-1.0.jar and ~.m2\repository\com\nymmbl\nymmbl1\1.0\nymmbl1-1.0.jar. When run locally the resource is old. It's as though heroku local is using some cached version.
Has anyone ever seen anything like this?
The out-of-date resource is a local read-only SQlite database. When running "heroku local" the database is accessed but the content returned is different than the actual database content in the current jar. The content returned is from an older version of the SQLite DB that is not in the current JAR.
As I said, this problem is not observed when run on the cloud.
My guess is that "heroku local" is doing something I don't expect. Can you suggest what may be the problem or how to debug this?
This problem disappeared upon updating some maven artifacts. For the record here's what I changed:
org.springframework.boot spring-boot-starter-parent, changed from
1.5.2.RELEASE to 1.5.7.RELEASE
webjars-bootstrap.version, from 3.3.6 to 3.3.7-1
webjars-jquery-ui.version 1.1.14 => 1.12.1
webjars-jquery.version 2.2.4 => 3.2.1
thymeleaf.version 3.2.5.RELEASE => 3.0.7.RELEASE
I am trying to link my Neo4j db with Elasticsearch using the recommended approach on the Neo4j website, with this GitHub repository https://github.com/neo4j-contrib/neo4j-elasticsearch
I have done all the steps that they say to do, but when I run it in terminal I get this error (everything works normally except that nothing is getting pushed to Elasticsearch):
Failed to load `org.apache.commons.logging.impl.AvalonLogger` from
plugin jar
`/Users/tkralj/Documents/Neo4j/default.graphdb/plugins/neo4j-
elasticsearch-3.1.4.jar`: org/apache/avalon/framework/logger/Logger
2017-07-13 20:21:46.911+0000 WARN [o.n.k.i.p.Procedures]
Failed to load `org.apache.commons.logging.impl.Log4JLogger` from
plugin jar
`/Users/tkralj/Documents/Neo4j/default.graphdb/plugins/neo4j-
elasticsearch-3.1.4.jar`: org/apache/log4j/Category
2017-07-13 20:21:46.911+0000 WARN [o.n.k.i.p.Procedures]
Failed to
load `org.apache.commons.logging.impl.LogKitLogger` from plugin jar
`/Users/tkralj/Documents/Neo4j/default.graphdb/plugins/neo4j-
elasticsearch-3.1.4.jar`: org/apache/log/Logger
I am running Neo4j 3.1.5, while this plugin was created for 3.1.4 and I think that may be the issue; however, there is no plugin made for 3.1.5, and I cannot find a way to download the older version of Neo4j.
Looks like old question but still answering for future googlers.
I was facing the same problem with 3.1.x version . For me it's working fine with version 3.2
I have recently updated my STS from 2.5.2 to 2.6. Since then, each grails project shows an error in the conf/spring/resources.groovy file reading: Description Resource Path Location Type
Internal compiler error: java.lang.VerifyError: (class: org/codehaus/jdt/groovy/internal/compiler/ast/JDTClassNode, method: initialize signature: ()V) Bad access to protected data at org.codehaus.jdt.groovy.internal.compiler.ast.JDTResolver.createClassNode(JDTResolver.java:461) resources.groovy /GrailsProject/grails-app/conf/spring line 0 Java Problem
The resources.groovy file is as good as empty (in default state), and if I delete it, the error is shown on the DataSource.groovy, so the file itself seems not to be the cause.The used groovy compiler version is 1.7.3.I have made a clean STS 2.6 install, installed the groovy and grails plugins and got the same error.What could be the problem? And is there a solution to this not resulting in downgrading to 2.5.2 again? Thank you
Take a look at your preferences Groovy -> Compiler. Are you by any chance accidentally using Groovy 1.6?
EDIT
That didn't solve the problem, but as described in http://forum.springframework.org/showthread.php?p=357361, upgrade to the latest dev build of Groovy-Eclipse as well as Grails Tooling and that should work.