Tarun, one of the organizers of Blogcamp2, started with an introduction to BlogCamp @ 10:10 AM, with a nice PPT having picture on almost every slide (I think, A picture speaks a thousand words). As it was an unconferencing conference he asked us to introduce ourselves. Luckily, I was introducing myself, someone clicked my picture and to my surprise, the same picture was published in next day's TimesOfIndia. After quite a bit of effort, today I could finally find the photographer and got this picture!
I really liked the enthusiasm of the attendees, especially the Mumbai bloggers were really energetic.
Sessions at Blogcamp:
The first session at BlogCamp was really interactive. Meetu blogs on movie reviews & her topic was “Marketing your Blog”. She wasn’t new to blogging, but certainly did n0t have much expertise in marketing her blog that effectively. Other bloggers from the audience gave many useful inputs. Meetu appreciated all of those inputs & accepted quite a few of them. I really liked this session, as it was more of discussion than typical presentation.
He was the youngest blogger of the blogcamp, he is just 15. And most of us were surprised that his blog gets around 38,000 hits a month!
@Scientist
This was one of the most knowledge rich, however monotonous session. No one asked a single question during or after the session. Maybe everyone was feeling sleepy with there stomach full.
He became the center of attraction at the end of BlogCamp! Whoever was sleeping in earlier session(at least I was) was shaken & woke up with Abhiskek’s standup act in lobby.
Have you read "Five Point Someone" by Chetan Bhagat? I was feeling like Chetan is standing in front of me & narrating his story. Yes, Abhishek is also an ex IITan. In the lobby, when he was sharing his experiences on various kinds of blogging, no one wanted to step away. He reiterated, "All of my blogs are in Cryo state now. And there is no point in visiting them at this moment. But they can revive anytime." I couldn't stop myself from checking out his extraordinary blogs & I could find them immediately through my iPhone. After some time, all of us moved to the conference room and enjoyed Abhishek's stories for almost an hour (I can't recollect from where I grabbed these pictures now)
I’ve worked with Weblogic & jBoss both the application server for quite some time now. While working on weblogic I’ve faced some issues, below are couple of them which are not issues with jBoss:
1. CacheFullException.
2. Stuck Thread.
CacheFullException:
Cause of Exception: This issue would occur when number of Entity beans cached in memory goes beyond the default size or the size configured in weblogic.xml.
Solution: There is one attribute which can be set in weblogic.xml, to set maximum number of beans can be held in memory. If this attribute not configured explicitly, the default value is 1000. This is only a work around for CacheFullException. Why I am saying ‘only work around’ is because, you are only delaying the problem but not really resolving it with setting. If the usage of the application goes high, the value you have set would not be sufficient eventually.
After long struggle the solution we have implemented is, set the attribute value to some reasonable value & have your code ensure it does not load more beans than configured.
The places you would generally need to load beans in large size is, either when you need to show them on screen or need to do some heavy processing. The idea behind our implementation was to do a processing in batching.
Stuck Thread:
Cause of Exception: This error would occur if a processing thread is taking too long (longer than configured) then server would throw this exception.
Solution: In my opinion you should relook at your code, find the process which is taking too long & break down that process into logical chunks. In weblogic by default there are only 15 threads available for your application. In fact all 15 threads are not available, but few of them are reserved for application server.
The savior issues I faced with stuck thread was, after getting several stuck thread errors weblogic became handicapped, could not proceed further until the stuck threads were released. The quick ‘work around’ you can do for this issue is, through configuration increase the number of threads available for your application. By doing so at least the server would not stop its processing.
jBoss experience:
When I worked with jBoss earlier, I did not face any of the above issues with this server. jBoss handles the cache of beans efficiently, it can handle as many beans as your application needs without any complains. Also jboss handles the thread pool efficiently, you don’t need to do any explicit setting for it.
Posts
