Hi I have build my plugin which fails to start with error as
Failed to parse configuration class
[com.q.plugins.config.MyPluginJavaConfig]; nested exception is java.io.FileNotFoundException: OSGi resource[classpath:com/atlassian/plugins/osgi/javaconfig/configs/beans/ModuleFactoryBean.class|bnd.id=187|bnd.sym=com.q.plugins.jira_dc_plugin] cannot be resolved to URL because it does not exist
[INFO] [talledLocalContainer] OSGi resource[classpath:com/atlassian/plugins/osgi/javaconfig/configs/beans/ModuleFactoryBean.class|bnd.id=187|bnd.sym=com.q.plugins.jira_dc_plugin] cannot be resolved to URL because it does not exist
My Setup
<jira.version>8.20.2</jira.version>
<platform.version>5.2.0</platform.version>
<refapp.version>5.3.0</refapp.version>
<amps.version>8.1.2</amps.version>
<plugin.testrunner.version>2.0.2</plugin.testrunner.version>
<osgi.javaconfig.version>0.5.0</osgi.javaconfig.version>
<spring.version>5.0.10.RELEASE</spring.version>
with OpenJDK 1.8 (java version "1.8.0_281")
My findings
Using atlasian SDK maven and repository
tried on clean start up using atlas- commands
same error when manually deployed to running Jira instance in docker
Followed - https://bitbucket.org/atlassian_tutorial/atlassian-plugins-osgi-javaconfig-demo/src/master/
Found similar question here but has no proper pointers to answer.
Thanks in advance.
Related
We built an app with 0.18.0 quarkus version and we have following application.properties:
quarkus.datasource.url=${POSTGRES_DATABASE_URL}
quarkus.datasource.driver=org.postgresql.Driver
quarkus.hibernate-orm.database.generation=update
quarkus.hibernate-orm.dialect=org.hibernate.dialect.PostgreSQL10Dialect
quarkus.http.port=${PORT:8080}
%dev.quarkus.datasource.url=jdbc:h2:mem:db
%dev.quarkus.datasource.driver=org.h2.Driver
%dev.quarkus.hibernate-orm.dialect=org.hibernate.dialect.H2Dialect
When I tried upgrading to 0.20.0 (or any version higher, including 1.0.0.Final) I get following error when building with maven:
[ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:0.20.0:build (default) on project thats-my-spot: Failed to build a runnable JAR: Failed to build a runner jar: Failed to augment application classes: For input string: "${PORT:8080}" -> [Help 1]
Why?
${PORT:8080} just means that it should take either the PORT environment variable if available or use 8080 if not.
I looked at potential issues, changes in semantics but found only one bug that might touch defaults in properties: https://github.com/quarkusio/quarkus/issues/3030 But the description and solution is different, so I don't think that it broke my app.
Can you try with 1.2.1.Final? We had some issues with handling defaults of environment properties at some point but it has been solved for quite a while.
If you can reproduce it with the latest, please open an issue in our tracker with a reproducer and we will have a look.
This error occur when the use SecureRandom() inside of application. ibmjceprovider.jar is build with project and it deployed successfully. (ibmjceprovider.jar already in WEB-INF/lib)
the oracle weblogic server not loading the ibmjceprovider.jar
java version 1.6
java.lang.RuntimeException: java.security.NoSuchAlgorithmException: class configured for SecureRandom(provider: IBMJCE)cannot be found.
at java.security.SecureRandom.getDefaultPRNG(SecureRandom.java:206)
at java.security.SecureRandom.<init>(SecureRandom.java:155)
As i think web logic server not use my project /libs
How i handle this in project environment
this issue resolve after restarting web-logic server.
15:28:38.716 [qtp1588771273-32] WARN o.e.jetty.servlet.ServletHandler - /tp/gremlin/execute
java.lang.IllegalArgumentException: Could not resolve dependency of type:javax.transaction.TransactionManager
at org.neo4j.graphdb.DependencyResolver$Adapter$1.select(DependencyResolver.java:87) ~[neo4j-kernel-2.2.9.jar:2.2.9]
at org.neo4j.kernel.extension.KernelExtensions.resolveDependency(KernelExtensions.java:112) ~[neo4j-kernel-2.2.9.jar:2.2.9]
This is from Neo4j 2.x (the Gremlin plug-in). The package, when built and deployed as instructed at https://github.com/thinkaurelius/neo4j-gremlin-plugin, does contain the jar-file which describes this class, and Maven did download it and did install it there. But, when the server attempts to load and execute the extension, nothing is resolved.
Why?
I updated a project that was using struts 2.2.3.1 to the 2.3.1.2 in the pom.xml file. After running maven it picked up the jar from the repo and all that and built the package just fine. But, when I run the webapp I am getting this error:
2012-04-26 13:42:06,300 ERROR org.apache.struts2.dispatcher.Dispatcher.error:38 - Dispatcher initialization faile Unable to load configuration. - bean - jar:file:/Library/Tomcat/apache-tomcat-6.0.35/webapps/idmadmin/WEB-INF/lib/struts2-core-2.3.1.2.jar!/struts-default.xml:29:72.....
I was thinking that maybe the old one was still stuck in the classpath but I don't see it.
Using Maven to build my project under windows works fine, but when I build it under Linux I get a NoSuchMethodError regarding one of the spring libs.
I am guessing it is something to do with class loader differences cross-platform and somewhere in my dependencies and I may have the same class twice but windows is loading one while linux loads the other?
Has anyone come across this problem before, or have any advice on how I can debug this error further?
nested exception is java.lang.NoSuchMethodError:
org.springframework.aop.config.AopNamespaceUtils.registerAutoProxyCreatorIfNecessary(Lorg/springframework/beans/factory/xml/ParserContext;Lorg/w3c/dom/Element;)V:
java.lang.NoSuchMethodError:
org.springframework.aop.config.AopNamespaceUtils.registerAutoProxyCreatorIfNecessary(Lorg/springframework/beans/factory/xml/ParserContext;Lorg/w3c/dom/Element;)V
at org.springframework.transaction.config.AnnotationDrivenBeanDefinitionParser$AopAutoProxyConf
Stack Trace Pastie
POM.xml Pastie
Your spring dependencies have too many different versions:
org.springframework:spring-beans:jar:2.5.6:compile
org.springframework:spring-aop:jar:2.0.8:compile
org.springframework:spring-jms:jar:3.0.5.RELEASE:compile
Make all spring dependencies have the same version (preferably 3.0.5.RELEASE)