I have followed below procedure for publishing statistics. I have setup in desktop with standalone configurations and no clustering, database is installed.
https://docs.wso2.com/display/AM1100/Publishing+API+Runtime+Statistics+Using+REST+Client
I'm getting below error in the apim logs and not able to see statistcis.
ERROR - usage:jag java.lang.IndexOutOfBoundsException:
Index: 0, Size: 0
ERROR - usage:jag java.lang.IndexOutOfBoundsException:
Index: 0, Size: 0
error i see in statistics page
i have searched old stackoverflow tickets but couldn't find the correct solution. can anybody please help on this
This issue is already reported and you can find the relevant jira in [1]. Please note that WSO2 API Manager 1.10 only supports WSO2 DAS 3.0.X versions. Based on the jira this issue is already fixed in WSO2 DAS 3.1.0. I am not sure why you are getting this in DAS 3.1.0. Anyway, you cannot use DAS 3.1.0 with APIM 1.10 due to other complexities.
The root cause for this issue when you start the server in the daemon mode the Spark variables are not loaded and Spark cluster does not function properly. To avoid this you can start the DAS servers in nohup mode as follows.
nohup ./wso2server.sh &
Related
Backend works correct. Problem is only on frontend with additionally Login Form on custom login site.
I getting 503 error after trying login by "Login Panel". It doesn't matter right or wrong login data.
I turned off the redirect on backend but I still get this same error with log below:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1064: An exception occurred while executing a query: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ')))) AND (fe_users.deleted = 0)' at line 1 | Doctrine\DBAL\Exception\SyntaxErrorException thrown in file /public/my_site_name/vendor/doctrine/dbal/src/Driver/API/MySQL/ExceptionConverter.php in line 86. Requested URL: https://my-domain-name.pl/login?tx_felogin_login%5Baction%5D=login&tx_felogin_login%5Bcontroller%5D=Login&cHash=9238b3d3ba4dbeb2c75d778a5cd1f17b
I know it is probably cause by third party extension like bootstrap (bk2k). But I don't believe I need to rewrite manual syntax in my mariadb. it's ridiculous.
Im checked requirements for this version of TYPO3. And my requirements are ok. Im checked my database (MariaDB) by mysqlcheck and all is ok. Checked version of MariaDB and its ok.
Im beginner in TYPO3 so please be understanding.
root#database-deb:/home/marlon# mysql -V
mysql Ver 15.1 Distrib 10.7.3-MariaDB, for debian-linux-gnu (x86_64) using readline EditLine wrapper
I looked in wrong places. On TYPO3 site you can see:
System requirements PHP 8.1 MariaDB 10.3+ / MySQL 8.0+ / PostgreSQL
10.0+ / SQLite 3.8.3+
but if you see details:
Requirements on TYPO3 site
MariaDB >= 10.3.0 <= 10.6.99 is not the same MariaDB 10.3+
I guess, due to incompatible version of mariadb...
A few hours later... I create new one VM with older MariaDB.
root#mariadb-10-6:/home/marlon# mysql -V
mysql Ver 15.1 Distrib 10.6.11-MariaDB, for debian-linux-gnu (x86_64) using readline EditLine wrapper
Nothing changed. Still same error.
I've recently been developing an app, and noticed a few days ago I updated R to 4.1.2. After making some changes to the app, I used the Publish button to deploy to shinyapps.io. The deployment console threw the following error and failed:
Error: Unhandled Exception: Child Task 1045191965 failed: Error building image: R version 4.1.2 currently unavailable
Execution halted
Now, I've deployed many times previously, and this was the first deployment since the update to R. I haven't included any code because my app.R is over 1500 lines and it really didn't seem to be related to any of thee changes I made. I was wondering if anyone could help me figure out whether this error is referring to my system or the server I am deploying to. I expect I may have to roll back to the pre-update snapshot and try again, but I'd like to avoid doing that if the problem lies somewhere else.
Rstudio is Version 1.4.1103
Operating system:
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
Thanks in advance!
After checking with shinapps.io support, they informed me their server has not been updated to 4.1.2 and to downgrade until they are able to make the upgrade. They were not able to provide an ETA on that. Thanks to the support staff there!
I have connected my Android application with firebase-database by putting this dependency (kapt 'com.google.firebase:firebase-database:16.0.1:15.0.0') but after that I am getting errors like the one mentioned in title also when I synchronized the project I am getting different errors like: Connection time out, Failed to resolved build listener.
Enabling/Disabling offline work and setting proxy in gradle.properties file doesn't work for me.
Also you guys have seen that I used 'kapt' in dependency as it is necessary to use, without it I am getting error "failed to resolve 15.0.0". Removing 15.0.0 doesn't work for me.
Error
Cause:org.jetbrains.plugins.gradle.tooling.util.ModuleComponentIdentifierImpl.getModuleIdentifier()Lorg/gradle/api/artifacts/ModuleIdentifier;ing
I am using Android Studio 3.2 and sadly I can't update this version.
Gradle version: 5.1.1 and
Plugin version: 3.4.0
My current version of Artifactory Pro 6.5.2. I can upgrade incrementally from 6.5.2 to 6.5.9 to 6.0.0. If I try to upgrade beyond 6.0.0, I receive a 404 error when attempting to access Artifactory.
HTTP Status 404 – Not Found
Type Status Report
Message /artifactory/webapp/
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Apache Tomcat/8.5.32
I see the following errors in /var/opt/jfrog/artifactory/logs/catalina/catalina.out
Failed to ensure db table 'master_key_status' exists
Error creating bean with name 'accessJdbcHelperImpl': Invocation of init method failed; nested exception is java.lang.IllegalStateException: Could not initialize database: Not supported
org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/access]]
The database I'm using is MySQL
mysql Ver 15.1 Distrib 5.5.60-MariaDB, for Linux (x86_64) using readline 5.1
Has any encountered a similar issue when upgrading Artficatory Pro?
Thanks
Just marking down the answer.
The issue was with the JDBC driver version of the Maria DB.
One more update done by you was adding the timezone value.
I am trying to run Corda nodes on macOS El Capitan with JDK 1.8.0_60 by following the instructions here: https://docs.corda.net/getting-set-up.html.
I am getting the following error:
CAPSULE EXCEPTION: Could not parse version: -9.0.1 while processing
system property java.home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre
java.lang.IllegalArgumentException: Could not parse version: -9.0.1
How can I fix this?
Although its older thread, i encountered it today and stumbled upon this page and thought to share my findings.
Actually Oracle changed the numbering style from java9 (like 9.0.1) and it seems you have it installed. You will have to point to jdk 1.8.x so make it work until capsule is updated to work with java9.
Running Corda nodes requires a JDK version greater than JDK 8u121. If you upgrade your JDK, this error will disappear.