Today i faced with issue that puppetserver suddenly become dead.
I already tried to add -Djava.io.tmpdir=/var/lib/puppet/tmp to JAVA_ARGS in /etc/default/puppetserver
this new tmp folder have 1777 perms and puppet as owner.
There is no more helpful result during google =(
Please help where to dig ?
Full log here https://drive.google.com/file/d/1h-Tmqg9YJ5VLWe4OhvftNzQHOxkzfesF/view?usp=sharing
2022-10-20T18:41:05.668Z INFO [main] [o.e.j.u.log] Logging initialized #14500ms to org.eclipse.jetty.util.log.Slf4jLog
2022-10-20T18:41:07.894Z INFO [async-dispatch-2] [p.t.s.s.scheduler-service] Initializing Scheduler Service
2022-10-20T18:41:08.005Z INFO [async-dispatch-2] [o.q.i.StdSchedulerFactory] Using default implementation for ThreadExecutor
2022-10-20T18:41:08.069Z INFO [async-dispatch-2] [o.q.c.SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
2022-10-20T18:41:08.069Z INFO [async-dispatch-2] [o.q.c.QuartzScheduler] Quartz Scheduler v.2.3.2 created.
2022-10-20T18:41:08.070Z INFO [async-dispatch-2] [o.q.s.RAMJobStore] RAMJobStore initialized.
2022-10-20T18:41:08.078Z INFO [async-dispatch-2] [o.q.c.QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v2.3.2) 'c709d36f-47d9-48e3-a618-a56f2f00e737' with instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
2022-10-20T18:41:08.078Z INFO [async-dispatch-2] [o.q.i.StdSchedulerFactory] Quartz scheduler 'c709d36f-47d9-48e3-a618-a56f2f00e737' initialized from an externally provided properties instance.
2022-10-20T18:41:08.078Z INFO [async-dispatch-2] [o.q.i.StdSchedulerFactory] Quartz scheduler version: 2.3.2
2022-10-20T18:41:08.078Z INFO [async-dispatch-2] [o.q.c.QuartzScheduler] Scheduler c709d36f-47d9-48e3-a618-a56f2f00e737_$_NON_CLUSTERED started.
2022-10-20T18:41:08.087Z INFO [async-dispatch-2] [p.t.s.w.jetty9-service] Initializing web server(s).
2022-10-20T18:41:08.272Z INFO [async-dispatch-2] [p.t.s.s.status-service] Registering status callback function for service 'puppet-profiler', version 7.9.2
2022-10-20T18:41:08.282Z INFO [async-dispatch-2] [p.s.j.jruby-puppet-service] Initializing the JRuby service
2022-10-20T18:41:08.359Z INFO [async-dispatch-2] [p.s.j.jruby-pool-manager-service] Initializing the JRuby service
2022-10-20T18:41:08.396Z INFO [async-dispatch-2] [p.s.j.jruby-puppet-service] JRuby version info: jruby 9.3.4.0 (2.6.8) 2022-03-23 eff48c1ebf OpenJDK 64-Bit Server VM 25.342-b07 on 1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 +jit [x86_64-linux]
2022-10-20T18:41:08.466Z INFO [clojure-agent-send-pool-0] [p.s.j.i.jruby-internal] Creating JRubyInstance with id 1.
2022-10-20T18:41:08.487Z INFO [async-dispatch-2] [p.t.s.s.status-service] Registering status callback function for service 'jruby-metrics', version 7.9.2
2022-10-20T18:41:08.509Z INFO [async-dispatch-2] [p.s.v.versioned-code-service] No code-id-command set for versioned-code-service. Code-id will be nil.
2022-10-20T18:41:08.515Z INFO [async-dispatch-2] [p.s.v.versioned-code-service] No code-content-command set for versioned-code-service. Attempting to fetch code content will fail.
2022-10-20T18:41:08.538Z INFO [async-dispatch-2] [p.t.s.m.jolokia] Metrics access control using trapperkeeper-authorization is enabled.
2022-10-20T18:41:20.640Z ERROR [async-dispatch-2] [p.t.internal] Error during service init!!!
java.lang.IllegalStateException: Unable to borrow JRubyInstance from pool
at puppetlabs.services.jruby_pool_manager.impl.jruby_internal$fn__34345$borrow_from_pool_BANG__STAR___34350$fn__34351.invoke(jruby_internal.clj:313)
at puppetlabs.services.jruby_pool_manager.impl.jruby_internal$fn__34345$borrow_from_pool_BANG__STAR___34350.invoke(jruby_internal.clj:300)
at puppetlabs.services.jruby_pool_manager.impl.jruby_internal$fn__34392$borrow_from_pool_with_timeout__34397$fn__34398.invoke(jruby_internal.clj:348)
at puppetlabs.services.jruby_pool_manager.impl.jruby_internal$fn__34392$borrow_from_pool_with_timeout__34397.invoke(jruby_internal.clj:337)
at puppetlabs.services.jruby_pool_manager.impl.instance_pool$fn__35156.invokeStatic(instance_pool.clj:48)
at puppetlabs.services.jruby_pool_manager.impl.instance_pool$fn__35156.invoke(instance_pool.clj:10)
at puppetlabs.services.protocols.jruby_pool$fn__34946$G__34894__34953.invoke(jruby_pool.clj:3)
at puppetlabs.services.jruby_pool_manager.jruby_core$fn__36070$borrow_from_pool_with_timeout__36075$fn__36076.invoke(jruby_core.clj:222)
at puppetlabs.services.jruby_pool_manager.jruby_core$fn__36070$borrow_from_pool_with_timeout__36075.invoke(jruby_core.clj:209)
at puppetlabs.services.config.puppet_server_config_core$fn__44216$get_puppet_config__44221$fn__44222$fn__44223.invoke(puppet_server_config_core.clj:107)
at puppetlabs.services.config.puppet_server_config_core$fn__44216$get_puppet_config__44221$fn__44222.invoke(puppet_server_config_core.clj:107)
at puppetlabs.services.config.puppet_server_config_core$fn__44216$get_puppet_config__44221.invoke(puppet_server_config_core.clj:102)
at puppetlabs.services.config.puppet_server_config_service$reify__44251$service_fnk__5324__auto___positional$reify__44262.init(puppet_server_config_service.clj:25)
at puppetlabs.trapperkeeper.services$fn__5148$G__5140__5151.invoke(services.clj:9)
at puppetlabs.trapperkeeper.services$fn__5148$G__5139__5155.invoke(services.clj:9)
at puppetlabs.trapperkeeper.internal$fn__14616$run_lifecycle_fn_BANG___14623$fn__14624.invoke(internal.clj:196)
at puppetlabs.trapperkeeper.internal$fn__14616$run_lifecycle_fn_BANG___14623.invoke(internal.clj:179)
at puppetlabs.trapperkeeper.internal$fn__14645$run_lifecycle_fns__14650$fn__14651.invoke(internal.clj:229)
at puppetlabs.trapperkeeper.internal$fn__14645$run_lifecycle_fns__14650.invoke(internal.clj:206)
at puppetlabs.trapperkeeper.internal$fn__15283$build_app_STAR___15292$fn$reify__15304.init(internal.clj:602)
at puppetlabs.trapperkeeper.internal$fn__15331$boot_services_for_app_STAR__STAR___15338$fn__15339$fn__15341.invoke(internal.clj:630)
at puppetlabs.trapperkeeper.internal$fn__15331$boot_services_for_app_STAR__STAR___15338$fn__15339.invoke(internal.clj:629)
at puppetlabs.trapperkeeper.internal$fn__15331$boot_services_for_app_STAR__STAR___15338.invoke(internal.clj:623)
at clojure.core$partial$fn__5910.invoke(core.clj:2647)
at puppetlabs.trapperkeeper.internal$fn__14690$initialize_lifecycle_worker__14701$fn__14702$fn__14865$state_machine__11925__auto____14890$fn__14893.invoke(internal.clj:249)
at puppetlabs.trapperkeeper.internal$fn__14690$initialize_lifecycle_worker__14701$fn__14702$fn__14865$state_machine__11925__auto____14890.invoke(internal.clj:249)
at clojure.core.async.impl.ioc_macros$run_state_machine.invokeStatic(ioc_macros.clj:978)
at clojure.core.async.impl.ioc_macros$run_state_machine.invoke(ioc_macros.clj:977)
at clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invokeStatic(ioc_macros.clj:982)
at clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invoke(ioc_macros.clj:980)
at clojure.core.async$ioc_alts_BANG_$fn__12154.invoke(async.clj:421)
at clojure.core.async$do_alts$fn__12093$fn__12096.invoke(async.clj:288)
at clojure.core.async.impl.channels.ManyToManyChannel$fn__6766$fn__6767.invoke(channels.clj:99)
at clojure.lang.AFn.run(AFn.java:22)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at clojure.core.async.impl.concurrent$counted_thread_factory$reify__6669$fn__6670.invoke(concurrent.clj:29)
at clojure.lang.AFn.run(AFn.java:22)
at java.lang.Thread.run(Thread.java:750)
Caused by: org.jruby.embed.EvalFailedException: (LoadError) load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory
at org.jruby.embed.internal.EmbedEvalUnitImpl.run(EmbedEvalUnitImpl.java:131)
at org.jruby.embed.ScriptingContainer.runUnit(ScriptingContainer.java:1296)
at org.jruby.embed.ScriptingContainer.runScriptlet(ScriptingContainer.java:1289)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:167)
at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:102)
at puppetlabs.services.jruby.jruby_puppet_core$fn__36371$get_initialize_pool_instance_fn__36376$fn__36377$fn__36378.invoke(jruby_puppet_core.clj:118)
at puppetlabs.services.jruby_pool_manager.impl.jruby_internal$fn__34145$create_pool_instance_BANG___34154$fn__34157.invoke(jruby_internal.clj:256)
at puppetlabs.services.jruby_pool_manager.impl.jruby_internal$fn__34145$create_pool_instance_BANG___34154.invoke(jruby_internal.clj:225)
at puppetlabs.services.jruby_pool_manager.impl.jruby_agents$fn__34563$add_instance__34568$fn__34572.invoke(jruby_agents.clj:52)
at puppetlabs.services.jruby_pool_manager.impl.jruby_agents$fn__34563$add_instance__34568.invoke(jruby_agents.clj:47)
at puppetlabs.services.jruby_pool_manager.impl.jruby_agents$fn__34590$prime_pool_BANG___34595$fn__34599.invoke(jruby_agents.clj:76)
at puppetlabs.services.jruby_pool_manager.impl.jruby_agents$fn__34590$prime_pool_BANG___34595.invoke(jruby_agents.clj:61)
at puppetlabs.services.jruby_pool_manager.impl.instance_pool$fn__35152$fn__35153.invoke(instance_pool.clj:16)
at puppetlabs.trapperkeeper.internal$shutdown_on_error_STAR_.invokeStatic(internal.clj:403)
at puppetlabs.trapperkeeper.internal$shutdown_on_error_STAR_.invoke(internal.clj:378)
at puppetlabs.trapperkeeper.internal$shutdown_on_error_STAR_.invokeStatic(internal.clj:388)
at puppetlabs.trapperkeeper.internal$shutdown_on_error_STAR_.invoke(internal.clj:378)
at puppetlabs.trapperkeeper.internal$fn__15134$shutdown_service__15139$fn$reify__15141$service_fnk__5324__auto___positional$reify__15146.shutdown_on_error(internal.clj:448)
at puppetlabs.trapperkeeper.internal$fn__15081$G__15060__15089.invoke(internal.clj:411)
at puppetlabs.trapperkeeper.internal$fn__15081$G__15059__15098.invoke(internal.clj:411)
at clojure.core$partial$fn__5908.invoke(core.clj:2642)
at clojure.core$partial$fn__5908.invoke(core.clj:2641)
at puppetlabs.services.jruby_pool_manager.impl.jruby_agents$fn__34537$send_agent__34542$fn__34543$agent_fn__34544.invoke(jruby_agents.clj:41)
at clojure.core$binding_conveyor_fn$fn__5823.invoke(core.clj:2050)
at clojure.lang.AFn.applyToHelper(AFn.java:154)
at clojure.lang.RestFn.applyTo(RestFn.java:132)
at clojure.lang.Agent$Action.doRun(Agent.java:114)
at clojure.lang.Agent$Action.run(Agent.java:163)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
... 1 common frames omitted
Caused by: org.jruby.exceptions.LoadError: (LoadError) load error: psych -- java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:85)
at RUBY.<main>(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych_jars.rb:2)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:85)
at RUBY.<main>(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:5)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:85)
at RUBY.<main>(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/yaml.rb:4)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:85)
at RUBY.<main>(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/format_handler.rb:1)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at org.jruby.RubyKernel.require_relative(org/jruby/RubyKernel.java:1045)
at RUBY.<main>(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/format_support.rb:1)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at org.jruby.RubyKernel.require_relative(org/jruby/RubyKernel.java:1045)
at RUBY.<main>(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/tag_set.rb:2)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at org.jruby.RubyKernel.require_relative(org/jruby/RubyKernel.java:1045)
at RUBY.<main>(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/tagging.rb:2)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at org.jruby.RubyKernel.require_relative(org/jruby/RubyKernel.java:1045)
at RUBY.<main>(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:1)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at org.jruby.RubyKernel.require_relative(org/jruby/RubyKernel.java:1045)
at RUBY.<main>(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/logging.rb:2)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at org.jruby.RubyKernel.require_relative(org/jruby/RubyKernel.java:1045)
at RUBY.<main>(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:795)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at org.jruby.RubyKernel.require_relative(org/jruby/RubyKernel.java:1045)
at RUBY.<main>(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:16)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:85)
at RUBY.<main>(uri:classloader:/puppetserver-lib/puppet/server.rb:1)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:85)
at RUBY.<main>(uri:classloader:/puppetserver-lib/puppet/server/master.rb:1)
at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1017)
at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:85)
at RUBY.<main>(<script>:1)
Caused by: java.lang.RuntimeException: BUG: we can not copy embedded jar to temp directory
Related
Using Red Hat WildFly 27.0.1 I'm trying to migrate Mojarra 4.0.0.SP01 to MyFaces 4.0.
Trying to use document "7.26. Jakarta Server Faces Configuration" at:
https://docs.wildfly.org/27/Admin_Guide.html#Jakarta_Server_Faces
Also I can't run "7.26.2. Changing the default Jakarta Server Faces implementation":
./jboss-cli.sh /subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=<JSF_IMPL_NAME>-<JSF_VERSION>)
I find the document conflicts.
Also "Working of the Multi-JSF Implementation" (posted on WildFly Forum).
How can I do this? TIA.
Posted on WildFly Forum: "That support is currently not working correctly. We have an open JIRA to address that, but we've simply had higher priorities. I hope to get to that "soon", but I can't make any promises. Principal Software Engineer, Red Hat JBoss EAP"
Have upgraded to MyFaces 4.0.0-RC4. Unable to resolve "WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid":
15:00:15,485 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "java-jakarta-primefaces-1.0.war" (runtime-name: "java-jakarta-primefaces-1.0.war")
15:00:17,208 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Read persistence.xml for io.aturanj.jakarta.pu
15:00:17,223 WARN [org.jboss.as.jsf] (MSC service thread 1-8) WFLYJSF0005: Unknown Jakarta Server Faces version 'myfaces-impl-4.0.0-RC4'. Default version 'myfaces-impl-4.0.0' will be used instead.
15:00:17,223 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "java-jakarta-primefaces-1.0.war"
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
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:1377)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid
at org.jboss.as.jsf#27.0.1.Final//org.jboss.as.jsf.deployment.JSFDependencyProcessor.deploy(JSFDependencyProcessor.java:94)
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
... 8 more
15:00:17,225 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
15:00:17,225 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
15:00:17,226 ERROR [org.jboss.as.server] (External Management Request Threads -- 1) WFLYSRV0021: Deploy of deployment "java-jakarta-primefaces-1.0.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
15:00:17,244 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment java-jakarta-primefaces-1.0.war (runtime-name: java-jakarta-primefaces-1.0.war) in 17ms
Next ...
Have added to WildFly 27 with:
com/sun/jsf-impl/myfaces-impl-4.0.0/myfaces-impl-4.0.0-RC4.jar
com/sun/jsf-impl/myfaces-impl-4.0.0/module.xml
javax/faces/api/myfaces-impl-4.0.0/module.xml
javax/faces/api/myfaces-impl-4.0.0/myfaces-api-4.0.0-RC4.jar
org/apache/commons/digester/main/commons-digester3-3.2.jar
org/apache/commons/digester/main/module.xml
org/jboss/as/jsf-injection/myfaces-impl-4.0.0/module.xml
org/jboss/as/jsf-injection/myfaces-impl-4.0.0/weld-jsf-5.1.0.Final.jar
org/jboss/as/jsf-injection/myfaces-impl-4.0.0/weld-jsf-5.1.0.Final.jar
Run:
./jboss-cli.sh
connect
/subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=myfaces-impl-4.0.0)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
Then:
/subsystem=jsf:list-active-jsf-impls()
Deployed test WAR:
14:03:01,310 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "java-jakarta-primefaces-1.0.war" (runtime-name: "java-jakarta-primefaces-1.0.war")
14:03:03,431 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Read persistence.xml for io.aturanj.jakarta.pu
14:03:03,455 WARN [org.jboss.as.jsf] (MSC service thread 1-2) WFLYJSF0005: Unknown Jakarta Server Faces version 'myfaces-impl-4.0.0'. Default version 'myfaces-impl-4.0.0' will be used instead.
14:03:03,456 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "java-jakarta-primefaces-1.0.war"
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
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:1377)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid
at org.jboss.as.jsf#27.0.1.Final//org.jboss.as.jsf.deployment.JSFDependencyProcessor.deploy(JSFDependencyProcessor.java:94)
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
... 8 more
14:03:03,458 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
14:03:03,458 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
14:03:03,461 ERROR [org.jboss.as.server] (External Management Request Threads -- 1) WFLYSRV0021: Deploy of deployment "java-jakarta-primefaces-1.0.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
14:03:03,487 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment java-jakarta-primefaces-1.0.war (runtime-name: java-jakarta-primefaces-1.0.war) in 26ms
14:08:35,964 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 86) WFLYDR0009: Content /usr/local/Cellar/wildfly-as/wildfly-preview-27.0.1.Final-MyFaces/standalone/data/content/fc/c21529f2a77775585d0b6dc2bc91c7ae02d4f6 is obsolete and will be removed
14:08:35,967 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 86) WFLYDR0002: Content removed from location /usr/local/Cellar/wildfly-as/wildfly-preview-27.0.1.Final-MyFaces/standalone/data/content/fc/c21529f2a77775585d0b6dc2bc91c7ae02d4f6/content
Results still with:
Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid
Answer - MyFaces won't run/deploy on:
wildfly-preview-27.0.1.Final
Works with:
wildfly-27.0.1.Final
I have installed spark 2.3.2 on a cluster of 2 workers and 1 master.
Im executing
spark-submit \
--class com.group.Main \
--master spark:<publicIp>:6066 \
--deploy-mode cluster app.jar input.txt
and below is the output
2022-08-25 03:20:41 WARN Utils:66 - Your hostname, master resolves to a loopback address: 127.0.1.1; using <publicIp> instead (on interface eth1)
2022-08-25 03:20:41 WARN Utils:66 - Set SPARK_LOCAL_IP if you need to bind to another address
Running Spark using the REST application submission protocol.
2022-08-25 03:20:52 INFO RestSubmissionClient:54 - Submitting a request to launch an application in spark://<publicIp>:6066.
2022-08-25 03:20:52 INFO RestSubmissionClient:54 - Submission successfully created as driver-20220825032052-0003. Polling submission state...
2022-08-25 03:20:52 INFO RestSubmissionClient:54 - Submitting a request for the status of submission driver-20220825032052-0003 in spark://<publicIp>:6066.
2022-08-25 03:20:52 INFO RestSubmissionClient:54 - State of driver driver-20220825032052-0003 is now RUNNING.
2022-08-25 03:20:52 INFO RestSubmissionClient:54 - Driver is running on worker worker-20220825031423-zz.zz.zz.zz-42773 at <publicIp>:42773.
2022-08-25 03:20:53 INFO RestSubmissionClient:54 - Server responded with CreateSubmissionResponse:
{
"action" : "CreateSubmissionResponse",
"message" : "Driver successfully submitted as driver-20220825032052-0003",
"serverSparkVersion" : "2.3.2",
"submissionId" : "driver-20220825032052-0003",
"success" : true
}
2022-08-25 03:20:53 INFO ShutdownHookManager:54 - Shutdown hook called
2022-08-25 03:20:53 INFO ShutdownHookManager:54 - Deleting directory /tmp/spark-aaeb9959-ba1f-4a5b-b7c4-6d0d3eb6ca70
On spark UI the application is reported always as FAILED
Please note that on client mode the application runs
--Updated--
As I was looking in stderr driver logs that the issue might be relevant to the files input of the application
I have tried multiple ways having input directory/single file on the local system
And getting the bellow error
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.spark.deploy.worker.DriverWrapper$.main(DriverWrapper.scala:65)
at org.apache.spark.deploy.worker.DriverWrapper.main(DriverWrapper.scala)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 0
is there any way to achieve file input in spark without using hdfs or s3?
I have download Pentaho 7 CE edition and I have not been able to make it work. I have noticed that there is System Error 0014 that pops up in the log.
I have also downloaded Java jre1.8.0_131 and I am using Windows 10 machine. The following is a snippet of the error log in the tomcat.
20:39:08,993 ERROR [OSGIBoot] Error starting Karaf
java.lang.RuntimeException: Could not resolve mvn:org.apache.felix/org.apache.felix.framework/4.2.1
at org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
at org.apache.karaf.main.Main.createClassLoader(Main.java:309)
at org.apache.karaf.main.Main.launch(Main.java:229)
at org.pentaho.platform.osgi.KarafBoot$4.run(KarafBoot.java:239)
at java.lang.Thread.run(Unknown Source)
at org.pentaho.platform.osgi.KarafBoot.startup(KarafBoot.java:247)
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:443)
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:434)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:413)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:434)
at org.pentaho.platform.engine.core.system.PentahoSystem.access$000(PentahoSystem.java:84)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:365)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:362)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:413)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:362)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:332)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:228)
at org.pentaho.platform.web.http.context.SolutionContextListener.contextInitialized(SolutionContextListener.java:162)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4853)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1092)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1834)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
20:39:09,001 ERROR [Logger] Error: Pentaho
20:39:09,005 ERROR [Logger] misc-org.pentaho.platform.engine.core.system.PentahoSystem: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.osgi.OSGIBoot
org.pentaho.platform.api.engine.PentahoSystemException: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.osgi.OSGIBoot
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:370)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:332)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:228)
at org.pentaho.platform.web.http.context.SolutionContextListener.contextInitialized(SolutionContextListener.java:162)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4853)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1092)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1834)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.osgi.OSGIBoot
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:452)
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:434)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:413)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:434)
at org.pentaho.platform.engine.core.system.PentahoSystem.access$000(PentahoSystem.java:84)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:365)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:362)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:413)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:362)
... 16 more
Caused by: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.osgi.OSGIBoot
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:444)
... 24 more
20:39:09,009 ERROR [Logger] Error end:
20:39:09,009 INFO [PeriodicStatusLogger] Warning, one or more errors occurred during the initialization process.
Pentaho BI Platform server failed to properly initialize. The system will not be available for requests. (pentaho-platform-core 7.1.0.0-12) Fully Qualified Server Url = http://localhost:8080/pentaho/, Solution Path = C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\pentaho-solutions
10-Jul-2018 20:39:29.970 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\pentaho has finished in 295,164 ms
10-Jul-2018 20:39:29.970 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\pentaho-style
10-Jul-2018 20:39:30.894 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
10-Jul-2018 20:39:30.910 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\pentaho-style has finished in 940 ms
10-Jul-2018 20:39:30.910 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\ROOT
10-Jul-2018 20:39:31.640 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
10-Jul-2018 20:39:31.656 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\ROOT has finished in 730 ms
10-Jul-2018 20:39:31.656 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\sw-style
10-Jul-2018 20:39:32.398 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
10-Jul-2018 20:39:32.414 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\sw-style has finished in 758 ms
10-Jul-2018 20:39:32.445 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-apr-8080"]
10-Jul-2018 20:39:32.632 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-apr-8009"]
10-Jul-2018 20:39:32.632 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 298043 ms
I would appreciate anyone help in resolving my issue.
When I am creating a web project deploy on WildFly application server, I'm getting following errors.
Server logs:
2015-10-29 14:23:20,060 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."JavaEEFirstProject.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."JavaEEFirstProject.war".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "JavaEEFirstProject.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:95)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
... 5 more
Caused by: java.io.FileNotFoundException: C:\Users\mert\IdeaProjects\JavaEEFirstProject\out\artifacts\JavaEEFirstProject\JavaEEFirstProject.war (Sistem belirtilen yolu bulamıyor)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:146)
at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:51)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:254)
at org.jboss.vfs.VFS.mountZipExpanded(VFS.java:533)
at org.jboss.as.server.deployment.DeploymentMountProvider$Factory$ServerDeploymentRepositoryImpl.mountDeploymentContent(DeploymentMountProvider.java:108)
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:91)
... 6 more
2015-10-29 14:23:20,066 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "JavaEEFirstProject.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"JavaEEFirstProject.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"JavaEEFirstProject.war\".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment \"JavaEEFirstProject.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
Caused by: java.io.FileNotFoundException: C:\\Users\\mert\\IdeaProjects\\JavaEEFirstProject\\out\\artifacts\\JavaEEFirstProject\\JavaEEFirstProject.war (Sistem belirtilen yolu bulamıyor)"}}
2015-10-29 14:23:20,069 ERROR [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0021: Deploy of deployment "JavaEEFirstProject.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"JavaEEFirstProject.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"JavaEEFirstProject.war\".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment \"JavaEEFirstProject.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
Caused by: java.io.FileNotFoundException: C:\\Users\\mert\\IdeaProjects\\JavaEEFirstProject\\out\\artifacts\\JavaEEFirstProject\\JavaEEFirstProject.war (Sistem belirtilen yolu bulamıyor)"}}
2015-10-29 14:23:20,078 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment JavaEEFirstProject.war (runtime-name: JavaEEFirstProject.war) in 7ms
2015-10-29 14:23:20,080 INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."JavaEEFirstProject.war".STRUCTURE
On Intellij IDEA 14 has artifacts for deployed files. And I think I have a problem on this artifacts section because i am getting artifacts path errors with FileNotFoundException named. I am sharing artifacts print on following.
How can I add .war file with artifacts pages?
Call "Build > Build Artifacts" and make sure (via Windows Explorer for example) that in the the JavaEEFirstProject folder there is a file called "JavaEEFirstProject.war". Then redeploy it from IDEA.
Currently, my service is running on http://localhost:8080/MyService/. I want to change localhost to service.example.com - http://service.example.com:8080/MyService/. I updated standalone-full.xml with the new alias.
<subsystem xmlns="urn:jboss:domain:web:2.1" default-virtual-server="default-host" native="false">
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" />
<virtual-server name="default-host" enable-welcome-root="true">
<alias name="localhost"/>
<alias name="service.example.com"/>
</virtual-server>
</subsystem>
But it did not work. I am getting "This Webpage is not available" message. Please suggest.
Update:
Changed jboss-web.xml as above. When deploy my war file, I am getting 404 error.
jboss-web.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
<security-domain>java:/jaas/EmpMem</security-domain>
<context-root>/</context-root>
<virtual-host>service.example.com</virtual-host>
</jboss-web>
standalone-full.xml
Server Log:
16:09:21,705 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-7) Exception during createSubject()JBAS013303: Runtime Exception:: java.lang.RuntimeException: JBAS013303: Runtime Exception:
at org.jboss.as.security.plugins.ModuleClassLoaderLocator.get(ModuleClassLoaderLocator.java:56)
at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:317)
at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:146)
at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:83)
at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1078)
at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1073)
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
at org.jboss.jca.deployers.common.AbstractDsDeployer.createSubject(AbstractDsDeployer.java:1072)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:600)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:282)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:316)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:120)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: org.jboss.modules.ModuleNotFoundException: com.usaa.loginmodule:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.as.security.plugins.SecurityActions.getModuleClassLoader(SecurityActions.java:61)
at org.jboss.as.security.plugins.ModuleClassLoaderLocator.get(ModuleClassLoaderLocator.java:47)
... 16 more
16:09:21,718 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:/usecom_sau]
16:09:21,734 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221013: Using NIO Journal
16:09:21,911 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221034: Waiting to obtain live lock
16:09:21,912 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221035: Live Server Obtained live lock
16:09:21,917 WARN [jacorb.codeset] (MSC service thread 1-4) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1
16:09:21,940 INFO [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016330: CORBA ORB Service started
16:09:22,009 INFO [org.jboss.web] (ServerService Thread Pool -- 61) JBAS018210: Register web context: /JBOSSWAR
16:09:22,035 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started
16:09:22,083 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment ent_securityprefs_empMemService.war
16:09:22,110 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: ent_securityprefs_empMemService.war
16:09:22,163 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.23 (redhat)
16:09:22,170 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment ent_securityprefs_empMemService.war
16:09:22,352 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 127.0.0.1:5455 for CORE protocol
16:09:22,354 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 127.0.0.1:5445 for CORE protocol
16:09:22,355 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221007: Server is now live
16:09:22,356 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221001: HornetQ Server version 2.3.20.Final (2.3.20, 123) [43f01d80-b3cb-11e4-a1e5-0d8484f2438a]
16:09:22,371 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
16:09:22,372 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.fooQueue
16:09:22,376 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/queue/foo
16:09:22,377 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/foo
16:09:22,378 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
16:09:22,414 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) JBAS010406: Registered connection factory java:/JmsXA
16:09:22,445 INFO [org.hornetq.ra] (MSC service thread 1-6) HornetQ resource adaptor started
16:09:22,446 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatorhornetq-ra
16:09:22,447 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
16:09:22,594 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.web.deployment."emp.example.com"./: org.jboss.msc.service.StartException in service jboss.web.deployment."emp.example.com"./: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.IllegalArgumentException: JBWEB000250: Child container with name already exists
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:794)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:353)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:62)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:38)
at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1704) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:52) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1949) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1908) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
... 3 more
16:09:22,630 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "JBOSSEAR.ear" (runtime-name : "JBOSSEAR.ear")
16:09:22,630 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "ent_securityprefs_empMemService.war" (runtime-name : "ent_securityprefs_empMemService.war")
16:09:22,631 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.web.deployment."emp.example.com"./: org.jboss.msc.service.StartException in service jboss.web.deployment."emp.example.com"./: Failed to start service
16:09:22,717 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
16:09:22,717 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:09:22,718 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started (with errors) in 3347ms - Started 360 of 399 services (2 services failed or missing dependencies, 75 services are lazy, passive or on-demand)
16:09:27,677 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment ent_securityprefs_empMemService.war
16:09:27,686 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment ent_securityprefs_empMemService.war (runtime-name: ent_securityprefs_empMemService.war) in 14ms
16:09:27,757 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "ent_securityprefs_empMemService.war" (runtime-name: "ent_securityprefs_empMemService.war")
16:09:27,759 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.catalina.servlets.DefaultServlet".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.jasper.servlet.JspServlet".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.jboss.as.weld.webtier.jsp.JspInitializationListener".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.web.deployment."emp.example.com"./.realm (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
JBAS014777: Services which failed to start: service jboss.web.deployment."emp.example.com"./
16:09:42,782 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found ent_securityprefs_empMemService.war in deployment directory. To trigger deployment create a file called ent_securityprefs_empMemService.war.dodeploy
16:09:42,788 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "ent_securityprefs_empMemService.war" (runtime-name: "ent_securityprefs_empMemService.war")
16:09:42,834 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment ent_securityprefs_empMemService.war
16:09:42,841 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: ent_securityprefs_empMemService.war
16:09:42,843 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment ent_securityprefs_empMemService.war
16:09:42,889 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.web.deployment."emp.example.com"./: org.jboss.msc.service.StartException in service jboss.web.deployment."emp.example.com"./: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.IllegalArgumentException: JBWEB000250: Child container with name already exists
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:794)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:353)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:62)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:38)
at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1704) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:52) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1949) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1908) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
... 3 more
16:09:42,893 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "ent_securityprefs_empMemService.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.web.deployment.\"emp.example.com\"./" => "org.jboss.msc.service.StartException in service jboss.web.deployment.\"emp.example.com\"./: Failed to start service
Caused by: java.lang.IllegalArgumentException: JBWEB000250: Child container with name already exists"}}
16:09:42,894 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment ent_securityprefs_empMemService.war
16:09:42,897 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment ent_securityprefs_empMemService.war (runtime-name: ent_securityprefs_empMemService.war) in 4ms
16:09:42,897 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014776: Newly corrected services:
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.faces.webapp.FacetTag".START (no longer required)
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.catalina.servlets.DefaultServlet".START (no longer required)
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.jasper.servlet.JspServlet".START (no longer required)
service jboss.web.deployment."emp.example.com"./.realm (no longer required)
JBAS014777: Services which failed to start: service jboss.web.deployment."emp.example.com"./
you need to specify an appropriate virtual-host definition in your jboss-web.xml descriptor.
<jboss-web>
<context-root>/</context-root>
<virtual-host>www.mydot.com</virtual-host>
</jboss-web>
Click here to read more