I need to migrate from WSO2 API Manager 1.4.0 to 1.8.0. I executed all instructions from 'wso2am_1.8.0/dbscripts' (how it was possible)
migration 1.4.0 to 1.5.0
migration 1.5.0 to 1.6.0
migration 1.6.0 to 1.7.0
migration 1.7.0 to 1.8.0
But the very last ant script 'swagger-doc-migration' (from 1.7.0 to 1.8.0) failed and showed exception like this:
2015-01-20 16:32:47,142] ERROR - RPCMessageReceiver Resource does not exist at path /_system/governance/apimgt/applicationdata/api-docs/SOME_API-1.0-xxxxxxxx-AT-xxxxxxxxx.com/1.2
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:212)
at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117)
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)...
It seems scripts 1.6.0 to 1.7.0 doesn't migrate swagger docs completely because 'swagger-doc-migration' script (1.7.0->1.8.0) can't find path /_system/governance/apimgt/applicationdata/api-docs/SOME_API-1.0-xxxxxxxx-AT-xxxxxxxxx.com/1.2.
So, how can I make "swagger-doc-migration" from "migration 1.7.0 to 1.8.0" work?
There was an issue in swagger resource migration script and it was fixed in the latest patch.
Please use the scripts from following location : https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/apimgt/1.8.0/modules/distribution/resources/migration-1.6.0_to_1.7.0/
have the same issue with migration. I try to migrate 1.6.0 -> 1.7.0 -> 1.8.0 and swagger-doc-migration fails for the step 1.7.0 -> 1.8.0. But if I setup 1.7.0 and then migrate to 1.8.0 swagger-doc-migration succeed.
Seems like swagger-doc-migration from 1.6.0 -> 1.7.0 fails to migrate api docs correctly.
Note: I've tried https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/apimgt/1.8.0/modules/distribution/resources/migration-1.6.0_to_1.7.0/ from Abimaran Kugathasan's answer.
Related
Hey i have an django application which is working fine locally but its not working when it is hosted on a web showing below error
django.core.exceptions.ImproperlyConfigured: Error loading pyodbc module: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/site/wwwroot/antenv/lib/python3.7/site-packages/pyodbc.cpython-37m-x86_64-linux-gnu.so)
Did i miss anything at the time of hosting?
Assuming you got this issue during deployment via DevOps pipeline, you could specify an exact version of python in the UsePythonVersion (including minor version) task.
Supported python versions, you could check the software of the agent image:
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software
Also, you could try the solution in the following case, by adding deadsnakes repo, installing 3.7 and symlink python to python3.7:
https://github.com/actions/virtual-environments/issues/2634#issuecomment-775808754
So i am trying to load the WSO2 gateway from my local machine running the new 3.0.0-m6 version downloaded from their website.
I have run everything as described in the quickstart guide, and i get the following error on start up.
Could not load Logmanager "org.ballerinalang.launcher.BLogManager"
java.lang.ClassNotFoundException: org.ballerinalang.launcher.BLogManager
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.util.logging.LogManager$1.run(LogManager.java:195)
at java.util.logging.LogManager$1.run(LogManager.java:181)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.<clinit>(LogManager.java:181)
at java.util.logging.Logger.demandLogger(Logger.java:448)
at java.util.logging.Logger.getLogger(Logger.java:502)
at com.sun.jmx.remote.util.ClassLogger.<init>(ClassLogger.java:55)
at sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstrap.java:846)
at sun.management.Agent.startLocalManagementAgent(Agent.java:138)
at sun.management.Agent.startAgent(Agent.java:260)
at sun.management.Agent.startAgent(Agent.java:447)
ballerina: unknown command 'start'
Run 'ballerina help' for usage.
ActiveMQ is running
WSO2 Server is running
WSO2 Identity manager is running
WSO2 API Manager is running
I am starting the gateway from the root folder as explained in the start up guide.
Are you running this in Windows? The version 3.0.0-m6 is based on Ballerina v0.89 and in this version of Ballerina, there's a bug in the bin/ballerina.batfile. As you can see, it's looking for a class named org.ballerinalang.launcher.BLogManager and fails. This class was moved to another package and now, its fully qualified name is org.ballerinalang.logging.BLogManager. In the ballerina.bat script, change the property (towards the end of the file) -Djava.util.logging.manager="org.ballerinalang.launcher.BLogManager" to -Djava.util.logging.manager="org.ballerinalang.logging.BLogManager" and it should solve your problem.
We are facing some problem regarding jar dependencies and jar clashes while working with AWS java SDK 1.10.105.
We are seeing that in the AWS SDK httpClient 4.5.2 version is used, while we are using 4.5.0 version in our project. It is also coming for httpcore 4.4.4 jar also. What will be the solution? We are not even sure that whether we are facing this error for the jar clashes, we think AWS SDK is independent of all external jars. Please help.
The error we are facing:
java.lang.ClassNotFoundException: org.apache.http.impl.client.HttpClients
After using same jar version of AWS SDK, now we are facing this error.We are using jodaTime 2.8.1(Same of SDK)
java.lang.NoClassDefFoundError: Could not initialize class com.amazonaws.auth.internal.AWS4SignerUtils
java.lang.NoSuchMethodError: org.joda.time.format.DateTimeFormatter.withZoneUTC()Lorg/joda/time/format/DateTimeFormatter;
Please check the dependencies:
-
com.fasterxml.jackson
jackson-modified
2.5.4
-
org.apache.commons
commons-csv
1.1
-
commons-logging
commons-logging
1.1.1
-
com.googlecode.json-simple
json-simple
1.1.1
-
log4j
log4j
1.2.16
compile
-
com.fasterxml.jackson.core
jackson-databind
2.6.6
-
com.fasterxml.jackson.core
jackson-databind
2.6.6
After upgrade to ES 1.3.2 I'm facing the following issues:
1) On startup got error:
[2014-08-26 11:10:20,285][ERROR][bootstrap ] {1.3.2}: Initialization Failed ...
1) NoSuchMethodError[org.elasticsearch.discovery.zen.ZenDiscovery.(Lorg/elasticsearch/common/settings/Settings;Lorg/elasticsearch/cluster/ClusterName;Lorg/elasticsearch/threadpool/ThreadPool;Lorg/elasticsearch/transport/TransportService;Lorg/elasticsearch/cluster/ClusterService;Lorg/elasticsearch/node/settings/NodeSettingsService;Lorg/elasticsearch/cluster/node/DiscoveryNodeService;Lorg/elasticsearch/discovery/zen/ping/ZenPingService;Lorg/elasticsearch/Version;)V]2) IllegalStateException[This is a proxy used to support circular references involving constructors. The object we're proxying is not constructed yet. Please wait until after injection has completed to use this object.]
2) when I attempt to upgrade the cloud-aws plugin to version 2.3.0 (compatible with ES 1.3) I get:
`Exception in thread "main" java.lang.UnsupportedClassVersionError: org/elasticsearch/plugins/PluginManager : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:643)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
Could not find the main class: org.elasticsearch.plugins.PluginManager. Program will exit.`
Java version is:
java version "1.7.0_45"
OpenJDK Runtime Environment (amzn-2.4.3.2.32.amzn1-x86_64 u45-b15)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)
Same issue faced with ES versions 1.3.1 and 1.3.0
Surprisingly ES v1.3.2 works fine on java version "1.7.0_25"
The issue is resolved. The issue comes when compilation happens with a different java version and at runtime a different version of java is found. When we looked at the Java -version, it was pointing at 1.7 where as java_home was pointing to 1.6. We also checked command "java which" which was pointing to 1.7. When we checked the script of elastic search, it gives precedence to "JAVA_HOME" and then looks for "java which". Installed JDK 1.7(earlier only JRE 1.7) was installed, uninstalled 1.6 using command
yum install java-1.7.0-openjdk
yum remove install openjdk-6-jre
yum remove java-1.6.0-openjdk
and the issue is resolved..!! :)
I am trying to use lein-ring plugin. After having installed the plugin any attempt to issue a a lein ring command yields a
java.lang.ClassNotFoundException: javax.xml.stream.XMLInputFactory
I am using leiningen 1.7.1 and java version 1.5.
The XML streaming API wasn't included in the standard JRE until Java 6. You've got a few options:
Upgrade to Java 6+
Download the JSR173 API here
Add [javax.xml/jsr173 "1.0"] to your Leiningen dependencies