Peer gone problem

When I connect to weblogic server through a client. If I do some long time (or
cpu consuming) operation, I will get the peer gone exception. What is this exception
for and how can I solve it?
Thanks

Shiva Paranandi <[email protected]> wrote:
Do you see this on the client or the server?Server Side.
>
c l wrote:
When I connect to weblogic server through a client. If I do some longtime (or
cpu consuming) operation, I will get the peer gone exception. Whatis this exception
for and how can I solve it?
Thanks

Similar Messages

  • Peer Gone Exception

    We are experiencing a problem where two of the three servers in our cluster
              are reporting PeerGoneExceptions.
              Server @10.10.3.15 reports
              Tue Jan 16 17:48:33 EST 2001:<I> <RJVM> Signaling
              peer -7147237972709474721C10.10.3.15 gone: weblogic.rjvm.PeerGoneException:
              - with nested exception:
              [java.io.EOFException]
              Server @10.10.3.16 reports
              Tue Jan 16 17:48:57 EST 2001:<I> <RJVM> Signaling peer
              5919020684957854659C10.10.3.16 gone: weblogic.rjvm.PeerGoneException:
              - with nested exception:
              [java.io.EOFException]
              All servers in our cluster are using the same cluster properties
              weblogic.cluster.multicastTTL=1
              weblogic.cluster.enable=true
              weblogic.cluster.multicastAddress=224.13.13.13
              weblogic.cluster.defaultLoadAlgorithm=round-robin
              The third server reports no such error. The error repeats every 10 minutes.
              Using WL server 5.1 sp 8
              Any help is appreciated
              thanks
              Mike Horn
              

    Hi Mike,
              We were having the same error message. But this comes when whatever
              application talking to the app server is terminated and the connection is
              closed. Whichever application is starting this connection, when it closes it
              causes the PerrGoneException message on weblogic servers.
              hope this helps,
              venu
              Mike Horn wrote:
              > Solaris 2.7
              > I am unaware of any other usage of our multicast address. There where no
              > Conflict messages in the logs
              >
              > Thanks for your assistance
              > Mke H
              >
              > "Shiva" <[email protected]> wrote in message
              > news:[email protected]...
              > >
              > > Do you see any errors before this error? The possible errors could be
              > ConflictStart-ConflictStop errors. Are you sure that no other application is
              > sharing the same multicast address as the weblogic cluster?
              > > What is the configuration of your OS? NT or Solaris? Which version?
              > >
              > > Shiva.
              > >
              > > "Mike Horn" <[email protected]> wrote:
              > > >We are experiencing a problem where two of the three servers in our
              > cluster
              > > >are reporting PeerGoneExceptions.
              > > >
              > > >Server @10.10.3.15 reports
              > > >Tue Jan 16 17:48:33 EST 2001:<I> <RJVM> Signaling
              > > >peer -7147237972709474721C10.10.3.15 gone:
              > weblogic.rjvm.PeerGoneException:
              > > > - with nested exception:
              > > >[java.io.EOFException]
              > > >
              > > >Server @10.10.3.16 reports
              > > >Tue Jan 16 17:48:57 EST 2001:<I> <RJVM> Signaling peer
              > > >5919020684957854659C10.10.3.16 gone: weblogic.rjvm.PeerGoneException:
              > > > - with nested exception:
              > > >[java.io.EOFException]
              > > >
              > > >All servers in our cluster are using the same cluster properties
              > > >weblogic.cluster.multicastTTL=1
              > > >weblogic.cluster.enable=true
              > > >weblogic.cluster.multicastAddress=224.13.13.13
              > > >weblogic.cluster.defaultLoadAlgorithm=round-robin
              > > >
              > > >The third server reports no such error. The error repeats every 10
              > minutes.
              > > >Using WL server 5.1 sp 8
              > > >
              > > >Any help is appreciated
              > > >
              > > >thanks
              > > >Mike Horn
              > > >
              > > >
              > >
              

  • Ad-hoc/peer-to-peer WIFI problems

    There definitely seems to be a problem with WIFI on the iPhone 4.
    At my work, I have been using a peer-to-peer/ad-hoc wireless connection setup on my laptop with internet connection sharing. I've been using this for over a year, first with my iPhone 2G and then my 3GS. Five of my colleagues have also been using the connection fine.
    However, two of us have now upgraded to iPhone 4s and, although they work fine on our home WIFI networks, neither of them work on our work ad-hoc network. They connect to the network, but it takes ages before the WIFI symbol appears and, when it finally does, you cannot access the internet.
    Also, if one of our iPhone 4s connects to the network, all other 3Gs and 3GSs can’t access the internet! It’s amazing to watch. Surf from web page to web page on a 3GS fine, connect an iPhone 4 and, bang, 3GS stops loading pages. Turn off WIFI on the iPhone 4 and 3GS starts loading pages again. Weird!
    Before anyone asks, there are no ip address conflicts on the network and we have checked the settings on all of the phones numerous times; they’re fine.
    We’ve also tried this on three different laptops although, I have to admit, they are all the same model; IBM ThinkPad Lenovo R400.
    I’m suspecting it’s a frequency issue and I can probably resolve it by adjusting the WIFI card settings on the laptop, but so far I’ve had no joy.
    Any ideas?

    Tried many different combinations of the WIFI card settings on the ThinkPad, but no joy. It's as though the iPhone 4 is too noisy on the network and causes the other devices to fail to comunticate on the network.
    When a 3GS is connected on its own (or with other 3GSs), I can ping it. But as soon as I connect an iPhone 4, I can no longer ping the 3GS. What is happening?
    The actual card in the ThinkPad is an Intel WiFi Link 5100 AGN.

  • Folder & question mark once; rebooted & it's gone:  problem?

    I powered up the iMac this morning and saw the folder with the question mark. I had this issue several months back, but was able to resolve it (don't recall how). This morning I powered the machine back down, and then back up again, and it booted normally.
    Should I presume I've got a hard drive ready to go? Needless to say, I'd rather be too careful (and replace a hard drive that might go bad early), than too late.
    If I do need to replace the iMac hard drive, is there any reason to try it myself, or does this need to go to Apple? From what little I've read it seems to be pretty challenging to do. What about running the machine (which is in an office where it's easy to hide an external drive) entirely from an external FW drive? Is that a bad idea?
    Thanks!

    I would start by doing a bit more testing:
    1) disconnect your external drive and any other peripherals you may have and leave them disconnected long enough to see if the problem still exists.
    2) reset the SMC: http://support.apple.com/kb/HT1543?viewlocale=en_US
    3) run Apple Hardware Test in Extended mode. insert the original install disk, restart and hold down the "d" key.
    If the AHT passes without any problems then most likely the problem is just the hard drive. Booting from an external drive will provide only moderate performance as FW 400 maxes out at about 35-40MB read/write and the FW800 drives that I have from OWC max at about 65MB read/write which is about what your current internal drive may get. Any of the newer 640GB drives by WD or Seagate get about 110MB read/write so replacing the drive internally will provide better performance.
    Do you have the 20" or 24" iMac? I have the 24" and there was actually quite a bit of extra room inside. I was just surprised that the whole process was much easier than I was expecting. You could always have an Apple approved repair center do the install for you.
    George

  • Peer-to-peer Blocking problems

    Hi folks,
    I'm using WiSMs version 7.0.235.3 and WLC 7.0.230.0.  I'm trying to allow peer-to-peer communication but am having some difficulty.  I have "Peer to Peer Blocking" set to Disable and can ping between devices i.e. ICMP is working fine.  IP however is not working which doesn't really make any sense to me.  I've confirmed this using Wireshark.  If I set "Peer to Peer Blocking" to Drop, all traffic is blocked.
    Any assistance/recommendations would be appreciated.
    Thanks. S.

    What are you actually trying to do? Is the issue when clients are associated to
    The same WLAN on the same WLC?
    Sent from Cisco Technical Support iPhone App

  • RJVM Signaling peer 3688822629303549796C160.96.179.40 gone: weblogic.rjvm.PeerGoneException:

    Hi,
    We are using WebLogic Server 5.1 SP8 as our AppServer.
    The server is killed abruptly with the following message :
    Mon Aug 20 14:44:39 GMT+08:00 2001:<I> <RJVM> Signaling peer 3688822629303549796C160.96.179.40
    gone: weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.io.EOFException]
    What should be the possible reasons?
    Is it something to do with the N/W breakups ?
    Regards,
    TejoKiran.Y

    Dear Kumar,
    Thanks for your interest in answering the Q.
    Well, there is no other stack trace available.
    The last message we saw is ,
    Mon Aug 20 14:44:39 GMT+08:00 2001:<I> <RJVM> Signaling peer 3688822629303549796C160.96.179.40
    gone: weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.io.EOFException]
    The server was killed completely.
    Infact, 160.96.179.40 is the IP Address of our Application Server (WebLogic Server
    is runnning at port 7001).
    That is the last statement.
    We observed this error few times before in our log file, but it
    didnot bring down the server.
    Would U mind explaining me what exactly does that error mean?
    For your info:
    We also saw this message few times,
    Fri Aug 17 15:08:36 GMT+08:00 2001:<I> <CliCon-#|ccls|0.998032002043> Connection
    to client for ClientContext - id: '#|ccls|0.998032002043', bound: 'true', dead:
    'false' has been unexpectedly lost because weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.io.EOFException].
    Initiating hard disconnect.
    Regards,
    TejoKiran.Y
    Kumar Allamraju <[email protected]> wrote:
    Are you sure that the server is killed (crashed)?
    The following informative message only says that the client
    with IP 160.96.179.40 has peer gone'd
    Could you post complete stack trace?
    TejoKiran wrote:
    Hi,
    We are using WebLogic Server 5.1 SP8 as our AppServer.
    The server is killed abruptly with the following message :
    Mon Aug 20 14:44:39 GMT+08:00 2001:<I> <RJVM> Signaling peer 3688822629303549796C160.96.179.40
    gone: weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.io.EOFException]
    What should be the possible reasons?
    Is it something to do with the N/W breakups ?
    Regards,
    TejoKiran.Y

  • My Nokia x3 problem.

    my nokia x3 wont start after showing the nokia logo, blinked 4 times with white screen and its goes off.WHY...
    And how to repair.. I want to repair it but I don't know how to repair it..
    Please, this is my third time my nokia x3 gon problem...

    Remove the battery for about 5 minutes.. Insert and retry..
    Else the only solution is .. Visit Nokia Care...
    --------------------------------------------------​--------------------------------------------------​--------------------------------------------------​--If you find this helpful, pl. hit the White Star in Green Box...

  • 4.4.1 ACR xmp problem - see new info

    As suggested I have upgraded to 4.4.1 and have the same problem. However there is further info below that should allow anyone to reproduce the problem. I.ve just done it on 3 machines.
    Original Posted Problem
    Would appreciate help on this if anyone has seen the problem.
    I use ACR 4.3 on windows XP Pro with CS3, 4 gig ram.
    My normal practice is to copy my CF cards to folders on the desktop, then
    drag each folder to Bridge to rough select the keepers.
    I then open the remaining images in ACR and make further deletions if
    necessary.
    When I delete images from the ACR screen, the X appears as normal but the
    sidecar.xmp file is not been deleted, only the NEF deletes.
    New Info.
    After deleting the X images the corresponding .xmp files have gone - problem fixed I thought!!
    If you now drag the same folder to bridge for the second time, then open all images in ACR, make any alteration to all of them, then delete for example 3 images, the X appears and the NEF file is deleted, but the dreaded sidecar.xmp files are still in the folder for those files deleted on the second pass.
    I,ve tried this a few times and it always gives the same result.
    Hope this makes sense and someone else ca reproduce the same problem
    Regards and thanks
    Michael

    Sounds like one of those pesky little bugs that might get fixed, unless it doesn't. My only suggestion would be to try converting to DNG. Then you wouldn't have to worry about the XMP files at all.

  • CME dial-peer PSTN call

    Hello
    I have 2 CME
    PSTN===>CME01===LAN==>CME02 please see attached file with dial-peer config
    problem:
    ip phone 1299 can call 07733XXXXX (PSTN phone)
    ip phone 1484 can call 1299 but cannot dial 07733XXXXX(PSTN phone)
    please can you help

    Yes certainly its possible, create another specific dial-peer for the 077XX number and configure over ride on that dial-peer as per below:
    dial-peer voice 4 voip
    incoming called-number ^07733.....$    <<<< This for matching all calls starting with 07733
    paramspace callsetup after-hours-exempt true  << this should exempt this dial-peer
    end
    So your calls hitting dial-peer 3 we previously created will match anything other than 07733 numbers and will have call block on. This dial-peer 4 will allow exemption for this specific number.
    If you want to exempt all calls from CME02 then you can have the command:
    paramspace callsetup after-hours-exempt true
    under the dial-peer 3 we previously created.
    Let me know how you go and please do rate all helpful posts.
    -Terry

  • Wldeploy dosent work as expected in 11.1.2 as it works in 11.1.1.1.5

    I have the exactly same problem as described in this thread Error running Weblogic.Deployer in medrec tutorial (wl9.1)
    But my old jdev version (11.1.1.1.5) where things works fine and I am migrating to new jdev version (11.1.2) during wldeploy
    C:\Oracle\Middleware1112\jdeveloper\jdev\bin>
    C:\Oracle\Middleware1112\jdk160_24\bin\javaw.exe -client -Dosgi.clean=true -XX:MaxPermSize=256M -Xbootclasspath/p:../lib/lwawt.jar -Xbootclasspath/p:../lib/apt-expose.jar -Dsun.awt.keepWorkingSetOnMinimize=true -XX:+HeapDumpOnOutOfMemoryError -Doracle.jdeveloper.webservice.showAllOwsmPolicyTypes=false -Doracle.jdeveloper.webservice.hidePropertyOverride=false -Dsun.awt.disablegrab=true -Xbootclasspath/p:../../rdbms/jlib/ojdi.jar -Dide.patches.dir=jdev/lib/patches -Dnetbeans.home=../../netbeans/platform/ -Dnetbeans.logger.console=true -Dexcluded.modules=org.eclipse.osgi -Dide.cluster.dirs=../../netbeans/netbinox/:../../netbeans/bridge/:../../ -Xmx800M -Xms128M -Xverify:none -Doracle.ide.extension.HooksProcessingMode=LAZY -Dorg.eclipse.equinox.simpleconfigurator.configUrl=file:bundles.info -Dosgi.bundles=file:../ide/lib/oracle.ide.osgi.jar@3:start -Dosgi.bundles.defaultStartLevel=1 -Dosgi.configuration.cascaded=false -Dosgi.noShutdown=true -Dorg.osgi.framework.bootdelegation=* -Dosgi.parentClassloader=app -Xbootclasspath/p:../../rdbms/jlib/ojdi.jar -Dosgi.classloader.singleThreadLoads=true -Dosgi.bundlefile.limit=2000 -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n-collation.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n-mapping.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n-servlet.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n-utility.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.nlsrtl_11.1.0/orai18n.jar -Xbootclasspath/a:../../../oracle_common/modules/oracle.xdk_11.1.0/xmlparserv2.jar -Djavax.xml.parsers.DocumentBuilderFactory=oracle.xml.jaxp.JXDocumentBuilderFactory -Djavax.xml.parsers.SAXParserFactory=oracle.xml.jaxp.JXSAXParserFactory -Dorg.xml.sax.driver=oracle.xml.parser.v2.SAXParser -Dide.feedback-server=ide.us.oracle.com -Xbootclasspath/a:../../ide/lib/xml-factory.jar -Djavax.xml.transform.TransformerFactory=oracle.ide.xml.SwitchableTransformerFactory -Dsun.java2d.noddraw=true -Dide.conf=C:\Oracle\Middleware1112\jdeveloper\jdev\bin\jdev.conf -Dide.startingcwd=C:\Oracle\Middleware1112\jdeveloper\jdev\bin "-Dide.user.dir=C:\Documents and Settings\pakrish.APPLICATIONS\Application Data\JDeveloper\system11.1.2.0.38.60.17\o.jdeveloper.extensiondt.core\EDTplatform-dt_jdev-UserAndPrefDir" -Dedt.hot.classes=D:\tmp\jdev1112\SAIExtn_1App\TestAntInvoke\classes -Dedt.hot.manifest=D:\tmp\jdev1112\SAIExtn_1App\TestAntInvoke\src\META-INF\extension.xml -Dedt.hot.deploydir=jdev/extensions/ -Dedt.extension.id=yourcompany.testantinvoke -agentlib:jdwp=transport=dt_socket,server=y,address=1589 -Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true -classpath C:\Oracle\Middleware1112\jdeveloper\ide\lib\ide-boot.jar;C:\Oracle\Middleware1112\jdeveloper\netbeans\platform\lib\boot.jar;C:\Oracle\Middleware1112\jdeveloper\netbeans\platform\lib\org-openide-util.jar;C:\Oracle\Middleware1112\jdeveloper\netbeans\platform\lib\org-openide-util-lookup.jar;C:\Oracle\Middleware1112\jdeveloper\netbeans\platform\lib\org-openide-modules.jar;C:\Oracle\Middleware1112\jdeveloper\ide\lib\fcpboot.jar -Djavax.net.ssl.trustStore=C:\DOCUME~1\PAKRIS~1.APP\LOCALS~1\Temp\trustStore5123141337500065063.jks -Dhttp.proxyHost=www-proxy.us.oracle.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|localhost.localdomain|127.0.0.1|::1|10.177.10.174| -Dhttps.proxyHost=www-proxy.us.oracle.com -Dhttps.proxyPort=80 -Xbootclasspath/a:C:\Oracle\Middleware1112\jdk160_24\lib\tools.jar;C:\Oracle\Middleware1112\jdk160_24\lib\dt.jar oracle.ide.osgi.boot.JDeveloper
    Listening for transport dt_socket at address: 1589
    Debugger connected to local process.
    Source breakpoint: InvokeAnt.java:35
    Source breakpoint: InvokeAnt.java:63
    Warning: Reference lib.path has not been set at runtime, but was found during
    build file parsing, attempting to resolve. Future versions of Ant may support
    referencing ids defined in non-executed targets.
    deploy:
    weblogic.Deployer -debug -nostage -verbose -upload -noexit -name globalweather -source C:\JDeveloper\mywork\SFE\outbound\globalweather\1.0.0.0.0\deploy\globalweather.ear -targets DefaultServer -adminurl t3://localhost:7101 -user weblogic -password ******** -deploy
    weblogic.Deployer invoked with options: -debug -nostage -verbose -upload -noexit -name globalweather -source C:\JDeveloper\mywork\SFE\outbound\globalweather\1.0.0.0.0\deploy\globalweather.ear -targets DefaultServer -adminurl t3://localhost:7101 -user weblogic -deploy
    [WebLogicDeploymentManagerImpl.<init>():115] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [WebLogicDeploymentManagerImpl.getNewConnection():158] : Connecting to admin server at localhost:7101, as user weblogic
    [ServerConnectionImpl.getEnvironment():286] : setting environment
    [ServerConnectionImpl.getEnvironment():289] : getting context using t3://localhost:7101
    [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7101/jndi/weblogic.management.mbeanservers.domainruntime
    java.io.IOException
         at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:196)
         at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:84)
         at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
         at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:238)
    weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://localhost:7101': Bootstrap to localhost/127.0.0.1:7101 failed. It is likely that the remote side declared peer gone on this JVM. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.

    Retrieving Information about WebLogic Server:
    Run
    1. <WLHOME>/server/bin/setWLSEnv
    2. java weblogic.Admin -adminurl t3://127.0.0.1:7001 -username weblogic -password weblogic1 PING 3 100
    In case of exception smth like "Caused By: java.net.UnknownHostException: localhost"
    add mappings of IP address to host name
    127.0.0.1 localhost
    For windows:
    C:\Windows\System32\drivers\etc\hosts
    Edited by: user6372268 on Dec 20, 2012 1:53 AM

  • Removing live nodes from cluster view.

    Hi All,
              We are experiencing some JMS problems connected with a cluster node being
              hung for some time.
              The following took place just before the problem arises:
              1. First of all one of the nodes (the first) gets one thread
              (weblogic.jms.backend.BEPushRequestSender@76512c) stuck.
              2. After that it closes the TCP connection to another node and
              3. Removes another node from its cluster view.(that is alive)
              4. After that the second node removes the first from its cluster
              view.
              5. Seconds later they find each other again and add each other to the
              cluster view.
              6. After that, the JMS distributed members are connected to each other,
              7. Something strange happens, because either the first node starts
              missing many messages in its distributed topic member or the second
              node doesn't propagate messages from distributed topic to the first
              node.
              Is it possible to set up weblogic cluster in a way, it won't remove
              other members from cluster view by peer gone exception, only by
              heartbeat timeout? Is heartbeat retry time parameter is configurable?
              Any help with this matter will be greatly appreciated.
              Dmitry Finkelstein
              

    You must run the update node list for each ORACLE_HOME on that machine. If this is RAC, the runInstaller will take care to update all nodes, so again, you run it once per ORACLE_HOME installed.
    Shared Home is a single copy of the Oracle software, rather than each node holding their own copy of the software. There's a paper that talks about these two topics and gives some examples of full commands on OTN:
    http://www.oracle.com/technology/products/database/clustering/index.html
    "Oracle Homes in an Oracle Real Application Clusters Environment(PDF) January 2008"
    direct link: http://www.oracle.com/technology/products/database/clustering/pdf/oh_rac.pdf
    Enjoy and hope this helps.
    Saar.

  • Issues when we try to lookup for EJB using T3 protocol

    Hi,
    We have EJB's deployed in Weblogic server and we are trying to invoke them using T3 protocol.
    We are facing problem as its giving the following exception
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://170.0.10.45:7685: Bootstrap to dev2.test.zone/170.0.10.45:7685 failed. It is likely that the remote side declared peer gone on this JVM];
    We tried to enable HttpTunneling in Weblogic server but it did not work.
    Could anyone suggest solution for this at the earliest. Not sure whether this is a cluster issue .

    We are trying to connect to service and EJB from our local weblogic portal
    Client Server Info
    Weblogic version 9.2
    jdk1.5
    Server Info
    Weblogic version 9.2
    jdk1.5
    In properties file we have delcared the EJB client URL : t3://IP:7685
    code
    private static final String CLIENT_EJB_KEY_PREFIX = "ejbclient.";
    private static final String CLIENT_EJB_JNDI_NAME_SUFFIX = ".remoteJndiName";
    try {
    String className = cls.getName();
    String key = CLIENT_EJB_KEY_PREFIX + className + CLIENT_EJB_JNDI_NAME_SUFFIX;
    LOG.debug("Looked up key of {} for className: {}", key, className);
    String jndiName = cfg.getString(key);
    System.out.println("Inside getHome Method : Jndi Name"+jndiName);
    if (StringUtils.isEmpty(jndiName)) {
    System.out.println("Inside if");
    throw new ServiceNotAvailableException("Unable to locate JNDI key of %s for class %s", key, className);
    Hashtable<String, String> env = new Hashtable<String, String>();
    env.putAll(context.connectionEnv());
    Context ctx = new InitialContext(env);
    EJBHome home = (EJBHome) ctx.lookup(jndiName);
    return home;
    } catch (NamingException cause) {
    throw new ServiceNotAvailableException(cause);
    The call to EJB is failing because it is not able to communicate using T3 protocol.

  • Has CR086758 been reintroduced in 8.1

              I found the following CR's in the documentation for both 6.0 and 7.0.
              We are running on 8.1 and experiencing the same error.
              CR086758
              In a multi-tier implementation, after ten hours of stress testing, the web tier
              hung. This occurred while the web tier (consisting of servlets, jsps, and custom
              classes that implement a custom cache) was communicating with the EJB tier (all
              stateless session beans), after the EJB tier closed the Connection Manager, due
              to missed RJVM heartbeats.
              Before the web tier hangs the following are the exceptions are thrown in the ejb
              tier. <Sep 24, 2002 8:43:58 AM PDT> <Info> <RJVM> <Failure in heartbeat trigger
              for RJVM: '7831636024374910916S:10.10.10.187:[8001,8001,8002,8002,8001,8002,-1]:webserver:sourcingWebserver'
              java.rmi.ConnectException: The connection manager to ConnectionManager for: 'weblogic.rjvm.RJVMImpl@3bedf2
              - id: '7831636024374910916S:10.10.10.187:[8001,8001,8002,8002,8001,8002,-1]:webserver:sourcingWebserver'
              connect time: 'Tue Sep 24 06:15:16 PDT 2002'' has already been shut down at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.java:1348)
              at weblogic.rjvm.ConnectionManager.createHeartbeatMsg(ConnectionManager.java:1306)
              at weblogic.rjvm.ConnectionManager.sendHeartbeatMsg(ConnectionManager.java:497)
              at weblogic.rjvm.RJVMImpl$HeartbeatChecker.trigger(RJVMImpl.java:1032) at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
              at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              Problem was solved by adding logic to assure that pending responses are notified
              of peer gone events.
              CR086758
              Fixed a problem in which, in an application with a web tier and an EJB tier, the
              web tier communicating with the EJB tier would hang (throws exception similar
              to the one shown below) when the EJB tier closed the ConnectionManager.
              <Sep 24, 2002 8:43:58 AM PDT> <Info> <RJVM> <Failure in heartbeat trigger for
              RJVM: '7831636024374910916S:10.10.10.187:[8001,8001,8002,8002,8001,8002,-1]:webserver:sourcingWebserver'
              java.rmi.ConnectException: The connection manager to ConnectionManager for: 'weblogic.rjvm.RJVMImpl@3bedf2
              - id: '7831636024374910916S:10.10.10.187:[8001,8001,8002,8002,8001,8002,-1]:webserver:sourcingWebserver'
              connect time: 'Tue Sep 24 06:15:16 PDT 2002'' has already been shut down at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.java:1348)
              at ...
              

    I'm seeing this too. My symptoms are this: I'm running a JMS topic
              listener in an applet, and it works great, until the page is
              refreshed. The applet locks up, and eventually comes back to life and
              barfs the exact exception shown below and in the CR description.
              Oddly, tho, the topic listener is then alive and well. Weirder still,
              it works fine after subsequent reloads, without this problem.
              Customer support said they replicated it and are working on it.
              "Bob Stevenson" <[email protected]> wrote in message news:<[email protected]>...
              > The relationship to jms is that client side MessageListeners are having their connections
              > closed, preventing any further message receipt or acknowledgement of previously
              > received messages.
              > The RJVM Heartbeat monitor is detecting the connection loss. The console shows
              > the durable subscribers as inactive.
              >
              > Tom Barnes <[email protected]> wrote:
              > >I don't know the answer. What does this have to do with jms?
              > >Anyhow, I suggest contacting customer support, it seems like
              > >a known issue and I suspect they are already looking at it.
              > >I also suggest supplying thread-dumps from the various servers
              > >to help narrow down the solution more quickly.
              > >
              > >Tom
              > >
              > >Amanda wrote:
              > >> I found the following CR's in the documentation for both 6.0 and 7.0.
              > >> We are running on 8.1 and experiencing the same error.
              > >>
              > >> CR086758
              > >> In a multi-tier implementation, after ten hours of stress testing,
              > the web tier
              > >> hung. This occurred while the web tier (consisting of servlets, jsps,
              > and custom
              > >> classes that implement a custom cache) was communicating with the EJB
              > tier (all
              > >> stateless session beans), after the EJB tier closed the Connection
              > Manager, due
              > >> to missed RJVM heartbeats.
              > >>
              > >> Before the web tier hangs the following are the exceptions are thrown
              > in the ejb
              > >> tier. <Sep 24, 2002 8:43:58 AM PDT> <Info> <RJVM> <Failure in heartbeat
              > trigger
              > >> for RJVM: '7831636024374910916S:10.10.10.187:[8001,8001,8002,8002,8001,8002,-1]:webserver:sourcingWebserver'
              > >> java.rmi.ConnectException: The connection manager to ConnectionManager
              > for: 'weblogic.rjvm.RJVMImpl@3bedf2
              > >> - id: '7831636024374910916S:10.10.10.187:[8001,8001,8002,8002,8001,8002,-1]:webserver:sourcingWebserver'
              > >> connect time: 'Tue Sep 24 06:15:16 PDT 2002'' has already been shut
              > down at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.java:1348)
              > >> at weblogic.rjvm.ConnectionManager.createHeartbeatMsg(ConnectionManager.java:1306)
              > >> at weblogic.rjvm.ConnectionManager.sendHeartbeatMsg(ConnectionManager.java:497)
              > >> at weblogic.rjvm.RJVMImpl$HeartbeatChecker.trigger(RJVMImpl.java:1032)
              > at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
              > >> at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
              > >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at
              > weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > >>
              > >> Problem was solved by adding logic to assure that pending responses
              > are notified
              > >> of peer gone events.
              > >>
              > >> CR086758
              > >> Fixed a problem in which, in an application with a web tier and an
              > EJB tier, the
              > >> web tier communicating with the EJB tier would hang (throws exception
              > similar
              > >> to the one shown below) when the EJB tier closed the ConnectionManager.
              >
              > >> <Sep 24, 2002 8:43:58 AM PDT> <Info> <RJVM> <Failure in heartbeat trigger
              > for
              > >> RJVM: '7831636024374910916S:10.10.10.187:[8001,8001,8002,8002,8001,8002,-1]:webserver:sourcingWebserver'
              > >> java.rmi.ConnectException: The connection manager to ConnectionManager
              > for: 'weblogic.rjvm.RJVMImpl@3bedf2
              > >> - id: '7831636024374910916S:10.10.10.187:[8001,8001,8002,8002,8001,8002,-1]:webserver:sourcingWebserver'
              > >> connect time: 'Tue Sep 24 06:15:16 PDT 2002'' has already been shut
              > down at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.java:1348)
              > >> at ...
              > >>
              > >
              

  • Reconnect does not work after PeerGoneException

    Application faced JMS PeerGoneException.
    And tried to recover by reconnecting to queue. but still reconnect is not successfull. it does not throw any exception but subscriber count on web logic console is zero. and no messages are consumed pening in Queue.
    1. Exception
    weblogic.jms.common.LostServerException: java.lang.Exception: weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds
         at weblogic.jms.client.JMSConnection.dispatcherPeerGone(JMSConnection.java:1543)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.run(DispatcherWrapperState.java:689)
         at weblogic.messaging.dispatcher.DispatcherWrapperState.timerExpired(DispatcherWrapperState.java:614)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    Caused by: java.lang.Exception: weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds
         at weblogic.messaging.dispatcher.DispatcherWrapperState.onDisconnect(DispatcherWrapperState.java:391)
         at weblogic.rjvm.RJVMImpl$DisconnectEventDeliverer.run(RJVMImpl.java:1662)
         ... 3 more
    Caused by: weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds
         at weblogic.rjvm.RJVMImpl$HeartbeatChecker.timerExpired(RJVMImpl.java:1591)
         at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
         ... 3 more
    2. Reconnect code
    queueSession = queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
                             Iterator it = //queueinfo iterator
                             while(it.hasNext()) {
                                  QueueInfo queueInfo = (QueueInfo) it.next();
                                  String selector = configureQueueSelector(queueInfo.getName());
                                  QueueReceiver receiver = null;
                                  if (selector == null || selector.trim().length() == 0) {
                                       receiver = queueSession.createReceiver(queueInfo.getQueue());
                                  } else {
                                       receiver = queueSession.createReceiver(queueInfo.getQueue(), selector);
                                  receiver.setMessageListener(this);
    any help is appreciated.

    Hi,
    A 240 second peer-gone timeout typically occurs after an atypical "silent" network failure that does not force a socket error (such as a physical cable disconnect or a firewall activation).
    WebLogic detects such failures by checking whether periodic "heartbeat" packets get through the TCP/IP connection.
    Thoughts:
    Verify that you have network connectivity from the problem client.
    Verify that other clients to the WLS remain connected.
    Check your WL server log for errors - this may yield a clue to the problem.
    If this doesn't help, please respond with a description your network addressing and topology. Namely:
    - Client type (thin t3, old-style thin, thick, or install)
    - URL
    - Are there intervening NAT/firewalls/load-balancers?
    HTH,
    Tom

  • Server encounters PeerGoneException

    My server hit this problem quite often about 50%. Below is the exception
    thrown in weblogic.log. What can be the possible reason? I have set time-out
    values in weblogic.properties and added <%@ page buffer="32kb" %> in the
    appropriate pages. I am using WLS 510 sp 9.
    Wed Nov 07 15:01:14 GMT+08:00 2001:<I> <RJVM> Signaling
    peer -6154435941152476468C189.170.10.85 gone:
    weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.net.SocketException: Connection reset by peer: Connection reset by
    peer]
    Wed Nov 07 15:01:14 GMT+08:00 2001:<I> <CliCon-#|server|1.1005019764594>
    Connection to client for ClientContext - id: '#|server|1.1005019764594',
    bound: 'true', dead: 'false' has been unexpectedly lost because
    weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.net.SocketException: Connection reset by peer: Connection reset by
    peer].
    Initiating hard disconnect.
    regards,
    mo

    'Peer gone exception' indicates that a 'Peer' disconnected from WebLogic. The
    peer can be another WL instance in a cluster, a WL Console or something else.
    If this is the only message you see and there are no other problems, you can
    ignore the message.
    Mike
    "mo guangquan" <[email protected]> wrote:
    My server hit this problem quite often about 50%. Below is the exception
    thrown in weblogic.log. What can be the possible reason? I have set time-out
    values in weblogic.properties and added <%@ page buffer="32kb" %> in
    the
    appropriate pages. I am using WLS 510 sp 9.
    Wed Nov 07 15:01:14 GMT+08:00 2001:<I> <RJVM> Signaling
    peer -6154435941152476468C189.170.10.85 gone:
    weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.net.SocketException: Connection reset by peer: Connection reset
    by
    peer]
    Wed Nov 07 15:01:14 GMT+08:00 2001:<I> <CliCon-#|server|1.1005019764594>
    Connection to client for ClientContext - id: '#|server|1.1005019764594',
    bound: 'true', dead: 'false' has been unexpectedly lost because
    weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.net.SocketException: Connection reset by peer: Connection reset
    by
    peer].
    Initiating hard disconnect.
    regards,
    mo

Maybe you are looking for