Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Major
Fix Version/s: 3.6.0.Final
Affects Version/s: 3.4.0.Final, 3.5.0.Final
Component/s: Performance
Labels:
None
Environment:

Hide

DEBUG 320 as.config Configured system properties:
file.encoding = Cp1252
java.class.path = C:\Home\JBoss\EAP61\jboss-eap-6.1\jboss-modules.jar
java.class.version = 51.0
java.home = C:\Program Files\Java\jdk1.7.0_13\jre
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = 1.7.0_13-b20
java.specification.vendor = Oracle Corporation
java.vm.name = Java HotSpot(TM) 64-Bit Server VM
java.vm.version = 23.7-b01
jboss.bind.address = localhost
jboss.home.dir = C:\Home\JBoss\EAP61\jboss-eap-6.1
jboss.modules.system.pkgs = org.jboss.byteman
jboss.server.base.dir = C:\Home\JBoss\EAP61\jboss-eap-6.1\standalone
os.name = Windows 7
os.version = 6.1
sun.java.command = org.jboss.modules.Main -mp C:/Home/JBoss/EAP61/jboss-eap-6.1/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml

DEBUG 324 as.config VM Arguments: -Dprogram.name=JBossTools: JBoss EAP 6.1 MS 3.5 Server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Home/JBoss/EAP61/jboss-eap-6.1/standalone/log/boot.log -Dlogging.configuration=file:/C:/Home/JBoss/EAP61/jboss-eap-6.1/standalone/configuration/logging.properties -Djboss.home.dir=C:/Home/JBoss/EAP61/jboss-eap-6.1 -Dorg.jboss.logmanager.nocolor=true -Dfile.encoding=Cp1252

Show
DEBUG 320 as.config Configured system properties: file.encoding = Cp1252 java.class.path = C:\Home\JBoss\EAP61\jboss-eap-6.1\jboss-modules.jar java.class.version = 51.0 java.home = C:\Program Files\Java\jdk1.7.0_13\jre java.runtime.name = Java(TM) SE Runtime Environment java.runtime.version = 1.7.0_13-b20 java.specification.vendor = Oracle Corporation java.vm.name = Java HotSpot(TM) 64-Bit Server VM java.vm.version = 23.7-b01 jboss.bind.address = localhost jboss.home.dir = C:\Home\JBoss\EAP61\jboss-eap-6.1 jboss.modules.system.pkgs = org.jboss.byteman jboss.server.base.dir = C:\Home\JBoss\EAP61\jboss-eap-6.1\standalone os.name = Windows 7 os.version = 6.1 sun.java.command = org.jboss.modules.Main -mp C:/Home/JBoss/EAP61/jboss-eap-6.1/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml DEBUG 324 as.config VM Arguments: -Dprogram.name=JBossTools: JBoss EAP 6.1 MS 3.5 Server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Home/JBoss/EAP61/jboss-eap-6.1/standalone/log/boot.log -Dlogging.configuration= file:/C:/Home/JBoss/EAP61/jboss-eap-6.1/standalone/configuration/logging.properties -Djboss.home.dir=C:/Home/JBoss/EAP61/jboss-eap-6.1 -Dorg.jboss.logmanager.nocolor=true -Dfile.encoding=Cp1252

Steps to Reproduce:
Hide

Create a JBoss EAP 6.1 instance, with the configuration https://github.com/vrolijken/ModeshapePerformance/blob/master/ModeshapePerformance/WebContent/standalone.xml

Deploy the war (https://github.com/vrolijken/ModeshapePerformance/blob/master/ModeshapePerformance/WebContent/ModeshapePerformance.war) in that server

Start the server

Using JMeter, load https://github.com/vrolijken/ModeshapePerformance/blob/master/ModeshapePerformance/WebContent/Simple.jmx

Using 20 threads, 10 iterations, the first request will usually fail (first 3, but second and third are a consequence of the first one failing)

Sometimes more requests fail, sometimes not. Though it is the first request that fails, this does not seem to occur when using 1 JMeter thread.
Show
Create a JBoss EAP 6.1 instance, with the configuration https://github.com/vrolijken/ModeshapePerformance/blob/master/ModeshapePerformance/WebContent/standalone.xml Deploy the war ( https://github.com/vrolijken/ModeshapePerformance/blob/master/ModeshapePerformance/WebContent/ModeshapePerformance.war ) in that server Start the server Using JMeter, load https://github.com/vrolijken/ModeshapePerformance/blob/master/ModeshapePerformance/WebContent/Simple.jmx Using 20 threads, 10 iterations, the first request will usually fail (first 3, but second and third are a consequence of the first one failing) Sometimes more requests fail, sometimes not. Though it is the first request that fails, this does not seem to occur when using 1 JMeter thread.

I created a war with the simplest instance of this bug I could think of in https://github.com/vrolijken/ModeshapePerformance. When a new node is saved, it can't always be found immediately after. This seems to happen most right after server startup.

Assignee:: Horia Chiorean (Inactive)

Reporter:: Friso V (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2013/09/20 9:36 AM

Updated:: 2021/10/24 5:22 AM

Resolved:: 2013/09/23 9:49 AM

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates