I'm trying to understand the concept of release chunks from the release matrix page: link
Looking at the ESB480 build instructions, the wording suggests that the release chunks are NOT backward compatible.
To determine which chunk to use for a specific product version, see
the Release Matrix
Question: Are turing release chunks backward compatible? For example, would API Manager 1.5.0 that was released with chunk 2 also run on chunk 5?
Turing platform is a new platform release concept introduced recently. The mail thread "Introducing the Carbon Platform Release Concept" on dev and architecture mailing lists explains this.
As you know, A WSO2 product = WSO2 Carbon + Set of features.
Your question is also about building from source. I know you have an idea about the WSO2 SVN structure and orbit, kernel and platform. You asked those questions :)
As I understand the ESB 4.8.0 Building from Source wiki page suggests that you should checkout relevant chunk release tag.
The release matrix has the information about the each chunk for a specific product.
For example, if you want to build ESB 4.8.0, you should checkout turing-chunk04 tag. To build API Manager 1.5.0, you should checkout turing-chunk02 tag.
Since the platform has all products, you must checkout relevant tag to get the released product.
The backward compatibility depends on each product. For example, the ESB 4.8.0 is not directly compatible with ESB 4.7.0 as the underlying Carbon is a major upgrade and there are user management changes. In such cases you need to migrate data. However the proxies may be compatible.
In general, any turing platform product is not directly backward compatible with a previous version of product with Carbon kernel version < 4.2.0.
Question: Are turing release chunks backward compatible? For example, would API Manager 1.5.0 that was released with chunk 2 also run on chunk 5?
AFAIU, your question is invalid. API Manager 1.5.0 is released under chunk02 and there is no API Manager release under chunk05. However API Manager 1.6.0 is released in Turing chunk 6. So you must checkout turing-chunk06 tag to build the API Manager 1.6.0.
I'm not sure API Manager 1.6.0 is compatible with API Manager 1.5.0. I'm not aware of the changes yet. However I can assure you that there are no changes in the user management and registry tables.
The important factors with Turing platform are that all products are based on Carbon 4.2.0 and there is only one P2 Repository. This means that any turing platform product can install features from a single Turing P2 repository.
I hope this helps to clear out your doubts.
Thanks!
Related
We have several plugins working in C++ with Autodesk 2016 so now wants to have these plugins working on Autodesk 2022 by upgrading Autodesk version. Please share the complete procedure for this.
Please share complete details of Autodesk Revit tool.
The steps for migrating Revit add-ins from one release to the next have been documented in full with many examples by The Building Coder in the category migration. As you probably know, the Revit API is .NET based, so the migration steps are independent of the programming language used. In many cases, no code modification is required from one release to the next, unless obsolete functionality is used. Obsoleted properties and methods are highlighted in the Revit API documentation included with the Revit SDK and also shared by The Building Coder in the articles on What's New in the Revit API.
I couldn't stomach purchasing the $150 for GCP's support service for this one question. I'm just looking to understand the schedule for Cloud Build Node.js versions. It's still stuck on Node.js v10.10 and my projects are starting to require higher versions to build. According to Cloud Build's changelog, I don't believe the Node.js version has updated in years. Any ideas?
As per the official Github repository:
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js.
So, this means it should work with Node.js 12 and the updates should be more constant. In addition to that, in here, it says that if you are using a Cloud Build config file, you can use Node.js 12, so the Node.js' latest version should be compatible with Cloud Build.
To summarize, by the repository, it should follow Node.js schedule. However, in case you think this is not occurring, I would recommend you to raise a bug on the Google's Issue Tracker - it's free, by the way - so they can assess this.
we are using Microsoft Sync Framework 2.1 in various customer projects for file and database sync. Extended Support will end in 2021.
So my questions are:
What is Microsofts strategy for the sync framework? Is it going to be open source, so we can change if needed ourselves? Is there a successor product that we should / can migrate to?
Is MSSF supported on Windows 10 and Server 2016?
Not sure if my answer really helps, but lets see: Microsoft announced the official release of the "Azure SQL Data Sync" on June 18 2018. It is not truly a successor of the original framework, but it is basically all you get. Other "non cloud" frameworks have also started to fade away, since Microsoft treats server/desktop/on-premise only as an extension to the cloud. As the name indicates, it is targeting Azure and it is not for file sync, either.
I have seen your question also in the "old" Microsoft social network (social.msdn.microsoft.com/Forums/en-US/home). In there they point to this framework in questions related to the original "Sync Framework" since something like 2012 (this was the oldest question I could associate with both frameworks).
We have a problem with our setup of WSO2 API Manager 1.10.0. We're using a clustered setup, with 3 gateway-worker-nodes and a manager node; separate store, publisher & key manager nodes (We recently updated from v1.8.0 to 1.10.0).
After the upgrade, every ~2 weeks, all our worker-nodes (and sometimes other nodes) heapdumps and crashes (pretty much at the same time).
Analyzing the heap dumps reveal:
28,509 instances of "com.hazelcast.nio.tcp.WriteHandler", loaded by "hazelcast" occupy 945,814,400 (44.42%) bytes
28,509 instances of "com.hazelcast.nio.tcp.ReadHandler", loaded by "hazelcast" occupy 940,796,960 (44.18%) bytes
with thread:
com.hazelcast.nio.tcp.iobalancer.IOBalancerThread # 0x7877eb628 hz.wso2.pubstore.domain.instance.IOBalancerThread Thread
We've not been able to search for a remedy. The logs tells us nothing other than the nodes getting OOM Exception. This happens on nodes with very little traffic and on nodes with very high traffic (different environments have the same behavior).
Anyone come across a similar behavior? Any ideas for going forward?
This did indeed turn out to be a memory-leak issue with Hazelcast. After upgrading to a later version, this problem stopped.
In order to upgrade Hazelcast, there's a bit of "trickery" to be done.
1) Download the WSO2 GitHub repo (or simply the pom-file) for your specific Hazelcast version here: https://github.com/wso2/orbit/tree/master/hazelcast
2) Change the Hazelcast version in this section of the POM (to your preferred version):
<properties>
<version.hazelcast>3.7.2</version.hazelcast>
</properties>
3) Build the package.
4) Deploy the built package as a Patch to your server.
This is a "work-around" as it's only possible to patch components with the same name as the ones already shipping with the product.
I'm looking for possibility to allow any users of certain project of Jira start (trigger) certain Hudson builds. Is it possible without creating own Jira plugin?
I would have expected this feature to be available with the Marvelution JIRA Hudson Integration, which offers functionality pretty similar to he one offered by the JIRA Bamboo Plugin (e.g. build status reporting) - surprisingly though, triggering builds as you desire seems not to be available in either one yet, despite an obvious feature indeed (the JIRA Bamboo Plugin has related/partial support at least, see Running a Bamboo Build when Releasing a Version).
Consequently you might want to file a feature request for the Marvelution JIRA Hudson Integration first rather than developing your own from scratch immediately, maybe it is going to be considered.
Please note that this plugin doesn't support JIRA 5.0 yet, but the respective version 5.0.0 is scheduled for May 24, 2012.