#21 The first lookup of a bean never returns

v2.2.1 (stable)
closed-works-for-me
nobody
5
2001-07-16
2001-05-04
Anonymous
No

I have a serious problem with JBoss-2.2/2.2.1 running
on my Linux
box (SuSE 6.4): The first lookup for a certain bean
after a server
restart or redeployment always hangs. This happens to
my own beans but also to the provided tomcat-test
application.

The symptoms are:

0. Restart JBoss.
1. Call http://localhost:8080/jboss/servlet/HelloEJB in
your browser.
It never returns. Stop the request.
2. Call http://localhost:8080/jboss/servlet/HelloEJB
again in your
browser. It never returns, too. Stop the request.
3. Call the URL a third time. Now the call succeeds.

The first call hangs at the lookup of the NonOptimized
bean, the
second hangs at the lookup of the Optimized bean and
after this everything works fine (maybe InitialContext
has a cache for paths?).

I've tested IBMJava2-13, Blackdown's j2sdk1.3.0 and
SUN's
jdk1.3.0_02 in any combinations with JBoss-2.2/2.2.1,
but it
didn't help.

Discussion

  • Georg Rehfeld

    Georg Rehfeld - 2001-05-09

    Logged In: YES
    user_id=215142

    I have the same error with slightly different behaviour
    on Windows 2000, SUN JDK1.3, JBoss 2.1 and 2.2.1 when
    looking up Entity Beans. The first lookup() ever succeeds,
    but one of the following then hangs forever (with bad
    consequences for the transactional behaviour). As with the
    original report, after the hang all further lookups seem
    to succeed.

    See the following jboss-user messages for my details
    including a stack trace showing the blocking lookup task.

    http://www.geocrawler.com/mail/msg.php3?
    msg_id=5705779&list=10767
    http://www.geocrawler.com/mail/msg.php3?
    msg_id=5706495&list=10767

    Georg Rehfeld

     
  • Nobody/Anonymous

    Logged In: NO

    Hi all,
    I must apologize for this error message: Our administrator
    changed the
    IP-address of my test-machine from a fixed one to a dynamic,
    but he
    forgot to tell me ... therefore my Linux-box was
    misconfigured in
    /etc/hosts (wrong IP). This was the reason for the strange
    behaviour
    of lookup().

    Regards,
    Max du Prel

     
  • Nobody/Anonymous

    Logged In: NO

    Hi all,
    I must apologize for this error message: Our administrator
    changed the
    IP-address of my test-machine from a fixed one to a dynamic,
    but he
    forgot to tell me ... therefore my Linux-box was
    misconfigured in
    /etc/hosts (wrong IP). This was the reason for the strange
    behaviour
    of lookup().

    Regards,
    Max du Prel

     
  • Juha Lindfors

    Juha Lindfors - 2001-07-16
    • status: open --> closed-works-for-me
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks