org.obe.server.j2ee.ejb.WMRuntimeException

Receive timed out

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1

  • via sourceforge.net by Unknown author, 11 months ago
    Receive timed out
  • Stack trace

    • org.obe.server.j2ee.ejb.WMRuntimeException: Receive timed out at org.obe.server.j2ee.ejb.EJBHelper.getEJBLocalHome(EJBHelper.java:132) at org.obe.client.api.local.J2EELocalClient.connect(J2EELocalClient.java:90) at org.obe.worklist.CLWorklist.connect(CLWorklist.java:1220) at org.obe.worklist.CLWorklist.doConnect(CLWorklist.java:237) at org.obe.worklist.CLWorklist.doMainMenu(CLWorklist.java:149) at org.obe.worklist.CLWorklist.main(CLWorklist.java:116) Caused by: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Re ceive timed out] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:971) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1052) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:450) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:443) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.obe.server.j2ee.ejb.EJBHelper.getEJBLocalHome(EJBHelper.java:130) ... 5 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 9 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    1 more bugmates