How to increase the MaxPermSize on the OpenShift environment? I am having trouble starting the jboss - deployment

I am new to OpenShift, and I am having trouble deploying my application, and it seems to be because I don't have enough MaxPermSize, which is set to 102m.
When I start the jboss I have this type of logs, loading the various services.
2014/12/30 10:13:37,806 ERROR [org.jboss.msc.service.fail] (MSC
service thread 1-3) MSC000001: Failed to start service
jboss.jacorb.poa-service.rootpoa: org.jbo
ss.msc.service.StartException in service
jboss.jacorb.poa-service.rootpoa: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936)
[jboss-msc.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_71]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71] Caused by: java.lang.OutOfMemoryError: unable to create new native
thread
at java.lang.Thread.start0(Native Method) [rt.jar:1.7.0_71]
at java.lang.Thread.start(Thread.java:714) [rt.jar:1.7.0_71]
at org.jacorb.poa.AOM.(AOM.java:135)
at org.jacorb.poa.POA.configure(POA.java:273)
at org.jacorb.orb.ORB.getRootPOA(ORB.java:1035)
at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1307)
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:153)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
[jboss-msc.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
[jboss-msc.jar:1.1.5.Final-redhat-1]
... 3 more
Like I said on the begginning, my guess is that I neeed to increase the JAVA_OPTS setting MaxPermSize to 256m or 512m. Can anyone help me do that on the OpenShift cenario?
Regards,
Emil Xavier

Openshift is a Cloud Platform.So Openshift will be provide dedicated server to you and there you might be have JBoss setup.
Just goto $JBOSS_HOME/bin/standalone.conf
Update your maxPermSize there.
Ex : JAVA_OPTS=-Xms1303M -Xmx1303M -XX:MaxPermSize=256M
Also you can update maxPermSize through each node wise and each group wise.

Related

Error JPA SPRING JBOSS Configuration Missing PersistenceUnitMetadata (thread local wasn't set)

I'm tryning an integration of SPRING JPA (Hibernate Implementation ) on existant Java EE Project with INFORMIX database.
I have this error
10:18:27,982 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.persistenceunit."sigems-ear-dme.ear/sigems-ihm-dme.war#blDpiPersistenceUnit": org.jboss.msc.service.StartException in service jboss.persistenceunit."sigems-ear-dme.ear/sigems-ihm-dme.war#blDpiPersistenceUnit": Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/D:/Developpement/Produits/DME/Tools/Server/jboss711/standalone/deployments/sigems-ear-dme.ear/sigems-ihm-dme.war/WEB-INF/classes/
at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:854)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:596)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:72)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
... 3 more
Caused by: java.lang.RuntimeException: JBAS011455: Missing PersistenceUnitMetadata (thread local wasn't set)
at org.jboss.as.jpa.hibernate4.HibernateAnnotationScanner.getClassesInJar(HibernateAnnotationScanner.java:208)
at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:484)
at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851)
... 9 more
Not sure what JBAS011455 is, but try to override the metadata by modifying the app bundled JBoss XML
Overriding metadata through XML

Error deploying EJBs in Wildfly 8 (JBOSS 8)

I am getting error when I am trying to deploy EJB in Wildfly 8. I am trying to place my ejb.ear file which contains (beans.jar file with all bean and remote classes and meta-inf folder with ejb-jar.xml and jboss.xml) in wildfly8/standalone/deployments folder.
It shows me all the module names and jndi names for all the bean files I have placed. But after showing following is the error I get.
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."ejbs.ear"."beans.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."ejbs.ear"."beans.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of subdeployment "beans.jar" of deployment "ejbs.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_55]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011058: Failed to install component ReportBean
at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:109)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
... 5 more
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.component.session.SessionBeanObjectViewConfigurator$2.configureDependency(SessionBeanObjectViewConfigurator.java:94)
at org.jboss.as.ejb3.component.session.SessionBeanObjectViewConfigurator$2.configureDependency(SessionBeanObjectViewConfigurator.java:91)
at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:151)
at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:101)
... 6 more
Can someone please help.
Thanks,
Jack.

War File with Webservice is not deployed in JBOSS EAP 6.2 in Standalone server

I tried to build a war file which contains web servicesm which deploys in JBOSS AS 5 and 6 without any issues.
But, in JBOSS EAP (Standalone) it gave me the following error.
I dont have any clue where to look for the error message.
18:20:56,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start
service jboss.deployment.unit."service.war".PARSE: org.jboss.msc.service.StartException in service j
boss.deployment.unit."service.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "s
ervice.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseServic
e.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.
java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746
) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1
.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1
.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resourc
e-adapter-name-service not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:4
48) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefau
ltResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:270)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processM
essageBeans(MessageDrivenComponentDescriptionFactory.java:152)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processA
nnotations(MessageDrivenComponentDescriptionFactory.java:80)
at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitPro
cessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:58)
at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDe
ploymentUnitProcessor.java:81)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseServic
e.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
... 5 more
18:20:56,245 ERROR [org.jboss.as.server] (HttpManagementService-threads - 2) JBAS015870: Deploy of d
eployment "service.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"service.war\".PARSE" => "org.jboss.msc.s
ervice.StartException in service jboss.deployment.unit.\"service.war\".PARSE: JBAS018733: Failed to
process phase PARSE of deployment \"service.war\"
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-res
ource-adapter-name-service not found"}}
18:20:59,072 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped dep
loyment service.war (runtime-name: service.war) in 2827ms
What is wrong with my deployment or with my application.
Its CXF, Hibernate, Spring and MY SQL jar file.
please help me.
You need to add the MDB resource to the EJB subsystem. The following needs to be added to the EJB3 subsystem in your XML configuration. There might be a way in CLI or the web console as well.
<mdb>
<resource-adapter-ref resource-adapter-name="hornetq-ra"/>
<bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
</mdb>

resteasy-spring module in jboss wildfly 8

I am having this problem with Wildfly 8 and resteasy-spring.jar (module). i am trying to deploy 2 wars on the same server, if i deploy 1 war it deploys fine, but whenever i add the second war it starts failing (and vice versa) with the following error:
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."TaskandTeamManager.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."TaskandTeamManager.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "TaskandTeamManager.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/C:/servers/jboss/wildfly-8.0.0.Final/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:126)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Final-SNAPSHOT.jar:8.0.0.Final-SNAPSHOT]
... 5 more
Caused by: java.io.IOException: VFS000017: Filesystem already mounted at mount point ""/C:/servers/jboss/wildfly-8.0.0.Final/modules/system/layers/base/org/jboss/resteasy/resteasy-spring/main/bundled/resteasy-spring.jar""
at org.jboss.vfs.VFS.mount(VFS.java:127)
at org.jboss.vfs.VFS.doMount(VFS.java:336)
at org.jboss.vfs.VFS.mountZip(VFS.java:360)
at org.jboss.as.jaxrs.deployment.JaxrsSpringProcessor.deploy(JaxrsSpringProcessor.java:119)
... 6 more
I already tried adding a dependencies in jboss-deployment-structure (META-INF), but i get the same error, both projects are using rest-easy and jackson dependencies.
Any help would be greatly appreciated
This is a bug. For now if you add the context param org.jboss.as.jaxrs.disableSpringIntegration=true to your application it should work around it.

How to solve hook deployment error on JBOSS AS7: Failed to process phase INSTALL of deployment

I am getting the following error (full stack-trace) when I try to deploy my TagsNavigation-hook.war:
14:04:37,562 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "TagsNavigation-hook.war"
14:04:37,589 INFO [org.jboss.as.jpa] (MSC service thread 1-1) added javax.persistence.api dependency to TagsNavigation-hook.war
14:04:37,596 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."TagsNavigation-hook.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."TagsNavigation-hook.war".INSTALL: Failed to process phase INSTALL of deployment "TagsNavigation-hook.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.runWorker(Unknown Source) [:1.7.0_04]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.7.0_04]
at java.lang.Thread.run(Unknown Source) [:1.7.0_04]
Caused by: java.lang.RuntimeException: Failed to load class com.liferay.taglib.portlet.NamespaceTag
at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:141)
at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:122)
at org.jboss.as.ee.component.LazyValue.get(LazyValue.java:40)
at org.jboss.as.ee.component.EEApplicationDescription.getClassConfiguration(EEApplicationDescription.java:183)
at org.jboss.as.ee.component.ComponentDescription.createConfiguration(ComponentDescription.java:153)
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:70)
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: java.lang.ClassNotFoundException: com.liferay.taglib.portlet.NamespaceTag from [Module "deployment.TagsNavigation-hook.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:361)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:333)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:310)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:103)
at java.lang.Class.forName0(Native Method) [:1.7.0_04]
at java.lang.Class.forName(Unknown Source) [:1.7.0_04]
at org.jboss.as.ee.component.deployers.EEClassConfigurationProcessor$1.compute(EEClassConfigurationProcessor.java:139)
... 11 more
This was working before, but is not working after I undeployed by directly deleting the TagsNavigation-hook.war from the location \liferay-portal-6.1.10-ee-ga1\jboss-7.0.2\standalone\deployments, on another Jboss server I undeployed through liferay's Control Panel --> Update Manager
I tried the following:
Renaming the file TagsNavigation-hook.war.failed to TagsNavigation-hook.war.dodeploy but still the same error.
Stopping the server, then change it to TagsNavigation-hook.war.dodeploy and then restart the server but still the same thing.
Completely deleting the TagsNavigation-hook.war and TagsNavigation-hook.war.failed files and then deploying it. I tried this as a hot deployment as well as by stopping the server --> deploying --> starting the server.
Other plugin deployments (themes, hooks and portlets) are working fine. And this hook is also working fine on Tomcat-7!
Environment: Liferay 6.1.10 EE bundled with JBOSS 7.0.2 on Linux
Now it is working.
I just added this property: portal-dependency-jars=util-taglib.jar inside liferay-plugin-package.properties and then deployed.
This feels quite strange because the hook works perfectly fine on tomcat without defining the property and only on Jboss it gave this error and that too only after I undeployed it.