About Me
Muhammad Edwin is just an ordinary Computer Geek and Anime Freak who works as an Application and DevOps Consultant at Red Hat.
Purpose
Im maintaining this blog mainly for keeping my programming journey notes. Everything that ive learned, i will put them here. I also set them as public so that it may help others that might have the same problem.
Email: edwin [at] redhat [dot] com
Nationality : Indonesian
Interests
- Photography
- Beaches
- Programming
- IT Gadgets
- Animes
- Mangas
- Online Games
- Premier League
Favorite Movies
- Finding Neverland
- Fight Club
- Beautiful Mind
- The Godfather Trilogy
- Gangs Of New York
- The Departed
- 50 First Dates
Hey,
I came across your profile randomly and noticed you enjoy java and gaming. My friends and I are working on replicating runescape classic and would love if you would take the time to chat with us and maybe help with the project?
Thanks!
Hi Todd, feel free to add my skype id 🙂
:-S Edwin, I came across your blog while search for information on thread creation management inside of Glassfish. We have Glassfish 3 installed and an application we have written deployed to Glassfish that handles “task”. Most of these task are printing task issued from within our ERP (JDEdwards). An issue we are having that I can’t seem to solve relates to sequencing of the printed output. Our end user community will submit print request for multiple shipping documents from JDEdwards, the task are submitted in the order they appear on the screen (i.e. mostly by an order number) and Java messaging is used to instantiate an instance of the print manager for the specific document. The issue lies in the multithreaded nature of GF. If say 10 print request are submitted and the EJB’s are processing at the same time within the Glassfish container, there is no control over the order that the tasks will complete their processing, so the order in which they print is not controlable either. Any suggestions on thread creation, thread management, etc. in the Glassfish environment so that I can effect the order of printed output? I’ve tried writing delays prior to the java message creation to allow any task currently processing the opportunity to finish if the next task being submitted is in the same group of work. This works sometimes but not 100 %. Thanks in advance!!
Hi Randy,
perhaps you could queueing your printing task using singleton class,
so basically the ordering would be First In First Out