My application id deployed on Jboss 7.1 and I can see 256 "MSC service thread" running and in waiting (parked) state.
What's the reason for so many threads? what do they do? Is it safe to reduce the number? If positive, how can I do that?
This was fixed in later versions of msc as part of https://issues.jboss.org/browse/MSC-144
you can manually upgrade jboss msc in 7.1.1 or upgrade to WildFly 8.1 that already has msc with this fix.
Related
I'm using Karaf 4.2.3 over JDK 1.8. I had ran a Black Duck Scan, and it is pointing to Apache ActiveMQ -5.15.9 with some vulnerabilities, one of them is critical. I'd like to know if it is possible to get this updated to the recommended version which is 5.17.1. Please if you have some advice it'd be highly appreciated. I'd like to point out that in the current project, I'm not really using ActiveMQ.
ActiveMQ 5.17.1 requires Java 11 so you won't be able to use that. You should upgrade to ActiveMQ 5.16.5 instead. It's the latest version which supports Java 8. That said, if you're not using ActiveMQ in your project then the simplest (and most secure) thing you can do is just remove it.
Initially i was using Tomee 7.0.68 version to deploy and run the web application.
But I now onwards I need to use Apache-tomee-plume-1.7.6 for the same. But after deploy what I found is that, There is No log or work or extracted war files generated once I run the server.
My question is, Is there any difference between apache-tomee-plume-1.7.6 and Tomee 7 to deploy and run/debug the appication?
How can I use Apache-tomee-plume-1.7.6 server?
Thanks.
TomEE 7.x.x is compatible with Java EE7.
TomEE 1.7.x is Java EE6 certified version.
Current TomEE 8.x branch is a work in progress for JavaEE8 compatibility.
As of today, TomEE 8.0.0-M3 is available containing also MicroProfile compatibility.
https://tomee.apache.org/download-ng.html
Earlier versions of Vxworks didn't support multiprocessing but I read Vxworks 6.6 and above support SMP (Symmetric multiprocessing).SMP would allow process to run parallel in multiple cores. But does Vxworks support multi-programming? One of the issues with Vxworks was that since whole software is one program, if one thread crash the whole software crash! Is it still the case?
The answer is Yes. There are several specific answers of Yes.
VxWorks 6.x and 7.x have process models (called RTPs)
VxWorks 6.6+ and 7.x have SMP.
VxWorks 7.x have memory models more like Unix.
VxWorks 6.x and VxWorks 7 both have Posix pthreads and native multiprogramming API including processor affinity API
I am using Vxworks 6.8 and it supports multiple threads well. Crash in a thread is isolated to it. Crashed thread terminates while others keep their execution.
We are using Worklight enterprise 6.2 with fix packs and we are planning to upgrade to 6.3 in the next month (beginning of May 2015). However, we see now that IBM is about to release MFP 7.
Can you please clarify to me those queries:
What is the impact on the project which has been developed on version 6.2 to be moved to 6.3 or 7?
What is the recommendation for us in terms of upgrading, should we go immediately to WL7 or to 6.3 first?
We are very close to the production and our concern that the WL7 "might" be unstable or contains issues that we might face in a critical time."Feedback would be appreciated"
MobileFirst Platform Foundation 7.0 is not about to be released - it is already released.
Lots of changes in both 6.3 and 7.0. Read the documentation to see what's changed...
6.3: http://www-01.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.getstart.doc/start/c_release_notes.html
7.0: http://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.getstart.doc/start/c_release_notes.html
In terms of your project structure, starting 6.3 the adapter thread pool has been removed and you are now in complete control of it. Your adapter XML will be upgraded to the new structure.
In terms of technology, starting 7.0 there is REST support together with a new authentication mechanism - OAuth. Classic authentication is as before and is still there. There are also now Java adapters in addition to JavaScript adapters, and lots more.
7.0 is indeed new, but provides you with a lot of new possibilities.
6.3 is very stable (that is not to say that 7.0 is not stable, but it's also very new).
We cannot decide for you if to upgrade or not, it sounds like you are already considering the right things to consider.
Read about the two releases.
I heard that JBoss 7 is not certified for FreeBSD - is that correct?
Where can I find a list of supported platforms? (I spent some time googling, but was not successful)
Strictly speaking there is no certified OS for JBoss 7 as only JBoss EAP 6 is supported by Red Hat.
The supported configuration for JBoss EAP 6 (the supported version of community JBoss 7) can be found here: https://access.redhat.com/knowledge/articles/111663
As JBoss is pure java application, a compliant JDK is enough to have a supported system. So if you have the Oracle or IBM JDK running on FreeBSD is will be supported by Red Hat. But they haven't test them with JBoss.
Any way if you want Red Hat support for the EAP you better check with there representative to discus the extends of the support (if the FreeBSD JDK have some compliance bug, they will probably send you back to the JDK supplier. If you chose RHEL with OpenJDK you will have one supplier to blame for any software stack issue, no redirect to another suplier.)
For community JBoss as for other platform, you will be responsible to make it work with your stack. An good first test can be performed by running the standard compliance tests included in the JBoss sources, if it runs on your target platform and JDK it is a good sign that JBoss is working on it.
Certified Support as per Redhat only goes up to 6:
https://access.redhat.com/knowledge/articles/111663
However if you look back at the release docs they have not changed. OS's are the same.