Monday, October 07, 2019
Add value by removing waste!
Today I had to stay at home from work since my daughter is sick from school, poor thing. But since I had some time over I found my old blog, very interesting reading old posts about JBoss and EJB3 from 2007. Thought it could be fun to publish something new since the last post was posted in 2014. So I made it easy for myself and linked this post to another blog I wrote some years ago :), which is about removing waste. Go ahead and read it, it's good to think about!
Saturday, May 10, 2014
IPhone app to save time!
Try my new app on app store. It is great if you want to save time. TimeSaver offers you:
- An easier life not having to remember hours and minutes.
- A fast and easy way to save your time at work.
- An easy way to list and edit any saved time.
- Time reports of current week or month, with only one touch.
- Time reports for any given time interval.
- Total time at work for any period of time.
- Average time at work per day.
- Option to include daily lunch time.
- Privacy - all data is stored in your phone.
Unfortunately I have not had time to update this, so it is not available on app store anymore. Maybe I will find some time and do the updates that is needed sometime.
- An easier life not having to remember hours and minutes.
- A fast and easy way to save your time at work.
- An easy way to list and edit any saved time.
- Time reports of current week or month, with only one touch.
- Time reports for any given time interval.
- Total time at work for any period of time.
- Average time at work per day.
- Option to include daily lunch time.
- Privacy - all data is stored in your phone.
Unfortunately I have not had time to update this, so it is not available on app store anymore. Maybe I will find some time and do the updates that is needed sometime.
Saturday, December 19, 2009
Sunday, March 30, 2008
JBoss Clustering 4.2
Easiest way is use the 'all' server instance that already is configured for clustering in jboss.
If you have not used the 'all' instance then copy these three files from 'all' server to your server instance and it should work:
If you have not used the 'all' instance then copy these three files from 'all' server to your server instance and it should work:
- cluster-service.xml (all/deploy directory)
- jbossha.jar (all/lib directory)
- jgroups.jar (all/lib directory)
JBoss Monitoring and Performance
JBoss page how to slim your JBoss AS
Tuning JBoss on linux article
Memory and thread Montoring (see chapter 10 in JBoss 4.2 Server configuration guide)
MBean
In the JMX-console: jboss.system:type=ServerInfo MBean (view interesting attributes like FreeMemory, ActiveThreadCount etc.)
Checklist
(Read more about this in the book "JBoss Seam - Simplicity and Power beyond Java EE")
1. Use "Call by reference" (see JBoss Reference)
2. Optimize JVM (start using the -server option)
- Give at least 75 percent of the physical RAM to the JVM ( JAVA_OPT in bin/run.sh)
- set JAVA_OPTS=%JAVA_OPTS% -Xms1024m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512
- Using the same value for Xms and Xmx will force JVM to use specified value (in this case 1GB)
- -Xms2g and -Xmx2g would force JVM use 2G of RAM for example
3. Garbage Collector (use parallel GC) or what might be best for you JVM/application
- Run parallel GC
set JAVA_OPTS=%JAVA_OPTS% -XX:+UseParallelGC -XX:+UseParallelOldGC
4. Reduce logging (see JBoss page how to slim your JBoss AS)
5. Tuning the HTTP Thread Pool (see JBoss page how to slim your JBoss AS)
6. Client- or Server-Side State Saving (really depends on your application and RAM vs. Mhz)
There are more things you can do like using Second-Level Cache and Clustering.
Tuning JBoss on linux article
Memory and thread Montoring (see chapter 10 in JBoss 4.2 Server configuration guide)
MBean
In the JMX-console: jboss.system:type=ServerInfo MBean (view interesting attributes like FreeMemory, ActiveThreadCount etc.)
Checklist
(Read more about this in the book "JBoss Seam - Simplicity and Power beyond Java EE")
1. Use "Call by reference" (see JBoss Reference)
2. Optimize JVM (start using the -server option)
- Give at least 75 percent of the physical RAM to the JVM ( JAVA_OPT in bin/run.sh)
- set JAVA_OPTS=%JAVA_OPTS% -Xms1024m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512
- Using the same value for Xms and Xmx will force JVM to use specified value (in this case 1GB)
- -Xms2g and -Xmx2g would force JVM use 2G of RAM for example
3. Garbage Collector (use parallel GC) or what might be best for you JVM/application
- Run parallel GC
set JAVA_OPTS=%JAVA_OPTS% -XX:+UseParallelGC -XX:+UseParallelOldGC
4. Reduce logging (see JBoss page how to slim your JBoss AS)
5. Tuning the HTTP Thread Pool (see JBoss page how to slim your JBoss AS)
6. Client- or Server-Side State Saving (really depends on your application and RAM vs. Mhz)
There are more things you can do like using Second-Level Cache and Clustering.
Tuesday, February 05, 2008
Flying Saucer renderer in JBoss Seam Fix
Used the iText and The Flying Saucer xhtml renderer to generate pdf's in my JBoss Seam application.
Problem: Everything worked fine. A pdf was generated in my app but the application context was somehow corrupt after the pdf generation and I could not continue using the app unless I redeployed it on JBoss AS again. I noticed that this happened after I had instanciated the org.xhtmlrenderer.pdf.ITextRenderer.
Found the fix for this in the JBoss Seam forum (thanks Calvin, you saved my day :)).
------------------------------------------------------------------------
Here's a fix for the problem. Set this system property before instantiating your first instance of ITextRenderer:
The problem seems to be caused by Flying Saucer reconfiguring the log manager by calling LogManager.readConfiguration. Flying Saucer shouldn't really be doing this because it blows away any existing log configuration, but on the other hand it's odd that Seam (or maybe JBoss?) behaves this way when logging is reconfigured.
--Calvin
----------------------------------------------------------------------------
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106412#4106412
Problem: Everything worked fine. A pdf was generated in my app but the application context was somehow corrupt after the pdf generation and I could not continue using the app unless I redeployed it on JBoss AS again. I noticed that this happened after I had instanciated the org.xhtmlrenderer.pdf.ITextRenderer.
Found the fix for this in the JBoss Seam forum (thanks Calvin, you saved my day :)).
------------------------------------------------------------------------
Here's a fix for the problem. Set this system property before instantiating your first instance of ITextRenderer:
| Code: |
System.setProperty("xr.util-logging.loggingEnabled", "false"); |
The problem seems to be caused by Flying Saucer reconfiguring the log manager by calling LogManager.readConfiguration. Flying Saucer shouldn't really be doing this because it blows away any existing log configuration, but on the other hand it's odd that Seam (or maybe JBoss?) behaves this way when logging is reconfigured.
--Calvin
----------------------------------------------------------------------------
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106412#4106412
Monday, January 07, 2008
JBoss Seam debug info
Enable/disable seam debug page and faclet debug
Seam - components.xml (debug = ture/false)
Facelets - web.xml (facelets.DEVELOPMENT = true/false)
Seam - components.xml (debug = ture/false)
Facelets - web.xml (facelets.DEVELOPMENT = true/false)
Subscribe to:
Posts (Atom)