We have application and trying to modularized the application . So keeping the separate module for google storage, pub sub and firestore. But the problem is that when we install the 3 modules, there will some issue with classnot found exception.
Related
I have two web applications deployed in Wildfly 18. Both of them use AWS ClOud HSM. They work perfectly fine while used alone. But as soon request is sent to both the applications I get the error "java.lang.UnsatisfiedLinkError: Native Library XXX.so already loaded in another classloader".
There is a jar file cloudhsm.jar which internally loads the .so library. I have to use the following statement to register a new security provider
Security.addProvider(new com.cavium.provider.CaviumProvider());
The same statement is used in both the applications
I have tried configuring the provider in java.security file also. But that also doesnt work.
How should I configure the provider to be used in both the applciations.
I had deployed the app last on friday and it got deployed successfully.But since, today morning the deployment is not happening at all.It is checking for conflicting process and failing.
I'm doing this from the webide and i'm not able to check what are the conflicting process and how to resolve it.
WebIDE lacks the ability to do proper investigation on deploying apps to SAP Cloud Foundry.
The best way to do this is to install the Cloud Foundry Multi-apps plugin (see this tutorial). This will allow you to use the local terminal to control the deployment (or alternatively use SAP Business Application Studio which already has the commands built in).
Then use the command cf mta-ops to get the list of ongoing operations and cf dmol <operation_id> to download the logs for that operation. cf deploy can be used to abort/retry operations.
We have an older application based on the AppEngine SDK (now deprecated) and the superseded Cloud Datastore.
In the process of migrating to Google Cloud SDK we also decided to move from JPA/Datanucleus to Objectify.
Given that the Cloud Datastore will be automatically upgraded to Cloud Firestore in Datastore mode sometime in the future, we decided to test our application as described at the bottom of this page:
https://cloud.google.com/datastore/docs/upgrade-to-firestore#testing_an_existing_application
1) Create a new project. In this project, create a Cloud Firestore in Datastore mode database.
2) Using the managed export service, export some of your application's data to Cloud Storage.
3) Using the managed import service, import your application's data to your new project.
4) Copy app logic you want to test to the new project or simulate app behaviour against the new project.
That's what we did and after some issues we could make a portion of our application run fine with the new datastore in a separate test project.
Now to the actual issue...
We wanted to test if the updated application could also run with the superseded Cloud Datastore, so we won't have to worry when the automatic upgrade occurs (as our app will be already ready).
So we deployed it as a new version of the existing AppEngine project (v2-dot-.....): unfortunately running the new version throws a permission error as soon as the app tries to read the datastore:
com.google.cloud.datastore.DatastoreException: Missing or insufficient permissions
So the questions are:
- could this be related to the Cloud Datastore not being upgraded to Cloud Firestore in Datastore mode for our project yet?
- is there anything we can do (add specific permissions maybe) to make it work anyway?
Our concern is that we need to have the new version of the app deployed before July 2020 (that's when the older AppEngine SDK will stop working), and we are worried that the automatic upgrade of the datastore will occur later.
Thank you for your help.
Turned out our project doesn't have the PROJECT_ID#appspot.gserviceaccount.com member in IAM.
It has a pletora of other members (for example: PROJECT_NUMBER-compute#developer.gserviceaccount.com, PROJECT_NUMBER#cloudservices.gserviceaccount.com, service-PROJECT_NUMBER#compute-system.iam.gserviceaccount.com, etc) which I guess are legacy members used in previous versions of Google App Engine.
Adding PROJECT_ID#appspot.gserviceaccount.com with the role Editor fixed the issue: now the new version can be deployed to the old projects and it works fine even if the datastore has not yet been converted to Cloud Firestore in Datastore Mode.
I just ran into this issue and spent way too much time troubleshooting it. Nine times out of ten if you're running into this issue it's because the default App Engine service account doesn't have permission to edit Cloud Datastore. The default App Engine service account is used by default if you're doing a simple gcloud app deploy and nothing else fancy. I solved the problem by giving the default App Engine service account the roles/datastore.owner role with the following:
gcloud projects add-iam-policy-binding PROJECT_ID \
--member="serviceAccount:PROJECT_ID#appspot.gserviceaccount.com" \
--role="roles/datastore.owner"
Hi I have been trying to test this two components on bluemix since last 2 days, I need to now if both of then has some robust library on NodeJs, because I have been trying the ones I found at npm and event the one featured at Bluemix Cloud Storage as Nodejs SDK and I have unsuccessfull on even connect to Cloud Storage and Hive, I feel completly lost. I hope some one here could at least give e a lead ....
Thanks in advance
I find out that the bluemix platform had an issue when creating the cloud storage within the Biginsights cluster manager, so I created the Object Storage first and then link it to the Biginsights service and now the NodeJs SDK from bluemix works just fine, thanks anyway.
While creating an Application in Bluemix trial account, I encountered an error BXNUI0005E: The "" application could not be added.
I tried creating the application using the Boiler plate "IoT For Electronics Starter" and it continuously failed with the above message.
Even tried from a different environment with a different App name, the results remained same.
After checking ahead found that trial accounts in Bluemix can only create 4 services.
The IoT for Electronics starter creates the below three different services
Internet of Things platform
IoT for electronics
Mobile Access client
I already had a simple node.js app associated to two different services.
As the boiler plate was unable to create these new services, the new application failed with error BXNUI0005E.
Once the other services were removed, the application created fine.