Getting org.osgi.framework.AdminPermission check failed - components

I am getting below exception after enabling security manager flag in wildfly can anyone help me here please how can i avoid this ? I tried adding <permission class="org.osgi.framework.AdminPermission" name="*" actions="*"/> in standalone.xml but still getting same exception.
java.security.AccessControlException: WFSM000001: Permission check failed (permission "("org.osgi.framework.AdminPermission" "(id=0)" "context")" in code source "(vfs:/content/myapp.war/WEB-INF/lib/org.eclipse.equinox.servletbridge_1.2.100.v20120209-2014.jar

I got the answer for this question from JBossDeveloper forum , there is already same question is in discussion for reference please refer:
https://developer.jboss.org/thread/275647

Related

SSL problems running azure-webapp-maven-plugin config

when running:
mvn com.microsoft.azure:azure-webapp-maven-plugin:1.14.0:config
I end up with
[ERROR] Failed to execute goal com.microsoft.azure:azure-webapp-maven-plugin:1.14.0:config (default-cli) on project storingen-api: Max retries 0 times exceeded. Error Details: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.microsoft.azure:azure-webapp-maven-plugin:1.14.0:config (default-cli) on project storingen-api: Max retries 0 times exceeded. Error Details: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Clearly this is a certificate problem that cannot be found. I have however no clue what certificate is needed nor in which keystore it needs to be. I suppose in the cacerts of my java distribution but it's not clear in any way.
Does anyone know which cert and where to put it ?
I just running into the same problem following Azure Learn Java Azure
Basically, this error ocurred because Java is trying to connect with your Azure Subscription at Azure Console. I saw the origin of this problem executing Maven command with -X. The log trace can be visualized over here, like this:
mvn com.microsoft.azure:azure-webapp-maven-plugin:1.12.0:config -X
What I did to solve:
I tried inserting Azure certifications inside Java cacerts - following the explanation here. But it didn't change or solved the problem.
I searched for a new one version of azure-webapp-maven-plugin. Nowadays, the version is 2.3.0. You can check at Maven repository the last version. It fixed my problem and no more throws the error caused by Java.
before: mvn com.microsoft.azure:azure-webapp-maven-plugin:1.12.0:config
after (I think so, that version fixes the problem): mvn com.microsoft.azure:azure-webapp-maven-plugin:2.3.0:config
Thanks

CDIIntegrationService errors were found when Weblogic upgrade from 12.1.2 to 12.1.3

I have upgraded Weblogic version in linux server by changing the wl_home path in the setDomainEnv.sh for 12.1.2 to 12.1.3 and restart. when restarting it gives below errors.
Appreciate if anyone can give idea about this.
java.lang.IllegalAccessError: tried to access method com.bea.logging.LogBufferHandler.bufferLogObject(Ljava/lang/Object;)V from class weblogic.logging.log4j.WLLog4jMemoryBufferAppender
java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.diagnostics.lifecycle.LoggingServerService
java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.diagnostics.lifecycle.DiagnosticFoundationService errors were found
java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.diagnostics.lifecycle.DiagnosticFoundationService
java.lang.IllegalArgumentException: While attempting to resolve the dependencies of com.oracle.injection.integration.CDIIntegrationService errors were found
java.lang.IllegalStateException: Unable to perform operation: resolve on com.oracle.injection.integration.CDIIntegrationService
Use the wllog4j.jar which is part of WLS 12.1.3 build. The one part of WLS_HOME/server/lib diretory.
If your domains-home/lib folder holds older wllog4.jar which was part of 12.1.2 then you will face this issue

How to stopMAS properly in JaCaMo?

I have a JaCaMo project where I'd like to stop the system when a believe is added as follow:
+winner <- .stopMAS.
I am doing like this in a pure Jason project, but in this JaCaMo project where I have an organization, after this stopMAS command an error is ocurring in CArtAgO API as bellow:
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1220)
at java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:335)
at java.util.concurrent.ArrayBlockingQueue.put(ArrayBlockingQueue.java:350)
at cartago.WorkspaceKernel.execOp(WorkspaceKernel.java:782)
at cartago.WorkspaceKernel.execOp(WorkspaceKernel.java:600)
at cartago.AgentBody.doAction(AgentBody.java:72)
at cartago.CartagoSession.doAction(CartagoSession.java:86)
at jacamo.infra.JaCaMoAgArch.stop(JaCaMoAgArch.java:198)
at jason.architecture.AgArch.stop(AgArch.java:57)
at jason.infra.centralised.CentralisedAgArch.stopAg(CentralisedAgArch.java:113)
at jason.infra.centralised.RunCentralisedMAS.stopAgs(RunCentralisedMAS.java:728)
at jason.infra.centralised.RunCentralisedMAS.finish(RunCentralisedMAS.java:826)
at jason.infra.centralised.CentralisedRuntimeServices.stopMAS(CentralisedRuntimeServices.java:110)
at jason.stdlib.stopMAS.execute(stopMAS.java:44)
at jason.asSemantics.TransitionSystem.applyExecInt(TransitionSystem.java:736)
at jason.asSemantics.TransitionSystem.applySemanticRuleAct(TransitionSystem.java:237)
at jason.asSemantics.TransitionSystem.act(TransitionSystem.java:1525)
at jason.infra.centralised.CentralisedAgArch.act(CentralisedAgArch.java:203)
at jason.infra.centralised.CentralisedAgArch.reasoningCycle(CentralisedAgArch.java:212)
at jason.infra.centralised.CentralisedAgArch.run(CentralisedAgArch.java:231)
at java.lang.Thread.run(Thread.java:748)
cartago.CartagoException: exec op exception.
at cartago.WorkspaceKernel.execOp(WorkspaceKernel.java:786)
at cartago.WorkspaceKernel.execOp(WorkspaceKernel.java:600)
at cartago.AgentBody.doAction(AgentBody.java:72)
at cartago.CartagoSession.doAction(CartagoSession.java:86)
at jacamo.infra.JaCaMoAgArch.stop(JaCaMoAgArch.java:198)
at jason.architecture.AgArch.stop(AgArch.java:57)
at jason.infra.centralised.CentralisedAgArch.stopAg(CentralisedAgArch.java:113)
at jason.infra.centralised.RunCentralisedMAS.stopAgs(RunCentralisedMAS.java:728)
at jason.infra.centralised.RunCentralisedMAS.finish(RunCentralisedMAS.java:826)
at jason.infra.centralised.CentralisedRuntimeServices.stopMAS(CentralisedRuntimeServices.java:110)
at jason.stdlib.stopMAS.execute(stopMAS.java:44)
at jason.asSemantics.TransitionSystem.applyExecInt(TransitionSystem.java:736)
at jason.asSemantics.TransitionSystem.applySemanticRuleAct(TransitionSystem.java:237)
at jason.asSemantics.TransitionSystem.act(TransitionSystem.java:1525)
at jason.infra.centralised.CentralisedAgArch.act(CentralisedAgArch.java:203)
at jason.infra.centralised.CentralisedAgArch.reasoningCycle(CentralisedAgArch.java:212)
at jason.infra.centralised.CentralisedAgArch.run(CentralisedAgArch.java:231)
at java.lang.Thread.run(Thread.java:748)
[GroupBoard] p1 has quit, role participant removed by the platform!
How to avoid this error? Is there anything I should do before this stopMAS command?
You can just ignore this message. The latest version of JaCaMo (0.7-SNAPSHOT) fixes this problem.

Setting Up Owasp crs rules Error creating rule: Failed to resolve operator: detectXSS on line 56

After adding Owasp crs rules for Modsecurity and restarting apache I am getting this error in REQUEST-941-APPLICATION-ATTACK-XSS.conf file.
AH00526: Syntax error on line 56 of /etc/apache2/modsecurity.d/rules/REQUEST-941-APPLICATION-ATTACK-XSS.conf:
Error creating rule: Failed to resolve operator: detectXSS
Action 'configtest' failed.
The Apache error log may have more information.
Please help me to fix this issue
DetectXSS was only added in ModSecurity 2.8: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#detectXSS
You must be running a previous version. Possibly because you are using a packaged version and they are terrible about keeping these up to date except for security patches. Centos/RHEL for example only has ModSecurity 2.7.3 in the standard repo for example.
You should upgrade to the latest version.

Error:Unable to start the daemon process.

Android Version:1.2.2
It shows Error:Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/2.2.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Please help me to fix this issue.
Error:Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at http://gradle.org/docs/2.2.1/userguide/gradle_daemon.html
Please read the following process output to find out more:
Any one help please

Resources