July 2011 - jboss-dev-forums - Jboss List Archives

[JBoss AS7 Development] - JBoss AS7 defining Queues

by Baljit Singh

Baljit Singh [http://community.jboss.org/people/mrbaljit] created the discussion "JBoss AS7 defining Queues" To view the discussion, visit: http://community.jboss.org/message/613222#613222 -------------------------------------------------------------- Can someone please point me to documentation of defining jms queues and topics? Thanks Baljit -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/613222#613222] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 10 months

1
0
0 / 0

[JBoss AS7 Development] - AS 7 startup time showdown

by Takayuki Konishi

Takayuki Konishi [http://community.jboss.org/people/tkonishi] modified the document: "AS 7 startup time showdown" To view the document, visit: http://community.jboss.org/docs/DOC-16971 -------------------------------------------------------------- How fast does AS 7 start on your computer? This page is a crowdsourced benchmark to see what type of times people are getting. It could also give you an idea if it's time to upgrade your computer to more cores. Start-up times may vary sligtly between different runs, due to system load, filesystem caching etc. We are interested in your best times :) On with the showdown! Start JBoss AS 7 in standalone mode and add your results to this page. We are mostly interested in *stock JVM settings*, just to even the playing field. If you add flags, please note that in the JVM column. h3. AS 7 (Web Profile) || *Username* || *Processor / Chipset* || *RAM* || *HardDrive Speed* || *Operating System* || *JVM* || *Startup Time* || | dan.j.allen | 2x Intel Core 2 Duo E8400 3.00 GHz 32-bit | 4GB 800MHz | 7200 RPM | Ubuntu 11.04 i686 2.6.38-8 (pae) | OpenJDK 1.6.0_22 32-bit (stock settings) | 1726ms | | dan.j.allen | 2x Intel Core 2 Duo E8400 3.00 GHz 32-bit | 4GB 800MHz | 7200 RPM | Ubuntu 11.04 i686 2.6.38-8 (pae) | OpenJDK 1.6.0_22 32-bit (JVM flags Group A) | 970ms | | dan.j.allen | Quad i7-2620M 2.70GHz 64-bit | 8GB 1333MHz | 7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-Bit (stock settings) | 1590ms | | dan.j.allen | Quad i7-2620M 2.70GHz 64-bit | 8GB 1333MHz | 7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-Bit (JVM flags Group A) | 1293ms | | dan.j.allen | 2x Intel Core 2 Duo T7500 2.20 GHz 32-bit | 4GB 667MHz | 5200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | Java(TM) SE HotSpot Server VM 1.6.0_24-b07 | 2822ms | | dan.j.allen | 2x Intel Core 2 Duo T7500 2.20 GHz 32-bit | 4GB 667MHz | 5200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | Java(TM) SE HotSpot Server VM 1.6.0_24-b07 (JVM flags Group A) | 1589ms | | david bosschaert | Quad i7 2.2GHz 64-bit | 8G 1333MHz | 7200 RPM | Mac OS X 10.6.8 Darwin 10.8.0 x86_64 | Apple Java 1.6.0_26 | 1479ms | | david bosschaert | Quad i7 2.2GHz 64-bit | 8G 1333MHz | 7200 RPM | Mac OS X 10.6.8 Darwin 10.8.0 x86_64 | Apple Java 1.6.0_26 (JVM flags Group A) | 1189ms | | ssilvert | Intel ® Core™ 2 Duo i7-620M -i7 (2.66GHz, 4MB L3, 1066MHz FSB, 35W) | 8GB 1333MHz | 7200 RPM | Windows 7 Enterprise SP1 | Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) | 1813ms | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 1450ms | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (JVM flags Group B) | 1012ms | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | KVM Image Fedora 15 2.6.38.8-32.fc15.i686 on Fedora 15 x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-i686 (JVM flags Group A) | 1007ms | | jason.greene | i7 Dual Core @ 2.66 GHz | 8GB 1067MHZ | 7200 RPM | Mac OS X 10.6.8 (forced 64 bit kernel) | Apple Java 1.6.0_26 (-d32 bit mode) | 1486ms | | jason.greene | i7 Dual Core @ 2.66 GHz | 8GB 1067MHZ | 7200 RPM | Mac OS X 10.6.8 (forced 64 bit kernel) | Apple Java 1.6.0_26 (stock settings) | 2041ms | | goldmann | Intel Core i5 2.4 Ghz | 8GB 1067MHZ | 7200 RPM | Mac OS X 10.6.7 | Apple Java 1.6.0_26 (stock settings) | 2476ms | | wolfc | Intel Core i7 860 2.80 Ghz | 6GB 1333Mhz | RAID0 2x7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-bit | 1287ms (w. patch) | | mike.pellegrini | Intel Core i5 560 2.66 GHz | 4GB 1067MHz | 7200 RPM | Fedora Core 15 2.6.38.8-32.fc15.x86_64 | Java(TM) SE Runtime Environment (build 1.6.0_26-b03) | 1930ms | | tommysdk | Intel ® Core™ i5 CPU M560 @ 2.70 GHz 64-bit | 4GB 1333 MHz | 7200 RPM | Windows 7 Professional | Java(TM) SE Runtime Environment (build 1.6.0_23-b05) Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode) (JVM flags Group A tweaked) | 1877 ms | | sannegrinovero | i7 Dual Core @ 2.66 GHz | 8GB 1067MHZ | SSD Intel G2 | Fedora Core 15/64bit custom kernel 2.6.39.2 | Java(TM) SE Runtime Environment (build 1.6.0_25-b06) Options Group B | 1232ms | | kevin.sapper | Intel ® Core™ i7 CPU Q720 @ 1.60 GHz | 6GB 1333 MHz | 5600 RPM | Windows 7 Home | Java(TM) SE Runtime 64-Bit Environment (build 1.6.0_26-b03) Options Group A | 2098ms | | kevin.sapper | Intel ® Core™ i7 CPU Q720 @ 1.60 GHz | 6GB 1333 MHz | 5600 RPM | Windows 7 Home | Java(TM) SE Runtime 64-Bit Environment (build 1.6.0_26-b03) Options Group B | 1771ms | | dimitris | Intel Core i7 CPU Q740 @ 1.73GHz | 4G | SSD Samsung PM800 | Windows 7 Prol SP1 | java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing) | 1649ms | | mmiura | Six-Core AMD Opteron Processor 2435 @ 2.60GHz x2 | 24G | SSD Intel X25-M 80G | Fedora 14 2.6.35.13-92.fc14.x86_64 | java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.8) (fedora-53.1.9.8.fc14-x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) | 1507ms | | pgier | Intel® CoreTM 2 Duo i7-620M -i7 @ 2.66GHz | 4G | 7200 RPM | Fedora 13 2.6.34.8-68.fc13.i686 | Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode) | 1969ms | | tkonishi | Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz | 16G | SSD Crucial C300 128GB | Fedora 15 2.6.38.8-32.fc15.x86_64 | java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.2) (fedora-58.1.10.2.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)(JVM flags Group A) | 866ms | | tkonishi | Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz | 16G | SSD Crucial C300 128GB | Fedora 15 2.6.38.8-32.fc15.x86_64 | java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.2) (fedora-58.1.10.2.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) (JVM flags Group B) | 706ms | | tkonishi | Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz | 16G | SSD Crucial C300 128GB | Fedora 15 2.6.38.8-32.fc15.x86_64 | java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.2) (fedora-58.1.10.2.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) (stock settings) | 1039ms | h3. Older AS Versions || *Username* || *Processor / Chipset* || *RAM* || *HardDrive Speed* || *Operating System* || *JVM* || *AS Version* || *Startup Time* || | dan.j.allen | 2x Intel Core 2 Duo E8400 3.00 GHz 32-bit | 4GB 800MHz | 7200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | OpenJDK 1.6.0_22 32-Bit (stock settings) | 6.0.0.Final | 14.5s | | dan.j.allen | Quad i7-2620M 2.70GHz 64-bit | 8GB 1333MHz | 7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-Bit (stock settings) | 6.0.0.Final | 13s | | dan.j.allen | 2x Intel Core 2 Duo T7500 2.20 GHz 32-bit | 4GB 667MHz | 5200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | Java(TM) SE HotSpot Server VM 1.6.0_24-b07 | 6.0.0.Final | 21.88s | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 6.0.0.Final | 12.0s | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 5.1.0.GA | 19.0s | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 4.2.3.GA | 6.2s | | mike.pellegrini | Intel Core i5 560 2.66 GHz | 4GB 1067MHz | 7200 RPM | Fedora Core 15 2.6.38.8-32.fc15.x86_64 | Java(TM) SE Runtime Environment (build 1.6.0_26-b03) | 5.1.0 | 23s. | h3. JVM flag legend (for table above) * *Group A*: -Xms64m -Xmx512m -XX:MaxPermSize=256m -client -Xverify:none -XX:+UseFastAccessorMethods -XX:+DisableExplicitGC -XX:+UseCompressedOops * *Group B*: -server -Xms128m -Xmx128m -XX:MaxPermSize=128m -Djava.net.preferIPv4Stack=true -XX:+UseFastAccessorMethods -XX:+TieredCompilation -Xverify:none h3. Optimizations You get better startup times with 32 bit over 64 bit, because of the smaller integer size. If you are on a 64 bit machine, you can do one of two things to get 32 bit performance: * Run in 32 bit mode using the JVM flag: -d32 (Mac and Windows) * Use the JVM compression flag: -XX:+UseCompressedOops (option not valid on a 32 bit JVM) There are also some other JVM flags that will speed things up: * -noverify * -XX:+DisableExplicitGC * -client (32 bit JVM only. You have to edit standalone.sh to use -client instead of -server) You can squeeze out a few fractions of a second by disabling the console logging (or directing it to /dev/null): ./standalone.sh > /dev/null You can still view the log output by tailing the server log. See comments for other suggestions. Let the best machine win! -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-16971] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

12 years, 10 months

1
0
0 / 0

[JBoss AS7 Development] - AS 7 startup time showdown

by Takayuki Konishi

Takayuki Konishi [http://community.jboss.org/people/tkonishi] modified the document: "AS 7 startup time showdown" To view the document, visit: http://community.jboss.org/docs/DOC-16971 -------------------------------------------------------------- How fast does AS 7 start on your computer? This page is a crowdsourced benchmark to see what type of times people are getting. It could also give you an idea if it's time to upgrade your computer to more cores. Start-up times may vary sligtly between different runs, due to system load, filesystem caching etc. We are interested in your best times :) On with the showdown! Start JBoss AS 7 in standalone mode and add your results to this page. We are mostly interested in *stock JVM settings*, just to even the playing field. If you add flags, please note that in the JVM column. h3. AS 7 (Web Profile) || *Username* || *Processor / Chipset* || *RAM* || *HardDrive Speed* || *Operating System* || *JVM* || *Startup Time* || | dan.j.allen | 2x Intel Core 2 Duo E8400 3.00 GHz 32-bit | 4GB 800MHz | 7200 RPM | Ubuntu 11.04 i686 2.6.38-8 (pae) | OpenJDK 1.6.0_22 32-bit (stock settings) | 1726ms | | dan.j.allen | 2x Intel Core 2 Duo E8400 3.00 GHz 32-bit | 4GB 800MHz | 7200 RPM | Ubuntu 11.04 i686 2.6.38-8 (pae) | OpenJDK 1.6.0_22 32-bit (JVM flags Group A) | 970ms | | dan.j.allen | Quad i7-2620M 2.70GHz 64-bit | 8GB 1333MHz | 7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-Bit (stock settings) | 1590ms | | dan.j.allen | Quad i7-2620M 2.70GHz 64-bit | 8GB 1333MHz | 7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-Bit (JVM flags Group A) | 1293ms | | dan.j.allen | 2x Intel Core 2 Duo T7500 2.20 GHz 32-bit | 4GB 667MHz | 5200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | Java(TM) SE HotSpot Server VM 1.6.0_24-b07 | 2822ms | | dan.j.allen | 2x Intel Core 2 Duo T7500 2.20 GHz 32-bit | 4GB 667MHz | 5200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | Java(TM) SE HotSpot Server VM 1.6.0_24-b07 (JVM flags Group A) | 1589ms | | david bosschaert | Quad i7 2.2GHz 64-bit | 8G 1333MHz | 7200 RPM | Mac OS X 10.6.8 Darwin 10.8.0 x86_64 | Apple Java 1.6.0_26 | 1479ms | | david bosschaert | Quad i7 2.2GHz 64-bit | 8G 1333MHz | 7200 RPM | Mac OS X 10.6.8 Darwin 10.8.0 x86_64 | Apple Java 1.6.0_26 (JVM flags Group A) | 1189ms | | ssilvert | Intel ® Core™ 2 Duo i7-620M -i7 (2.66GHz, 4MB L3, 1066MHz FSB, 35W) | 8GB 1333MHz | 7200 RPM | Windows 7 Enterprise SP1 | Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) | 1813ms | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 1450ms | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (JVM flags Group B) | 1012ms | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | KVM Image Fedora 15 2.6.38.8-32.fc15.i686 on Fedora 15 x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-i686 (JVM flags Group A) | 1007ms | | jason.greene | i7 Dual Core @ 2.66 GHz | 8GB 1067MHZ | 7200 RPM | Mac OS X 10.6.8 (forced 64 bit kernel) | Apple Java 1.6.0_26 (-d32 bit mode) | 1486ms | | jason.greene | i7 Dual Core @ 2.66 GHz | 8GB 1067MHZ | 7200 RPM | Mac OS X 10.6.8 (forced 64 bit kernel) | Apple Java 1.6.0_26 (stock settings) | 2041ms | | goldmann | Intel Core i5 2.4 Ghz | 8GB 1067MHZ | 7200 RPM | Mac OS X 10.6.7 | Apple Java 1.6.0_26 (stock settings) | 2476ms | | wolfc | Intel Core i7 860 2.80 Ghz | 6GB 1333Mhz | RAID0 2x7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-bit | 1287ms (w. patch) | | mike.pellegrini | Intel Core i5 560 2.66 GHz | 4GB 1067MHz | 7200 RPM | Fedora Core 15 2.6.38.8-32.fc15.x86_64 | Java(TM) SE Runtime Environment (build 1.6.0_26-b03) | 1930ms | | tommysdk | Intel ® Core™ i5 CPU M560 @ 2.70 GHz 64-bit | 4GB 1333 MHz | 7200 RPM | Windows 7 Professional | Java(TM) SE Runtime Environment (build 1.6.0_23-b05) Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode) (JVM flags Group A tweaked) | 1877 ms | | sannegrinovero | i7 Dual Core @ 2.66 GHz | 8GB 1067MHZ | SSD Intel G2 | Fedora Core 15/64bit custom kernel 2.6.39.2 | Java(TM) SE Runtime Environment (build 1.6.0_25-b06) Options Group B | 1232ms | | kevin.sapper | Intel ® Core™ i7 CPU Q720 @ 1.60 GHz | 6GB 1333 MHz | 5600 RPM | Windows 7 Home | Java(TM) SE Runtime 64-Bit Environment (build 1.6.0_26-b03) Options Group A | 2098ms | | kevin.sapper | Intel ® Core™ i7 CPU Q720 @ 1.60 GHz | 6GB 1333 MHz | 5600 RPM | Windows 7 Home | Java(TM) SE Runtime 64-Bit Environment (build 1.6.0_26-b03) Options Group B | 1771ms | | dimitris | Intel Core i7 CPU Q740 @ 1.73GHz | 4G | SSD Samsung PM800 | Windows 7 Prol SP1 | java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing) | 1649ms | | mmiura | Six-Core AMD Opteron Processor 2435 @ 2.60GHz x2 | 24G | SSD Intel X25-M 80G | Fedora 14 2.6.35.13-92.fc14.x86_64 | java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.8) (fedora-53.1.9.8.fc14-x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) | 1507ms | | pgier | Intel® CoreTM 2 Duo i7-620M -i7 @ 2.66GHz | 4G | 7200 RPM | Fedora 13 2.6.34.8-68.fc13.i686 | Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode) | 1969ms | | tkonishi | Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz | 16G | SSD Crucial C300 128GB | Fedora 15 2.6.38.8-32.fc15.x86_64 | java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.2) (fedora-58.1.10.2.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)(JVM flags Group A) | 866ms | | tkonishi | Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz | 16G | SSD Crucial C300 128GB | Fedora 15 2.6.38.8-32.fc15.x86_64 | java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.2) (fedora-58.1.10.2.fc15-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) (JVM flags Group B) | 706ms | | | | | | | | | h3. Older AS Versions || *Username* || *Processor / Chipset* || *RAM* || *HardDrive Speed* || *Operating System* || *JVM* || *AS Version* || *Startup Time* || | dan.j.allen | 2x Intel Core 2 Duo E8400 3.00 GHz 32-bit | 4GB 800MHz | 7200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | OpenJDK 1.6.0_22 32-Bit (stock settings) | 6.0.0.Final | 14.5s | | dan.j.allen | Quad i7-2620M 2.70GHz 64-bit | 8GB 1333MHz | 7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-Bit (stock settings) | 6.0.0.Final | 13s | | dan.j.allen | 2x Intel Core 2 Duo T7500 2.20 GHz 32-bit | 4GB 667MHz | 5200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | Java(TM) SE HotSpot Server VM 1.6.0_24-b07 | 6.0.0.Final | 21.88s | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 6.0.0.Final | 12.0s | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 5.1.0.GA | 19.0s | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 4.2.3.GA | 6.2s | | mike.pellegrini | Intel Core i5 560 2.66 GHz | 4GB 1067MHz | 7200 RPM | Fedora Core 15 2.6.38.8-32.fc15.x86_64 | Java(TM) SE Runtime Environment (build 1.6.0_26-b03) | 5.1.0 | 23s. | h3. JVM flag legend (for table above) * *Group A*: -Xms64m -Xmx512m -XX:MaxPermSize=256m -client -Xverify:none -XX:+UseFastAccessorMethods -XX:+DisableExplicitGC -XX:+UseCompressedOops * *Group B*: -server -Xms128m -Xmx128m -XX:MaxPermSize=128m -Djava.net.preferIPv4Stack=true -XX:+UseFastAccessorMethods -XX:+TieredCompilation -Xverify:none h3. Optimizations You get better startup times with 32 bit over 64 bit, because of the smaller integer size. If you are on a 64 bit machine, you can do one of two things to get 32 bit performance: * Run in 32 bit mode using the JVM flag: -d32 (Mac and Windows) * Use the JVM compression flag: -XX:+UseCompressedOops (option not valid on a 32 bit JVM) There are also some other JVM flags that will speed things up: * -noverify * -XX:+DisableExplicitGC * -client (32 bit JVM only. You have to edit standalone.sh to use -client instead of -server) You can squeeze out a few fractions of a second by disabling the console logging (or directing it to /dev/null): ./standalone.sh > /dev/null You can still view the log output by tailing the server log. See comments for other suggestions. Let the best machine win! -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-16971] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

12 years, 10 months

1
0
0 / 0

[jBPM Development] - Fault Node -> Exception Handler not being invoked

by Amin MC

Amin MC [http://community.jboss.org/people/aminmc] created the discussion "Fault Node -> Exception Handler not being invoked" To view the discussion, visit: http://community.jboss.org/message/613151#613151 -------------------------------------------------------------- Hi, I have the following graph: http://community.jboss.org/servlet/JiveServlet/showImage/2-613151-16646/E... http://community.jboss.org/servlet/JiveServlet/downloadImage/2-613151-166... After the Raise Fault node I use a fault node with the name "MyError". I then register an Exception Handler (process level): MyError = kcontext.getProcessInstance().signalEvent("fault", *null*); According to the docs "if no exception handler can be found, the process instance will be aborted, resulting in the cancellation of all nodes inside the process". What I am noticing is that the fault node is triggered but my exception handler is not being invoked as a result the process is terminated. Is there something I am missing? I have looked at the existing examples "BPMN2-ErrorBoundaryEventInterrupting.bpmn2" which i've tried to modify but still no success in that my custom exception handler is never invoked. I presume that if a custom exception handler is found the process will not terminate? Any help would be appreciated. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/613151#613151] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 10 months

1
0
0 / 0

[JBoss AS7 Development] - Re: Authentication issue in AS7

by Anil Saldhana

Anil Saldhana [http://community.jboss.org/people/anil.saldhana] created the discussion "Re: Authentication issue in AS7" To view the discussion, visit: http://community.jboss.org/message/612134#612134 -------------------------------------------------------------- Rich, we need to take a look at this. The DB login module can utilize a transaction manager from the app server. We need to evaluate the proper TM semantics for AS7. Let me get back to you. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/612134#612134] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 10 months

2
1
0 / 0

[JBoss AS7 Development] - AS 7 startup time showdown

by Paul Gier

Paul Gier [http://community.jboss.org/people/pgier] modified the document: "AS 7 startup time showdown" To view the document, visit: http://community.jboss.org/docs/DOC-16971 -------------------------------------------------------------- How fast does AS 7 start on your computer? This page is a crowdsourced benchmark to see what type of times people are getting. It could also give you an idea if it's time to upgrade your computer to more cores. Start-up times may vary sligtly between different runs, due to system load, filesystem caching etc. We are interested in your best times :) On with the showdown! Start JBoss AS 7 in standalone mode and add your results to this page. We are mostly interested in *stock JVM settings*, just to even the playing field. If you add flags, please note that in the JVM column. h3. AS 7 (Web Profile) || *Username* || *Processor / Chipset* || *RAM* || *HardDrive Speed* || *Operating System* || *JVM* || *Startup Time* || | dan.j.allen | 2x Intel Core 2 Duo E8400 3.00 GHz 32-bit | 4GB 800MHz | 7200 RPM | Ubuntu 11.04 i686 2.6.38-8 (pae) | OpenJDK 1.6.0_22 32-bit (stock settings) | 1726ms | | dan.j.allen | 2x Intel Core 2 Duo E8400 3.00 GHz 32-bit | 4GB 800MHz | 7200 RPM | Ubuntu 11.04 i686 2.6.38-8 (pae) | OpenJDK 1.6.0_22 32-bit (JVM flags Group A) | 970ms | | dan.j.allen | Quad i7-2620M 2.70GHz 64-bit | 8GB 1333MHz | 7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-Bit (stock settings) | 1590ms | | dan.j.allen | Quad i7-2620M 2.70GHz 64-bit | 8GB 1333MHz | 7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-Bit (JVM flags Group A) | 1293ms | | dan.j.allen | 2x Intel Core 2 Duo T7500 2.20 GHz 32-bit | 4GB 667MHz | 5200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | Java(TM) SE HotSpot Server VM 1.6.0_24-b07 | 2822ms | | dan.j.allen | 2x Intel Core 2 Duo T7500 2.20 GHz 32-bit | 4GB 667MHz | 5200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | Java(TM) SE HotSpot Server VM 1.6.0_24-b07 (JVM flags Group A) | 1589ms | | david bosschaert | Quad i7 2.2GHz 64-bit | 8G 1333MHz | 7200 RPM | Mac OS X 10.6.8 Darwin 10.8.0 x86_64 | Apple Java 1.6.0_26 | 1479ms | | david bosschaert | Quad i7 2.2GHz 64-bit | 8G 1333MHz | 7200 RPM | Mac OS X 10.6.8 Darwin 10.8.0 x86_64 | Apple Java 1.6.0_26 (JVM flags Group A) | 1189ms | | ssilvert | Intel ® Core™ 2 Duo i7-620M -i7 (2.66GHz, 4MB L3, 1066MHz FSB, 35W) | 8GB 1333MHz | 7200 RPM | Windows 7 Enterprise SP1 | Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) | 1813ms | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 1450ms | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (JVM flags Group B) | 1012ms | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | KVM Image Fedora 15 2.6.38.8-32.fc15.i686 on Fedora 15 x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-i686 (JVM flags Group A) | 1007ms | | jason.greene | i7 Dual Core @ 2.66 GHz | 8GB 1067MHZ | 7200 RPM | Mac OS X 10.6.8 (forced 64 bit kernel) | Apple Java 1.6.0_26 (-d32 bit mode) | 1486ms | | jason.greene | i7 Dual Core @ 2.66 GHz | 8GB 1067MHZ | 7200 RPM | Mac OS X 10.6.8 (forced 64 bit kernel) | Apple Java 1.6.0_26 (stock settings) | 2041ms | | goldmann | Intel Core i5 2.4 Ghz | 8GB 1067MHZ | 7200 RPM | Mac OS X 10.6.7 | Apple Java 1.6.0_26 (stock settings) | 2476ms | | wolfc | Intel Core i7 860 2.80 Ghz | 6GB 1333Mhz | RAID0 2x7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-bit | 1287ms (w. patch) | | mike.pellegrini | Intel Core i5 560 2.66 GHz | 4GB 1067MHz | 7200 RPM | Fedora Core 15 2.6.38.8-32.fc15.x86_64 | Java(TM) SE Runtime Environment (build 1.6.0_26-b03) | 1930ms | | tommysdk | Intel ® Core™ i5 CPU M560 @ 2.70 GHz 64-bit | 4GB 1333 MHz | 7200 RPM | Windows 7 Professional | Java(TM) SE Runtime Environment (build 1.6.0_23-b05) Java HotSpot(TM) 64-Bit Server VM (build 19.0-b09, mixed mode) (JVM flags Group A tweaked) | 1877 ms | | sannegrinovero | i7 Dual Core @ 2.66 GHz | 8GB 1067MHZ | SSD Intel G2 | Fedora Core 15/64bit custom kernel 2.6.39.2 | Java(TM) SE Runtime Environment (build 1.6.0_25-b06) Options Group B | 1232ms | | kevin.sapper | Intel ® Core™ i7 CPU Q720 @ 1.60 GHz | 6GB 1333 MHz | 5600 RPM | Windows 7 Home | Java(TM) SE Runtime 64-Bit Environment (build 1.6.0_26-b03) Options Group A | 2098ms | | kevin.sapper | Intel ® Core™ i7 CPU Q720 @ 1.60 GHz | 6GB 1333 MHz | 5600 RPM | Windows 7 Home | Java(TM) SE Runtime 64-Bit Environment (build 1.6.0_26-b03) Options Group B | 1771ms | | dimitris | Intel Core i7 CPU Q740 @ 1.73GHz | 4G | SSD Samsung PM800 | Windows 7 Prol SP1 | java version "1.6.0_24" Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing) | 1649ms | | mmiura | Six-Core AMD Opteron Processor 2435 @ 2.60GHz x2 | 24G | SSD Intel X25-M 80G | Fedora 14 2.6.35.13-92.fc14.x86_64 | java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.8) (fedora-53.1.9.8.fc14-x86_64) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) | 1507ms | | pgier | Intel® CoreTM 2 Duo i7-620M -i7 @ 2.66GHz | 4G | 7200 RPM | Fedora 13 2.6.34.8-68.fc13.i686 | Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode) | 1969ms | | | | | | | | | h3. Older AS Versions || *Username* || *Processor / Chipset* || *RAM* || *HardDrive Speed* || *Operating System* || *JVM* || *AS Version* || *Startup Time* || | dan.j.allen | 2x Intel Core 2 Duo E8400 3.00 GHz 32-bit | 4GB 800MHz | 7200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | OpenJDK 1.6.0_22 32-Bit (stock settings) | 6.0.0.Final | 14.5s | | dan.j.allen | Quad i7-2620M 2.70GHz 64-bit | 8GB 1333MHz | 7200 RPM | Ubuntu 11.04 x86_64 2.6.38-8 | OpenJDK 1.6.0_22 64-Bit (stock settings) | 6.0.0.Final | 13s | | dan.j.allen | 2x Intel Core 2 Duo T7500 2.20 GHz 32-bit | 4GB 667MHz | 5200 RPM | Ubuntu 10.10 i686 2.6.35-28 (pae) | Java(TM) SE HotSpot Server VM 1.6.0_24-b07 | 6.0.0.Final | 21.88s | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 6.0.0.Final | 12.0s | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 5.1.0.GA | 19.0s | | tkimura | Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz | 8GB 1333MHz | 7200 RPM | Fedora 15 2.6.38.8-32.fc15.x86_64 | OpenJDK 1.6.0_22 fedora-58.1.10.2.fc15-x86_64 (stock settings) | 4.2.3.GA | 6.2s | | mike.pellegrini | Intel Core i5 560 2.66 GHz | 4GB 1067MHz | 7200 RPM | Fedora Core 15 2.6.38.8-32.fc15.x86_64 | Java(TM) SE Runtime Environment (build 1.6.0_26-b03) | 5.1.0 | 23s. | h3. JVM flag legend (for table above) * *Group A*: -Xms64m -Xmx512m -XX:MaxPermSize=256m -client -Xverify:none -XX:+UseFastAccessorMethods -XX:+DisableExplicitGC -XX:+UseCompressedOops * *Group B*: -server -Xms128m -Xmx128m -XX:MaxPermSize=128m -Djava.net.preferIPv4Stack=true -XX:+UseFastAccessorMethods -XX:+TieredCompilation -Xverify:none h3. Optimizations You get better startup times with 32 bit over 64 bit, because of the smaller integer size. If you are on a 64 bit machine, you can do one of two things to get 32 bit performance: * Run in 32 bit mode using the JVM flag: -d32 (Mac and Windows) * Use the JVM compression flag: -XX:+UseCompressedOops (option not valid on a 32 bit JVM) There are also some other JVM flags that will speed things up: * -noverify * -XX:+DisableExplicitGC * -client (32 bit JVM only. You have to edit standalone.sh to use -client instead of -server) You can squeeze out a few fractions of a second by disabling the console logging (or directing it to /dev/null): ./standalone.sh > /dev/null You can still view the log output by tailing the server log. See comments for other suggestions. Let the best machine win! -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-16971] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

12 years, 10 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - AS 7 startup time showdown

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene] commented on the document "AS 7 startup time showdown" To view all comments on this document, visit: http://community.jboss.org/docs/DOC-16971#comment-6946 -------------------------------------------------- We do cache static module package indexes after the first boot. Caching deployment annotation indexes was slays planned but we just didn't get to it. It's a couple hours of work. Also the fact that our standalone script prevents -client is a bug we should let people do that. Feel free to hack the scripts. --------------------------------------------------

12 years, 10 months

1
0
0 / 0

Re: [jboss-dev-forums] [JBoss AS7 Development] - AS 7 startup time showdown

by Jason Greene

Jason Greene [http://community.jboss.org/people/jason.greene] commented on the document "AS 7 startup time showdown" To view all comments on this document, visit: http://community.jboss.org/docs/DOC-16971#comment-6945 -------------------------------------------------- UseCompressedStrings is what you are thinking of Dan UseCompressedOops is just the 32bit ptr optimization --------------------------------------------------

12 years, 10 months

1
0
0 / 0

[JBoss AS7 Development] - Generic type CLI commands

by Alexey Loubyansky

Alexey Loubyansky [http://community.jboss.org/people/aloubyansky] modified the document: "Generic type CLI commands" To view the document, visit: http://community.jboss.org/docs/DOC-16981 -------------------------------------------------------------- A type generic command is a command that is assigned to a specific node type and which allows to perform any operation and/or modify any of the properties exposed by the type on any existing instance of that type. For example, suppose there is a generic type command assigned to type /subsystem=datasources/data-source which is named data-source. Now using data-source command we can invoke any operation available for children of /subsystem=datasources/data-source and modify any of their properties (that have access-type read-write). The only thing left is to identify the target datasource we want to apply the action to. This is done by choosing one of the properties of the type as the identifying property. In case of this example, for datasources it could be, e.g., the jndi-name. Now you can invoke operations on data sources like this [standalone@localhost:9999 /] data-source flush-all-connection-in-pool --jndi-name=myds flush-all-connection-in-pool is an operation name which is exposed by the management model for all datasources and jndi-name argument identifies the datasource flush-all-connection-in-pool should be performed on. If the operation we want to perform requires properties, the properties can be added as command line arguments, i.e. here is an example of adding a new datasource [standalone@localhost:9999 /] data-source add --jndi-name=myds --driver-name=h2 --pool-name=myds-pool --connection-url=curl add is an operation name and the argument names match the operation property names prefixed with '--'. Node properties can be modified in a similar way. Property names prefixed with '--' become arguments names. Except here we don't need an operation name, just the identifying property, i.e. the jndi-name in our case (which is a read-only property). E.g. [standalone@localhost:9999 /] data-source --jndi-name=myds --min-pool-size=11 --max-pool-size=22 The examples above are actually for standalone mode. In domain mode, for the commands above to work they need one more argument - --profile. E.g. [standalone@localhost:9999 /] data-source --profile=default --jndi-name=myds --min-pool-size=11 --max-pool-size=22 h3. Getting help Generic type commands support --help option. The help content is fetched from the management model and is based on the description of the node type, operations and properties it exposes. E.g. the following will print the description of the type [standalone@localhost:9999 /] data-source --help A jdbc data-source configuration The following wil list all the properties and their descriptions (datasources hava lots of properties, so I'll paste only an exerpt here) [standalone@localhost:9999 /] data-source --help --properties connection-url - (required) The JDBC driver connection URL driver-class - (required) The fully qualifed name of the JDBC driver class jndi-name - (required) Specifies the JNDI name for the datasource new-connection-sql - (optional) Specifies an SQL statement to execute whenever a connection is added to the connection pool. And this is how to list the operations that can be invoked on an instance of the type (btw, this list excludes some operations like read-attribute, read-children-names, read-children-resources, read-children-types, read-operation-description, read-operation-names, read-resource, read-resource-description, validate-address, write-attribute) [standalone@localhost:9999 /] data-source --help --commands add disable enable flush-all-connection-in-pool flush-idle-connection-in-pool remove test-connection-in-pool To read the description of a specific command execute 'data-source command_name --help'. Here is an example of add operation description (again, it accepts a lot of properties, most of which are optional, so I paste only an exerpt of the complete description here) [standalone@localhost:9999 /] data-source add --help Operation description: Adds a new data-source Properties: --connection-url - (STRING,required) The JDBC driver connection URL --driver-class - (STRING,required) The fully qualifed name of the JDBC driver class --jndi-name - (STRING,required) Specifies the JNDI name for the datasource --driver-name - (STRING,required) Defines the JDBC driver the datasource should use. It is a symbolic name matching the the name of installed driver. In case the driver is deployed as jar, the name is the name of deployment unit --new-connection-sql - (STRING,optional) Specifies an SQL statement to execute whenever a connection is added to the connection pool. h3. Managing commands Generic type commands can be added and removed at runtime. There is a command called 'command' which can add new, list and remove existing generic type commands (but not other commands). For example [standalone@localhost:9999 /] command list data-source To add a new command, you need to identify the node type, choose the identifying property and the name for the command. E.g. [standalone@localhost:9999 /] command add --node-type=subsystem=resource-adapters/resource-adapter --property-id=archive --command-name=resource-adapter [standalone@localhost:9999 /] command list data-source resource-adapter Now there is resource-adapter command which can be used as any other CLI command, e.g. [standalone@localhost:9999 /] resource-adapter --help --commands add flush-all-connection-in-pool flush-idle-connection-in-pool remove test-connection-in-pool To read the description of a specific command execute 'resource-adapter command_name --help'. The command can be remove like this [standalone@localhost:9999 /] command remove --command-name=resource-adapter [standalone@localhost:9999 /] command list data-source NOTE: chnages made to generic type commands don't survive CLI restart yet. -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-16981] Create a new document in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

12 years, 10 months

1
0
0 / 0

[PicketBox Development] - Loading many policy sets from the code

by john john

john john [http://community.jboss.org/people/john78] created the discussion "Loading many policy sets from the code" To view the discussion, visit: http://community.jboss.org/message/612980#612980 -------------------------------------------------------------- Hi, Is it possible to load many policy sets from the code instead dynamicall from a file (as it is described http://community.jboss.org/docs/DOC-16676 http://community.jboss.org/wiki/XACMLRBACLocator). When I try: XACMLPolicy ps1 = PolicyFactory.createPolicySet(new FileInputStream(new File("ps1"))); XACMLPolicy ps2 = PolicyFactory.createPolicySet(new FileInputStream(new File("ps2"))); HashSet<XACMLPolicy> policies = new HashSet<XACMLPolicy>(); policies.add(ps1); policies.add(ps2); PolicyFinder pf = new PolicyFinder(); JBossPolicySetLocator psl = new JBossPolicySetLocator(); psl.setPolicies(policies); RequestContext req1 = RequestResponseContextFactory.createRequestCtx(); req1.readRequest(new FileInputStream(new File("req.xml"))); JBossPDP pdp = new JBossPDP(); ResponseContext resp1 = pdp.evaluate(req1); I get: 2011-07-01 15:18:05 org.jboss.security.xacml.sunxacml.finder.PolicyFinder findPolicy INFO: More than one top-level applicable policy for the request independently on what are the attributes which specify the roles within these two policy sets. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/612980#612980] Start a new discussion in PicketBox Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums July 2011