I got some issues with Wildfly.
I got this Exception but I don't know how to fix it...
I don't know what I could do know to fix this Problem...
.......................
21:58:09,529 INFO [org.jboss.modules] JBoss Modules version 1.3.0.Final
21:58:11,357 INFO [org.jboss.msc] JBoss MSC version 1.2.1.Final
21:58:12,201 INFO [org.jboss.as] JBAS015899: WildFly 8.0.1.Final-SNAPSHOT "WildFly" starting
21:58:21,545 INFO [org.jboss.as.server.deployment.scanner] JBAS015014: Re-attempting
failed deployment filesDB.war
21:58:21,545 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found fi
lesDb.war in deployment directory. To trigger deployment create a file called fi
lesDb.war.dodeploy
21:58:23,733 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Op
eration ("add") failed - address: ([("core-service" => "vault")]): java.lang.Run
timeException: JBAS015804: Error initializing vault -- org.jboss.as.server.serv
ices.security.VaultReaderException: JBAS013313: Vault Reader Exception:
at org.jboss.as.server.services.security.VaultAddHandler.performRuntime(
VaultAddHandler.java:82) [wildfly-server-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SN
APSHOT]
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddS
tepHandler.java:75) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNA
PSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeStep(Abstract
OperationContext.java:591) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Fi
nal-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(Abstr
actOperationContext.java:469) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1
.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal
(AbstractOperationContext.java:273) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar
:8.0.1.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(Abs
tractOperationContext.java:268) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0
.1.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.
java:333) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractControllerService.boot(AbstractContro
llerService.java:294) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-S
NAPSHOT]
at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildf
ly-server-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildf
ly-server-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractContr
ollerService.java:256) [wildfly-controller-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-
SNAPSHOT]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
Caused by: org.jboss.as.server.services.security.VaultReaderException: JBAS01331
3: Vault Reader Exception:
at org.jboss.as.security.vault.RuntimeVaultReader.createVault(RuntimeVau
ltReader.java:84) [wildfly-security-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHO
T]
at org.jboss.as.server.services.security.VaultAddHandler.performRuntime(
VaultAddHandler.java:80) [wildfly-server-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SN
APSHOT]
... 11 more
Caused by: org.jboss.security.vault.SecurityVaultException: java.lang.NullPointe
rException
at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecu
rityVault.java:210) [picketbox-4.0.21.Beta1.jar:4.0.21.Beta1]
at org.jboss.as.security.vault.RuntimeVaultReader.createVault(RuntimeVau
ltReader.java:82) [wildfly-security-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHO
T]
... 12 more
Caused by: java.lang.NullPointerException
at org.picketbox.plugins.vault.PicketBoxSecurityVault.checkAndConvertKey
StoreToJCEKS(PicketBoxSecurityVault.java:570) [picketbox-4.0.21.Beta1.jar:4.0.21
.Beta1]
at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecu
rityVault.java:207) [picketbox-4.0.21.Beta1.jar:4.0.21.Beta1]
... 13 more
21:58:23,780 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in a
n unrecoverable manner; exiting. See previous messages for details.
21:58:23,795 INFO [org.jboss.as] JBAS015950: WildFly 8.0.1.Final-SNAPSHOT "Wild
Fly" stopped in 11ms
Can anyone please help me? Thank You!
This is caused by a NullPointerException, so unfortunately, it is a bug. Please open an issue at https://issues.jboss.org/browse/SECURITY with this same description.
clean the server , or show in folder and delete all the folder exist in the deployment , and restart the server .
Related
I have a war file that I run under JBoss EAP 7.4. That war file contains a permissions.xml file that has the following:
<permissions version="7">
<!-- additional permissions omitted for brevity -->
<permission>
<class-name>javax.management.MBeanPermission</class-name>
<name>*</name>
<actions>queryNames,registerMBean,unregisterMBean</actions>
</permission>
</permissions>
Yet, when I run JBoss, I see the following error in the server.log, apparently caused by some hawtio code:
2022-11-17 19:36:30,507 ERROR
[org.jboss.as.controller.management-operation] (Controller Boot
Thread) WFLYCTL0013: Operation ("deploy") failed - address:
([("deployment" =>
"hawtio-wildfly-2.0.0.fuse-sb2-7_11_0-00036-redhat-00001.war")]) -
failure description: {"WFLYCTL0080: Failed services" =>
{"jboss.deployment.unit."hawtio-wildfly-2.0.0.fuse-sb2-7_11_0-00036-redhat-00001.war".undertow-deployment"
=> "java.lang.RuntimeException: java.lang.RuntimeException: java.security.AccessControlException: WFSM000001: Permission check
failed (permission "("javax.management.MBeanPermission"
"io.hawt.jmx.About#-[hawtio:type=About]" "registerMBean")" in
code source
"(vfs:/content/hawtio-wildfly-2.0.0.fuse-sb2-7_11_0-00036-redhat-00001.war/WEB-INF/lib/hawtio-system-2.0.0.fuse-sb2-7_11_0-00036-redhat-00001.jar
)" of "ModuleClassLoader for Module
"deployment.hawtio-wildfly-2.0.0.fuse-sb2-7_11_0-00036-redhat-00001.war"
from Service Module Loader")
It looks like there was a Red Hat Fuse defect similar to mine that got addressed around 2018. Why might I still be facing this problem? Is there something I can do on my end to resolve it? (I don't want to give all permissions.)
Trying to move from wildfly-25.0.0.Final (Jakarta EE 8 Full) to wildfly-preview-25.0.0.Final (Preview EE 9.1).
After adding my:
org/hibernate/ ...
org/jboss/ ...
I have WELD:
org/jboss/weld/3.1.4 ...
org/jboss/weld/4.0.0.Final ...
Error "Failed to link" at:
16:13:54,578 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 80) WFLYWS0002: Activating WebServices Extension
16:13:54,578 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 70) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
16:13:54,578 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 81) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "weld")]): java.lang.NoClassDefFoundError: Failed to link org/jboss/weld/exceptions/DeploymentException (Module "org.jboss.weld.core" version 3.1.5.Final from local module loader #7a1234bf (finder: local module finder #2f62ea70 (roots: /usr/local/Cellar/wildfly-as/wildfly-preview-25.0.0.Final/modules,/usr/local/Cellar/wildfly-as/wildfly-preview-25.0.0.Final/modules/system/layers/base))): javax/enterprise/inject/spi/DeploymentException
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1012)
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:423)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:555)
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339)
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126)
at org.jboss.modules.Module.loadModuleClass(Module.java:753)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
at org.jboss.as.weld#25.0.0.Final//org.jboss.as.weld.WeldSubsystemAdd.performBoottime(WeldSubsystemAdd.java:86)
at org.jboss.as.controller#17.0.1.Final//org.jboss.as.controller.AbstractBoottimeAddStepHandler.performRuntime(AbstractBoottimeAddStepHandler.java:119)
at org.jboss.as.controller#17.0.1.Final//org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:164)
at org.jboss.as.controller#17.0.1.Final//org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1045)
at org.jboss.as.controller#17.0.1.Final//org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:777)
at org.jboss.as.controller#17.0.1.Final//org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:466)
at org.jboss.as.controller#17.0.1.Final//org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
at java.base/java.lang.Thread.run(Thread.java:833)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Can see WELD 3.1.5 # https://weld.cdi-spec.org/news/2020/08/12/weld-315Final/
Which version of WELD should I use? 3.1.5 or 4.0.0.Final? Also where do I configure it?
(2) See 'Typo'.
Type on https://weld.cdi-spec.org/download/ for WELD 4.0.2 Finak:
WELD 4.0.2.Finak
Also error with "Download":
Not Found
The requested URL /weld/4.0.2.Finak was not found on this server.
Should be:
https://download.jboss.org/weld/4.0.2.Final/
Weld 4.x is the major version of Weld implementing EE 9 (e.g. with jakarta namespaces).
However, you don't need to declare this dependency manually. WildFly always contains Weld and the EE 9 variant is no different.
You can easily verify that by unpacking Wildfly distribution and looking into /modules/system/layers/base/org/jboss/weld
(2) See 'Typo'.
Thanks for pointing this out, I have fixed the broken link on Weld website.
I'm running jboss using command line its showing error as Failed to boot JBoss:java.lang.NullPointerException.
Failed to boot JBoss:
java.lang.NullPointerException
at org.jboss.system.server.profileservice.repository.StaticProfileFactory.create Source(StaticProfileFa
ctory.java:313)
at org.jboss.system.server.profileservice.repository.StaticProfileFactory.create ProfileMetaData(Static
ProfileFactory.java:270)
at org.jboss.system.server.profileservice.repository.StaticProfileFactory.createApplicationProfile(Sta
ticProfileFactory.java:245)
at org.jboss.system.server.profileservice.repository.StaticProfileFactory.createApplicationProfiles(St
aticProfileFactory.java:232)
at org.jboss.system.server.profileservice.repository.StaticProfileFactory.createProfileMetaData(Static
ProfileFactory.java:214)
at org.jboss.system.server.profileservice.repository.AbstractBootstrapProfileFactory.createProfiles(Ab
stractBootstrapProfileFactory.java:90)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:2
60)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:722)
06:07:01,743 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true
06:07:01,744 WARN [ProfileServiceBootstrap] Error deactivating profile: ProfileKey#eba82b[domain=default, ser
ver=default, name=default]
org.jboss.profileservice.spi.NoSuchProfileException: No active profile for: ProfileKey#eba82b[domain=default,
server=default, name=default]
at org.jboss.system.server.profileservice.repository.AbstractProfileService.deactivateProfile(Abstract
ProfileService.java:391)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.shutdown(ProfileServiceBootstrap.jav
a:327)
at org.jboss.bootstrap.AbstractServerImpl.shutdownServer(AbstractServerImpl.java:571)
at org.jboss.bootstrap.AbstractServerImpl$ShutdownHook.run(AbstractServerImpl.java:909)
06:07:01,747 WARN [ProfileServiceBootstrap] Error unregistering profile: ProfileKey#eba82b[domain=default, se
rver=default, name=default]
org.jboss.profileservice.spi.NoSuchProfileException: No such profile: ProfileKey#eba82b[domain=default, server
=default, name=default]
at org.jboss.system.server.profileservice.repository.AbstractProfileService.getProfile(AbstractProfile
Service.java:181)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.shutdown(ProfileServiceBootstrap.jav
a:336)
at org.jboss.bootstrap.AbstractServerImpl.shutdownServer(AbstractServerImpl.java:571) at org.jboss.bootstrap.AbstractServerImpl$ShutdownHook.run(AbstractServerImpl.java:909)
06:07:02,085 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
Press any key to continue . . .
Can anybody guide me to resolve this issue, your help will be appreciated.
org.jboss.profileservice.spi.NoSuchProfileException might be the reason of this NPE. Make sure that you have the 'default' domain present - I assume that you're tring to launch JBoss 5, is that correct?
I deployed successfully kie-drools-wb-distribution-wars-6.0.1.Final-jboss-as7.0.war on jboss-as-7.1.1.Final, running with jdk1.7.0_10.
But this configuration ...
kie-drools-wb-distribution-wars-6.0.1.Final-jboss-as7.0.war
wildfly-8.1.0.Final
jdk1.7.0_10
.. fails to deploy with this error :
14:58:06,531 WARN [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016011: Warning while parsing vfs:/C:/java/too
ls/wildfly-8.1.0.Final-guvnor/bin/content/kie-drools-wb-distribution-wars-6.0.1.Final-jboss-as7.0.war/WEB-INF/beans.xml:
1 cvc-elt.1 : DÚclaration de l'ÚlÚment 'beans' introuvable.
14:58:07,500 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.module
.service."deployment.kie-drools-wb-distribution-wars-6.0.1.Final-jboss-as7.0.war".main: org.jboss.msc.service.StartExcep
tion in service jboss.module.service."deployment.kie-drools-wb-distribution-wars-6.0.1.Final-jboss-as7.0.war".main: JBAS
018759: Failed to load module: deployment.kie-drools-wb-distribution-wars-6.0.1.Final-jboss-as7.0.war:main
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [wildfly-server-8.1.0.Fi
nal.jar:8.1.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-ms
c-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.F
inal.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_10]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_10]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_10]
Caused by: org.jboss.modules.ModuleNotFoundException: org.jboss.netty:main
at org.jboss.modules.Module.addPaths(Module.java:1050) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.Module.link(Module.java:1406) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1434) [jboss-modules.jar:1.3.3.Final]
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:242) [jboss-modules.jar:1.3.3.Final]
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [wildfly-server-8.1.0.Fi
nal.jar:8.1.0.Final]
... 5 more
The drools-wb documentation here :
http://docs.jboss.org/drools/release/6.0.1.Final/drools-docs/html/wb.Workbench.html#wb.Installation
jboss-as7: tailored for JBoss AS 7 (which is being renamed to WildFly
in version 8)
So the doc, let me think that this 6.0.1.Final release of the workbench should work well with wildfly. I might be wrong ?
I managed to figured out.
Thanks to this blog entry :
https://mswiderski.blogspot.ch/2014/06/lets-wildfly-with-jbpm6.html
So, obviously a kie-drools-wb-distribution-wars-6.0.1.Final-jboss-as7.0.war cannot be deployed to wildfly. But the documentation was confused.
Starting from version 6.1.0, there is a kie-drools-wb-distribution-wars-6.1.0.CR1-wildfly.war - I found it here :
http://central.maven.org/maven2/org/kie/kie-drools-wb-distribution-wars/6.1.0.CR1/
Finally, wildfly can be started with the default standalone.xml profile
(the standalone-full.xml profile is required for the kie-wb)
Hope that will be helpful for someone.
I'm trying to automate deployment of a play application as a .war file.
In the end the application will be run on JBOSS AS7.
The problem I'm running into right now is that when I deploy the war to JBOSS I get this exception.
14:52:39,728 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "my-test-app-server-0.0.2-SNAPSHOT.war"
14:52:43,822 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."my-test-app-server-0.0.2-SNAPSHOT.war".PARSE: org.jboss.msc.service.Start
Exception in service jboss.deployment.unit."my-test-app-server-0.0.2-SNAPSHOT.war".PARSE: Failed to process phase PARSE of deployment "my-test-app-server-0.0.2-SNAPSHOT.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to parse POJO xml ["/C:/jboss-as-web-7.0.2.Final/bin/content/my-test-app-server-0.0.2-SNAPSHOT.war/WEB-INF/lib/netty-3.2.5.Final.jar/META-INF/jboss-beans.xml"]
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:130)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptors(KernelDeploymentParsingProcessor.java:104)
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.deploy(KernelDeploymentParsingProcessor.java:76)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.2.Final.jar:7.0.2.Final]
... 5 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[17,1] Message: Unexpected element '{urn:jboss:bean-deployer:2.0}deployment'
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:98) [staxmapper-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) [staxmapper-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.as.pojo.KernelDeploymentParsingProcessor.parseDescriptor(KernelDeploymentParsingProcessor.java:123)
... 8 more
I found that if I manually remove the lib/netty-3.2.5.Final.jar file from the war before deploying it to JBOSS the problem goes away.
Now is there a way to do this when I'm generating the war with the play war command?
Any information on this would be much appreciated.
Thanks
Not that I am aware of simply. The play war command allows you to pass an exclude list, which I have copied the comments from the python file below.
~ To exclude some directories, use the --exclude option and ':'-separator (eg: --exclude .svn:target:logs:tmp).
However, this suggests it will only work for directories.
The command that is executed is package_as_war in framework/pym/utils.py, so you can hack that to specifically delete the file, but obviously this will not be backward compatible if you update your version of Play.