This content has been marked as final.
Show 5 replies
-
1. Re: Beans not bound after one two weeks
amjad277 Oct 30, 2009 2:33 PM (in response to amjad277)"amjad277" wrote:
I use jboss 4.0.5 GA which installed on Virtual machine and Oracle Database which installed on another Virtual machine.
I deployed ear file which has all beans (EJB3) in the jboss server, all the beans are bounded and every things work fine.
But after 2 weeks, and suddenly, the following exception shown and nothing work more: "Exception: Bean not bound". I tried to restart jboss but the problem remains!
The only solution to get every thing work, as before:
Restarting the vertual machines (Oracle VM and Jboss VM) then Jboss.
Please help!! -
2. Re: Beans not bound after one two weeks
amjad277 Oct 30, 2009 2:33 PM (in response to amjad277)"amjad277" wrote:
I use jboss 4.0.5 GA which installed on Virtual machine and Oracle Database which installed on another Virtual machine.
I deployed ear file which has all beans (EJB3) in the jboss server, all the beans are bounded and every things work fine.
But after 2 weeks, and suddenly, the following exception shown and nothing work more: "Exception: Bean not bound". I tried to restart jboss but the problem remains!
The only solution to get every thing work, as before:
Restarting the vertual machines (Oracle VM and Jboss VM) then Jboss.
Please help! -
3. Re: Beans not bound after one two weeks
amjad277 Oct 30, 2009 2:39 PM (in response to amjad277)Sorry I wrote the text 3 Times!!
-
4. Re: Beans not bound after one two weeks
amjad277 Nov 2, 2009 10:35 AM (in response to amjad277)Has anyone idea, why does this error happen? This problem happens irregularly every two weeks!
Please help!! -
5. Re: Beans not bound after one week
amjad277 Jan 18, 2010 10:49 AM (in response to amjad277)I habe solved this problem:
Another jboss-server (1) use an InitialContext with same url as my jboss-server (2), and every time when I start Server # 1 the error happened directly on the Server #2.
Sever #2 runs since long time and stays on, I use Server #2 only some times (one time every 2 weeks). So the error happened only every two weeks.