We have two mule projects in different version 3.0 and 3.7. We want deploy these two projects in single VM (Windows). But I can able to run only one mule runtime not both in single VM(Windows).
Please advise!
Yes, you could run multiple esb instances on a single computer. we have experience doing that one 3.4 version and 3.7 version.
Related
Since the update before last to AWS Toolkit, when running Visual Studio 2022 with AWS Toolkit installed and enabled, the entire PC grinds to crawl.
Specifically, physical memory use shoots up to 99%, there's a huge amount of continuous disk activity and CPU use rises to around 50%. This renders the entire system completely unusable (think, two minute delay between clicking and something happening). Oddly, nothing appears in the process list in Task Manager that accounts for either the levels of memory or CPU use. It feels like a monumental memory leak but really I've no idea what's going on.
I've tried completely uninstalling and reinstalling VS and uninstalling, deleting the AWS Toolkit folder in "Users...etc." and reinstalling the Toolkit. Everything is fully up-to-date.
As I say, this has happened since the update before last. It's strange that it isn't mentioned anywhere that I can find on the internet and it's difficult to imagine that such a serious issue would only happen to me.
So, has this happened to anyone else and does anyone have a fix? I wanted to raise a support case on AWS Console but I only have a basic account so am unable to do so.
This issue has been resolved (see https://github.com/aws/aws-toolkit-visual-studio/issues/314#issuecomment-1401060605 for more details).
The system in question is running Windows 7. At some point .NET 7 was installed onto it (possibly as a result of a Visual Studio update). .NET 7 does not support Windows 7, and dotnet publish commands started to produce internal errors, and is taking a long time to complete. The AWS Toolkit's Lambda publishing features are built on top of the dotnet CLI commands, which is how the degradation was noticed.
This can be mitigated by installing an older version of .NET (like .NET 6) and telling the dotnet tooling to use a specific version of .NET instead of the latest detected version.
From https://learn.microsoft.com/en-us/dotnet/core/tools/global-json:
The global.json file allows you to define which .NET SDK version is used when you run .NET CLI commands. Selecting the .NET SDK version is independent from specifying the runtime version a project targets. The .NET SDK version indicates which version of the .NET CLI is used.
Add a global.json file to the same folder as your project or solution with the contents shown below, referring to the .NET SDK version you want to use (the example below uses 6.0.300)
{
"sdk": {
"version": "6.0.300"
}
}
How to approach schema/data migration when upgrading to Couchbase 7.x from Couchbase 5.x ?
By schema I mean indexes, that must be created before any document inserted,
so have to
create new collection,
define indexes,
move documents from older collection except for ref docs.
For SQL there is database migration tool like Flyway/Liquibase
P.S. I am not quite good with Couchbase.
Is there any other general practices to keep db/data in good shape in update in environments pipeline DEV->UAT->PREPROD->PROD ?
There's a tool called CouchVersion.
CouchVersion is a Java framework which helps you to manage changes in
your Couchbase and synchronize them with your application. The concept
is very similar to other db migration tools such as Liquibase or
Flyway but without using XML/JSON/YML files.
You don't have to use any 3rd party tool for this! Couchbase offers everything out of the box.
First some background knowledge, couchbase is designed to work in a cluster that consists of at least two nodes, ideally in production you should use at least 3 nodes. Given that, if you want to upgrade couchbase you can do that live on the cluster! You simply remove a node from the cluster, upgrade the node, then joint it back into the cluster, that's it! The cluster continues to work while you remove and upgrade it node by node. Nothing is lost, no downtime, your clients will not even feel it.
Second, you can upgrade a couchbase cluster node only from one major version to the next (+1) major version, so in your case you have to upgrade all nodes from major version 5.x to 6.x then when all nodes in the cluster have version 6.x you upgrade all nodes from 6.x to 7.x
Note that couchbase cluster can run different node versions in the same cluster (called mixed mode), only when all nodes are upgraded to the latest version only then all version features are available.
I personally upgraded couchbase in test and production from version 6.0.3 to 6.5, from 6.5 to 6.6 and from 6.6 to 7.1
There is also data migration tool
https://github.com/tchlyah/couchmove
But specifically our current top option is to use solution provided by own CI/CD team
(that similarly defines SQL++ statements to execute)
If yes then what is the url/api to access it from run.pivotal.io 's trial account.
Also can the features of credhub be tested using pcfdev?
Thanks
Ver 0.28.0 is the latest PCFDev available on PivNet
It is PCF ver 1.11.x. Two versions older. This version does not support CredHub.
If I recall correctly, in ver 1.12 all internal properties are stored in CredHub. That said, PCFDev is not meant for production by any means. So, it may not support CredHub.
To test locally, you can spin up a credhub instance. And use that in your PCF app. To do that you will need VirtualBox and spin up a bosh-lite instance with CredHub.
Take a look at this article on how to set it up.
No, credhub is not supported for application developers on PWS at this time.
I am trying to develop server-side using loopback with database connector.
However, I am quite confused with installing loopback on AWS.
reference for installing loopback on AWS
This website mentioned that only loopback of version 2.0 could be installed.
Yet, when I browse through loopback website, https://strongloop.com/strongblog/how-to-setup-push-notifications-private-mbaas-amazon-aws-part-1/, this website shows that it seems possible to install loopback of version higher than 2.0 on AWS. Since there are some features only available after version 2.1x, it would be nice if AWS allows installation of loopback of version higher than 2.0. Could anyone help me solve the problem? BTW, I am only using free tier of AWS and do not intend to pay at this moment.
Even if you install the image that comes preconfigured with Loopback 2, you should be able to upgrade to newer versions using npm as you normally would (sudo npm install -g strongloop and the like). Imagine if there's a security issue that you'd need that wasn't backported for whatever reason...Loopback is just files and the image is just linux. You have free reign to update/upgrade whatever you need.
My recommendation would be to start out with a minimal Ubuntu image and install everything with npm. You'll understand the ecosystem better and won't be surprised by something you don't remember installing specifically.
One caveat that a bunch of preconfigured images have is they are only available on older instance types (m1 for instance--pun not intended ;)). They are slower and more expensive than newer instances.
You can probably install whatever you want.
The difference is that if you want a machine image that contains everything already there and don't want to build it yourself you're stuck to 2.0 here (https://aws.amazon.com/marketplace/pp/B00PG9I0M0)
What I would do is use the provided AMI and after that upgrade loopback manually.
Can I install coldfusion 8 and coldfusion 9 on the same server and use them separately?
Great thanks.
Here's how you do the install: Installing Multiple Versions of ColdFusion Together - Presentation at Philadelphia CFUG meeting by Daria Norris
Yes, absolutely. Basically there is no difference from using few instances of same version, like described in the Installing the J2EE Configuration help section.
P.S. Vote for ServerFault.
Yes it can..
the main issue here is how your webserver works out which one to use when.
the best way to do this is to have two different webservers (apache and IIS) serving the two different versions of CF.
Other ways would be..
to have WSConfig point to the same proxy port for both versions of CF but then you could only run one at a time.
to have WSConfig bind two different sets of file extensions (ie .cfm8 goes to CF8 and .cfm goes to CF9
None of these are really great solutions but it depends on what you are trying to achieve.