9:16 a.m.
[
https://issues.jboss.org/browse/AS7-5224?page=com.atlassian.jira.plugin.s...
]
Tomaz Cerar commented on AS7-5224:
----------------------------------
And you know why are you using all this jvm options?
-XX:+UseCompressedOops -Xms1g -Xmx2g -XX:PermSize=256m -XX:MaxPermSize=256m
-XX:+UseConcMarkSweepGC -XX:+UseLargePages
you use -XX:+UseCompressedOops and -XX:+UseLargePages it would say something is wrong with
the way you view what parameters are needed.
first one tells jvm to compress all pointers so it would use less memory overhead for
small heaps, second tells jvm to use Large memory
and to use second parameter properly you need to configure kernel to enable it. Also your
log file (boot.log)
{noformat}Java HotSpot(TM) 64-Bit Server VM warning: Failed to reserve shared memory
(errno = 1).{noformat}
tells you there is something wrong with configuration for large pages...
my first suggestion would be to remove all unneeded parameters and then try again.
try with something like this, assuming you want to limit jvm to 2GB heap
{noformat}
-server -XX:+UseCompressedOops -Xms2g -Xmx2g -Djava.net.preferIPv4Stack=true
-Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000
{noformat}
i have also removed PermSize* params for start as you do not need as big permgens unless
you have really big application.
Plese note that jvm memory configurations should not be just copied over from jboss <7
as the way whole system works has changed significantly.
[JBoss 7.1.0.Final] High CPU usage for single-core CPU VMWare virtual
machine running Redhat 6 OS
-------------------------------------------------------------------------------------------------
Key: AS7-5224
URL: https://issues.jboss.org/browse/AS7-5224
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.1.0.Final
Environment: -bash-4.1$ cat /proc/version
Linux version 2.6.32-279.el6.x86_64 (mockbuild(a)x86-008.build.bos.redhat.com) (gcc version
4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Wed Jun 13 18:24:36 EDT 2012
-bash-4.1$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
stepping : 2
cpu MHz : 2666.761
cache size : 12288 KB
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36
clflush dts acpi mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc up arch_perfmon
pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf unfair_spinlock pni pclmulqdq ssse3
cx16 sse4_1 sse4_2 popcnt aes hypervisor lahf_lm ida arat epb dts
bogomips : 5333.52
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
-bash-4.1$ cat /proc/meminfo
MemTotal: 3925212 kB
MemFree: 328048 kB
Buffers: 21276 kB
Cached: 3268128 kB
SwapCached: 180 kB
Active: 1832808 kB
Inactive: 1475292 kB
Active(anon): 3104 kB
Inactive(anon): 16008 kB
Active(file): 1829704 kB
Inactive(file): 1459284 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 8388600 kB
SwapFree: 8387940 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 18624 kB
Mapped: 12656 kB
Shmem: 416 kB
Slab: 220480 kB
SReclaimable: 196296 kB
SUnreclaim: 24184 kB
KernelStack: 792 kB
PageTables: 6980 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 10351204 kB
Committed_AS: 102640 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 283176 kB
VmallocChunk: 34359452028 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 10240 kB
DirectMap2M: 4184064 kB
Reporter: Claudiu Muresan
Assignee: Jason Greene
Attachments: boot.log, jstack.thread.dump, process.args, standalone.conf,
standalone.xml, top
When starting JBoss server in standalone configuration we have 100% CPU usage.
There are no deployments.
Please view attached items: thread dump, standalone.conf, standalone.xml.
The JVM version is -bash-4.1$ ./java -version
java version "1.6.0_27"
Java(TM) SE Runtime Environment (build 1.6.0_27-b07)
Java HotSpot(TM) 64-Bit Server VM (build 20.2-b06, mixed mode)
.
Tried also with the latest JVM version (6u33) => high CPU usage.
Tried also with 7.1.1 Final and same configuration(standalone.conf/standalone.xml) =>
high CPU usage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira