Multicast Exception when starting a managed weblogic server.

I receive a Multicast Exception when i try to start a managed weblogic server from the same machine on which my admin server is running.
          when i try to start a managed server from another machine then it does not allow me to do so.
          please help,
          Manish.
          

see Sanjeev Chopra's response on 10/25/00 , subject named "
weblogic.admin.host -- missing
property"...
Kumar
John Kelvie wrote:
I am having the same problem...any suggestions?
"Srividhya" <[email protected]> wrote in message
news:3a107849$[email protected]..
Hi All,
While starting the weblogic managed server, i get the following error:
Starting WebLogic Server ....
<Mon Nov 13 17:50:12 EST 2000> <Warning> <Management> <Unrecognizedproperty: ad
min.host>
<Mon Nov 13 17:50:15 EST 2000> <Error> <Configuration Management> <Errorconnect
ing to admin server and initializing admin home: admin URL:t3://kerala:7001
javax.naming.ServiceUnavailableException. Root exception isjava.rmi.NoSuchObje
ctException: The object identified by [3] could not because found. Eitherit was
has not been exported or it has been collected by the distributed garbagecolle
ctor.
atweblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:3
78)
atweblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLIniti
alContextFactoryDelegate.java:306)
atweblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
textFactoryDelegate.java:261)
atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:230)
at weblogic.jndi.Environment.getContext(Environment.java:129)
atweblogic.jndi.Environment.getInitialContext(Environment.java:112)
atweblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
at weblogic.management.Admin.start(Admin.java:295)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
On the admin server, it does not give any error.
What could be the reason?
Regards,
Srividhya

Similar Messages

  • Starting the managed weblogic server

    Hi All,
    While starting the weblogic managed server, i get the following error:
    Starting WebLogic Server ....
    <Mon Nov 13 17:50:12 EST 2000> <Warning> <Management> <Unrecognized property: ad
    min.host>
    <Mon Nov 13 17:50:15 EST 2000> <Error> <Configuration Management> <Error connect
    ing to admin server and initializing admin home: admin URL: t3://kerala:7001
    javax.naming.ServiceUnavailableException. Root exception is java.rmi.NoSuchObje
    ctException: The object identified by [3] could not because found. Either it was
    has not been exported or it has been collected by the distributed garbage colle
    ctor.
    at weblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:3
    78)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLIniti
    alContextFactoryDelegate.java:306)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
    textFactoryDelegate.java:261)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:230)
    at weblogic.jndi.Environment.getContext(Environment.java:129)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:112)
    at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
    at weblogic.management.Admin.start(Admin.java:295)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
    at weblogic.Server.main(Server.java:32)
    >
    On the admin server, it does not give any error.
    What could be the reason?
    Regards,
    Srividhya

    see Sanjeev Chopra's response on 10/25/00 , subject named "
    weblogic.admin.host -- missing
    property"...
    Kumar
    John Kelvie wrote:
    I am having the same problem...any suggestions?
    "Srividhya" <[email protected]> wrote in message
    news:3a107849$[email protected]..
    Hi All,
    While starting the weblogic managed server, i get the following error:
    Starting WebLogic Server ....
    <Mon Nov 13 17:50:12 EST 2000> <Warning> <Management> <Unrecognizedproperty: ad
    min.host>
    <Mon Nov 13 17:50:15 EST 2000> <Error> <Configuration Management> <Errorconnect
    ing to admin server and initializing admin home: admin URL:t3://kerala:7001
    javax.naming.ServiceUnavailableException. Root exception isjava.rmi.NoSuchObje
    ctException: The object identified by [3] could not because found. Eitherit was
    has not been exported or it has been collected by the distributed garbagecolle
    ctor.
    atweblogic.rmi.internal.OIDManager.getServerReference(OIDManager.java:3
    78)
    atweblogic.jndi.WLInitialContextFactoryDelegate.newLocalContext(WLIniti
    alContextFactoryDelegate.java:306)
    atweblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialCon
    textFactoryDelegate.java:261)
    atweblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:230)
    at weblogic.jndi.Environment.getContext(Environment.java:129)
    atweblogic.jndi.Environment.getInitialContext(Environment.java:112)
    atweblogic.management.Admin.initializeRemoteAdminHome(Admin.java:712)
    at weblogic.management.Admin.start(Admin.java:295)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:357)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
    at weblogic.Server.main(Server.java:32)
    On the admin server, it does not give any error.
    What could be the reason?
    Regards,
    Srividhya

  • Trouble starting managed weblogic server on another machine in  acluster

    Hi,
              I was having trouble starting managed weblogic server on another machine in a cluster from the command prompt
              I have following setup:
              1) BEA weblogic is installed on 2 machines - local machine A with ip address 172.17.2.219 and another machine B with ip address 172.17.2.201
              2)node manager is running on both machines
              3)An admin server myserver on the local machine at port 7001
              4)In the admin tree under Machines a new machine is created 'Machine1' with Node manager Listen Address: 172.17.2.201
              5) The managed server 'BEAServerMan1 ' instance is created with listen Address 172.17.2.201 and port 7705. This Server is assigened to Machine1. The server also belongs to a cluster 'Cluster1' where the 172.17.2.201:7705 is part of the Cluster Address.
              I can start 'BEAServerMan1 from http://172.17.2.16:7001/console/
              But I am unable to start BEAServerMan1 from the console using the command :
              startManagedWebLogic BEAServerMan1 http://172.17.2.219:7001
              startManagedWebLogic.sh BEAServerMan1 http://172.17.2.219:7001
              CLASSPATH=/opt/BEA/j2sdk1.4.1_03/lib/tools.jar:/opt/BEA/weblogic81/server/lib/weblogic_sp.jar:/opt/BEA/weblogic81/server/lib/weblogic.jar:/opt/BEA/weblogic81/server/lib/ojdbc14.jar::/opt/BEA/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/opt/BEA/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/opt/BEA/j2sdk1.4.1_03/jre/lib/rt.jar:/opt/BEA/weblogic81/server/lib/webservices.jar:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03:/opt/BEA/j2re1.4.1_03/bin:/opt/BEA/j2re1.4.1_03:/opt/BEA/j2sdk1.4.1_03/lib/tools.jar:/opt/oracle/OraHome1/jdbc/lib/classes111.jar:/opt/oracle/OraHome1/jdbc/lib/nls_charset11.jarx:/opt/BEA/user_projects/domains/mydomain/myserver/stage/_appsdir_dyn_ear/dyn.war:/opt/BEA/user_projects/domains/mydomain/./myserver/.wlnotdelete/extract/myserver__appsdir_dyn_ear_dyn/jarfiles/WEB-INF/lib/dspjspTaglib1_036773.jar:/usr/bin/j2re1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11:/usr/bin/j2sdk1_3_1_11/lib/tools.jar
              PATH=/opt/BEA/weblogic81/server/bin:/opt/BEA/j2sdk1.4.1_03/jre/bin:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03/bin:/opt/BEA/j2sdk1.4.1_03:/opt/BEA/j2re1.4.1_03/bin:/opt/BEA/j2re1.4.1_03:/opt/BEA/ATG6.2.0/home/bin:/usr/xpg4/bin:/opt/bmc/Patrol3/Solaris28-sun4/bin:/usr/bin::/usr/openwin/bin:/bin:/usr/ucb:/usr/local/sbin:/usr/dt/bin:/opt/RICHPse/bin:/usr/bin/j2re1_3_1_11/bin:/usr/bin/j2sdk1_3_1_11/bin
              * To start WebLogic Server, use a username and *
              * password assigned to an admin-level user. For *
              * server administration, use the WebLogic Server *
              * console at http://<hostname>:<port>/console *
              <13-Jan-2005 3:22:20 o'clock PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.1_03-b02 from Sun Microsystems Inc.>
              <13-Jan-2005 3:22:21 o'clock PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://172.17.2.219:7001 to check if there exists a running admin server at this URL.>
              <13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
              <13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009
              WebLogic XMLX Module 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009>
              <13-Jan-2005 3:22:22 o'clock PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://172.17.2.219:7001 to retrieve the initial configuration.>
              <13-Jan-2005 3:22:27 o'clock PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /opt/BEA/user_projects/domains/mydomain/BEAServerMan1 /BEAServerMan1 .log is opened. All server side log events will be written to this file.>
              <13-Jan-2005 3:22:37 o'clock PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
              <13-Jan-2005 3:22:38 o'clock PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "BEAServerMan1 " for domain "mydomain">
              <13-Jan-2005 3:22:50 o'clock PM EST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster Cluster1 on 237.0.0.1:7001.>
              <13-Jan-2005 3:22:50 o'clock PM EST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster1.>
              <13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <WebLogicServer> <BEA-000350> <Unable to create a server socket on Channel Default for: 172.17.2.201, port: 7705. java.net.BindException: Cannot assign requested address Perhaps the address 172.17.2.201 is incorrect or another process is using port 7705.>
              <13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <Security> <BEA-090085> <Server failed to bind to the configured port. The port may already be used by another process.>
              <13-Jan-2005 3:23:24 o'clock PM EST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Server failed to bind to the requested port. See preceeding log message for details.>
              The WebLogic Server did not start up properly.
              Exception raised: 'weblogic.server.ServerLifecycleException: Server failed to bind to the requested port. See preceeding log message for details.'
              Reason: Server failed to bind to the requested port. See preceeding log message for details.
              ***************************************************************************

    Hi
              i am also facing the same problem.kindly reply for th solution if you got.
              D:\bea1\user_projects_cluster\mydomain>startManagedWebLogic server2 10.16.96.21:
              7001
              D:\bea1\user_projects_cluster\mydomain>echo off
              CLASSPATH=d:\bea1\jdk131_03\lib\tools.jar;d:\bea1\weblogic700\server\lib\weblogi
              c_sp.jar;d:\bea1\weblogic700\server\lib\weblogic.jar;F:\bea\weblogic81\server\li
              b;D:\;c:\
              PATH=.;d:\bea1\weblogic700\server\bin;d:\bea1\jdk131_03\bin;E:\oracle\product\10
              .2.0\client_1\bin;C:\Program Files\Common Files\NetSarang;C:\WINDOWS\system32;C:
              \WINDOWS;C:\WINDOWS\System32\Wbem;F:\bea\jdk142_05\bin;C:\PROGRA~1\IBM\CLIENT~1;
              C:\PROGRA~1\IBM\CLIENT~1\Shared;C:\PROGRA~1\IBM\CLIENT~1\Emulator;
              * To start WebLogic Server, use a username and *
              * password assigned to an admin-level user. For *
              * server administration, use the WebLogic Server *
              * console at http://[hostname]:[port]/console *
              D:\bea1\user_projects_cluster\mydomain>"d:\bea1\jdk131_03\bin\java" -hotspot -Xm
              s32m -Xmx200m -Dweblogic.security.SSL.trustedCAKeyStore=d:\bea1\weblogic700\serv
              er\lib\cacerts -Dweblogic.Name="server2" -Dbea.home="d:\bea1" -Dweblogic.managem
              ent.username= -Dweblogic.management.password= -Dweblogic.management.server="10.1
              6.96.21:7001" -Dweblogic.ProductionModeEnabled= -Djava.security.policy="d:\bea1\
              weblogic700\server\lib\weblogic.policy" weblogic.Server
              <Sep 20, 2007 1:47:13 PM IST> <Info> <Security> <090065> <Getting boot identity
              from user.>
              Enter username to boot WebLogic server:weblogic
              Enter password to boot WebLogic server:
              Starting WebLogic Server...
              Connecting to http://10.16.96.21:7001...
              <Sep 20, 2007 1:47:25 PM IST> <Notice> <Security> <090082> <Security initializin
              g using realm myrealm.>
              <Sep 20, 2007 1:47:25 PM IST> <Notice> <WebLogicServer> <000328> <Starting WebLo
              gic Managed Server "server2" for domain "mydomain">
              Starting Cluster Service...
              <Sep 20, 2007 1:47:46 PM IST> <Notice> <Cluster> <000138> <Listening for announc
              ements from cluster mycluster on 237.0.0.1:7777>
              <Sep 20, 2007 1:47:46 PM IST> <Notice> <Cluster> <000133> <Waiting to synchroniz
              e with other running members of mycluster>
              <Sep 20, 2007 1:48:16 PM IST> <Notice> <Cluster> <000134> <Discovered and synchr
              onized with 1 other running members of mycluster>
              <Sep 20, 2007 1:48:17 PM IST> <Emergency> <WebLogicServer> <000350> <Unable to c
              reate a server socket on Channel Default for: 10.16.96.24/10.16.96.24, port: 900
              1. java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
              address 10.16.96.24/10.16.96.24 is incorrect or another process is using port 9
              001.>
              <Sep 20, 2007 1:48:18 PM IST> <Emergency> <Security> <090085> <Server failed to
              bind to any port such that it is not reachable from the console.>
              <Sep 20, 2007 1:48:18 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to i
              nitialize the server: Fatal initialization exception>
              The WebLogic Server did not start up properly.
              Reason: Fatal initialization exception
              D:\bea1\user_projects_cluster\mydomain>goto finish
              D:\bea1\user_projects_cluster\mydomain>ENDLOCAL
              D:\bea1\user_projects_cluster\mydomain>ENDLOCAL
              D:\bea1\user_projects_cluster\mydomain>

  • Deploying ADF application to a managed weblogic server - ADF security error

    Hi,
    Our group has written an ADF web application, which we are attempting to deploy to a managed weblogic server. Thus far, we have been unsuccessful. The application does successfully deploy to the AdminServer. Our setup:
    Weblogic version is 10.3.0. Domain name is adf_domain. We have installed the ADF (ADF version is 11.1.1.0.0), JSTL(1.2.0.1), and JSF(1.2.7.1) runtime libraries, and they are targeted to both the admin server AND the managed server, which is called CollabServer. This server communicates with the node manager and can be started and stopped via the admin console successfully. The AdminServer is on port 7101, and the CollabServer is on port 7104. We are not using SSL.
    application.xml:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
    version="5" xmlns="http://java.sun.com/xml/ns/javaee">
    <display-name>OracleRetailCollaboration</display-name>
    <module>
    <web>
    <web-uri>orc.war</web-uri>
    <context-root>orc</context-root>
    </web>
    </module>
    </application>
    weblogic-application.xml (as taken from the ear file):
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application.xsd" xmln
    s="http://www.bea.com/ns/weblogic/weblogic-application">
    <listener>
    <listener-class>oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener</listener-class>
    </listener>
    <library-ref>
    <library-name>adf.oracle.domain</library-name>
    </library-ref>
    </weblogic-application>
    weblogic.xml (as taken from the war file):
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ww
    w.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd">
    <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    <security-role-assignment>
    <role-name>valid-users</role-name>
    <principal-name>users</principal-name>
    </security-role-assignment>
    <library-ref>
    <library-name>jstl</library-name>
    <specification-version>1.2</specification-version>
    </library-ref>
    <library-ref>
    <library-name>jsf</library-name>
    <specification-version>1.2</specification-version>
    </library-ref>
    </weblogic-web-app>
    As I said, there are no deployment errors when we deploy to the admin server. However, we always see the following errors when deploying to the managed server:
    java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener
    etc.
    This error occurs when deploying via the <wldeploy> ant task included with weblogic, and when deploying the application manually via the admin console.
    So I removed this from weblogic-application.xml:
    <listener>
    <listener-class>oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener</listener-class>
    </listener>
    Which resolved the initial error (I assume there is some sort of bug that causes this workaround to be necessary). The next error is this:
    java.lang.ClassNotFoundException: oracle.adf.share.security.authentication.AuthenticationServlet
    Again, we don't get this error when deploying to the AdminServer - ONLY the managed server CollabServer.
    web.xml:
    <servlet>
    <servlet-name>adfAuthentication</servlet-name>
    <servlet-class>oracle.adf.share.security.authentication.AuthenticationServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
    </servlet>
    <servlet-mapping>
    <servlet-name>adfAuthentication</servlet-name>
    <url-pattern>/adfAuthentication/*</url-pattern>
    </servlet-mapping>
    I then added some adf jar files to the ear file, finally get this error message:
    java.lang.ClassNotFoundException: oracle.adf.share.jsp.ADFLibUtils
    Any ideas on how to resolve this? Thanks.
    Edited by: user10451099 on Apr 15, 2009 12:10 PM

    Dan,
    thanks fro reminding me :-)
    Here are the steps we had to take to get a managed WLS to run an adf application without copying any jar in the domain/lib directory:
    1. you still have to install the adf runtime to any server you want the adf application to deploy to
    2. open the admin console, select the managed server, and select the 'server start' tab in configutation settings.
    3. add /u01/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/bea/patch_jdev1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:
    /u01/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/bea/jrockit_160_05/lib/tools.jar:/u01/bea/wlserver_103/server/lib/weblogic_sp.jar:
    /u01/bea/wlserver_103/server/lib/weblogic.jar:/u01/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/u01/bea/wlserver_103/server/lib/webservices.jar:
    /u01/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/u01/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/u01/bea/jdeveloper/modules/features/adf.share_11.1.1.jar:
    /u01/bea/wlserver_103/common/eval/pointbase/lib/pbclient57.jar:/u01/bea/wlserver_103/server/lib/xqrl.jar:
    /u01/bea/patch_wls1030/profiles/default/sysext_manifest_classpath/weblogic_ext_patch.jar to the classpath edit box you have to change '/u01/bea/' with your bea home. The classpath should be on one line without the CR/LF i put in to make it readable.
    4. add -Xms256m -Xmx512m -da -Dplatform.home=/u01/bea/wlserver_103 -Dwls.home=/u01/bea/wlserver_103/server -Dweblogic.home=/u01/bea/wlserver_103/server
    -Ddomain.home=/u01/bea/user_projects/domains/naa_qs -Doracle.home=/u01/bea/jdeveloper -Doracle.security.jps.config=/u01/bea/user_projects/domains/naa_qs/config/oracle/jps-config.xml
    -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001
    -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=
    -Dweblogic.ext.dirs=/u01/bea/patch_wls1030/profiles/default/sysext_manifest_classpath:/u01/bea/patch_jdev1111/profiles/default/sysext_manifest_classpath:/u01/bea/patch_cie660/profiles/default/sysext_manifest_classpath
    -Dweblogic.management.username=weblogic -Dweblogic.management.password=******** -Dweblogic.Name=GESTIS_QS
    -Djava.security.policy=/u01/bea/wlserver_103/server/lib/weblogic.policy to the 'Arguments' edit box. As with the calsspath change '/u01/bea' to your bea home and change the domain name (in our case 'naa_qs') to your domain name. change the managementuser and passwort to your needs. As whith the classpath I put some CR/LF into the code section to make it readable.
    5. save the changes and restart the server
    Essentially all we copied the arguments from the admin server start script in addition to adding the class path.
    Timo

  • Failed to stop Managed Weblogic server ..

    Hello,
      I use Weblogic in OBIEE, i try to stop managed weblogic server but  it's failed, can you help me to undestand and fix this issue :
    > /servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/bin/stopManagedWebLogic.sh bi_server1 t3://srv-reporting-4.ppd.domaine.com:7001
      logs :
    SVR_GRP =
    Stopping Weblogic Server...
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Please enter your username :weblogic
    Please enter your password :
    Connecting to t3://srv-reporting-4.ppd.domaine.com:7001 with userid weblogic ...
    The CompatabilityMBeanServer is not initialized properly.
    This might happen if the CompatabilityMBeanServer is
    disabled via the JMXMBean.
    To view the root cause exception use dumpStack()
    WLST detected that the RuntimeMBeanServer is not enabled. This
    might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
    Please ensure that this MBeanServer is enabled. Online WLST cannot
    function without this MBeanServer.
    This Exception occurred at Tue Feb 17 17:29:34 CET 2015.
    java.lang.NullPointerException
            at java.util.StringTokenizer.<init>(StringTokenizer.java:182)
            at java.util.StringTokenizer.<init>(StringTokenizer.java:219)
            at weblogic.utils.StringUtils.splitCompletely(StringUtils.java:119)
            at weblogic.socket.utils.ProxyUtils.getProxySocket(ProxyUtils.java:178)
            at weblogic.socket.utils.ProxyUtils.getClientProxy(ProxyUtils.java:223)
            at weblogic.socket.SocketMuxer.newClientSocket(SocketMuxer.java:381)
            at weblogic.socket.ChannelSocketFactory.createSocket(ChannelSocketFactory.java:86)
            at weblogic.socket.BaseAbstractMuxableSocket.createSocket(BaseAbstractMuxableSocket.java:133)
            at weblogic.rjvm.t3.MuxableSocketT3.newSocketWithRetry(MuxableSocketT3.java:214)
            at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:383)
            at weblogic.rjvm.t3.ConnectionFactoryT3.createConnection(ConnectionFactoryT3.java:34)
            at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1784)
            at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1424)
            at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:443)
            at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
            at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
            at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
            at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
            at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
            at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
            at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
            at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
            at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
            at weblogic.jndi.Environment.getContext(Environment.java:315)
            at weblogic.jndi.Environment.getContext(Environment.java:285)
            at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
            at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
            at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
            at javax.naming.InitialContext.init(InitialContext.java:223)
            at javax.naming.InitialContext.<init>(InitialContext.java:197)
            at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:178)
            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.management.scripting.WLSTHelper.lookupMBeanServerConnection(WLSTHelper.java:678)
            at weblogic.management.scripting.WLSTHelper.initRuntimeServerConnection(WLSTHelper.java:398)
            at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:315)
            at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
            at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
            at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at org.python.core.PyReflectedFunction.__call__(Unknown Source)
            at org.python.core.PyMethod.__call__(Unknown Source)
            at org.python.core.PyObject.__call__(Unknown Source)
            at org.python.core.PyObject.invoke(Unknown Source)
            at org.python.pycode._pyx4.connect$1(<iostream>:16)
            at org.python.pycode._pyx4.call_function(<iostream>)
            at org.python.core.PyTableCode.call(Unknown Source)
            at org.python.core.PyTableCode.call(Unknown Source)
            at org.python.core.PyFunction.__call__(Unknown Source)
            at org.python.pycode._pyx15.f$0(/servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/shutdown.py:6)
            at org.python.pycode._pyx15.call_function(/servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/shutdown.py)
            at org.python.core.PyTableCode.call(Unknown Source)
            at org.python.core.PyCode.call(Unknown Source)
            at org.python.core.Py.runCode(Unknown Source)
            at org.python.util.PythonInterpreter.execfile(Unknown Source)
            at weblogic.management.scripting.WLST.main(WLST.java:124)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at weblogic.WLST.main(WLST.java:29)
    Problem invoking WLST - Traceback (innermost last):
      File "/servers/bipublisher/bip11/user_projects/domains/bifoundation_domain/shutdown.py", line 6, in ?
      File "<iostream>", line 22, in connect
      File "<iostream>", line 646, in raiseWLSTException
    WLSTException: Error occured while performing connect : "Cannot connect to WLST."
    Use dumpStack() to view the full stacktrace
    Regards
    Djms

    Hi
    Check that you are able to ping or telnet  the machine srv-reporting-4.ppd.domaine.com from the Admin Server machine .
    As from the Error message its not able to conenct to the machine and the port number .
    WLSTException: Error occured while performing connect : "Cannot connect to WLST
    Check the network connectivity and then try to stop the managed Server it will stop.
    Hope it helps

  • BUG: Entering a "version" when deploying to a WebLogic server doesn't work

    By default when deploying to a weblogic server the "Version" is set to v2.0. If you change that to something like v2.1 when the application is deployed, the deployment logs still show the Version=2.0. What needs to be done to get the Version in deployment to accept the changes on the deployment form?

    Sorry, I wasn't clear. This is a Portal application deployed using MDS. So it doesn't have the file referenced in that blog post. The Version field I'm referring to is on the form that pops up to set the MDS repository. For reasons unknown it will always come up v2.0 even during the first deployment. Regardless of what I change it to the Version always equals 2.0 in the deployment logs.

  • When i restart the weblogic server 9.2,all messages in Topic get cleared

    Hi,
              When i restart the weblogic server 9.2,all messages in Topic get cleared for inactive dudrable subscribers.
              Please advise what the issue here.
              Thanks.

    Hi Tom, Thanks you so much for spending your time on this issue.
              A)I didn't specify any persistent mode.so i believe default mode is "Persistent"
              B) when i click on durable subscribers link on the corrersponding Topic it is showing 2 users.
              actually these durable subscribers are created by executing below code after look up the Topic.
              TopicSubscriber tsub = ts.createDurableSubscriber(topic,"mysub");
              C) Delivery Mode Override is set to "No-Delivery".
              but Time-to-Live Override is set to 21600000 .
              i assume Time-to-Live is causing problem.
              Please advise.
              Thanks.
              Edited by rodex at 03/25/2008 3:55 PM

  • Bad load arguments supplied when starting up the Reports Server

    Dear All,
    In report60\server\<filename>.ora
    Following were the contents :
    maxconnect=20
    cachedir="d:\Oracle\806\REPORT60\server\cache"
    cachesize=50
    minengine=0
    initengine=0
    maxengine=1
    maxidle=30
    security=1
    englife=50
    We chnaged it to
    maxconnect=20
    cachedir="d:\Oracle\806\REPORT60\server\cache"
    cachesize=50
    minengine=1
    initengine=0
    maxengine=5
    maxidle=30
    security=1
    englife=50
    We imideatly got result we checked it put it on live application server.
    Everything was smooth but next day we got calls/email from user saying report were slow. when we checked the windows process on application server rwmts60 was occuping 50% of memory so we killed that process. We restrarted the report service but was unable to restart.Then we saw the report log as follows :
    *** 2008-07-29 17:36:51 -- Server started up an engine. (Rep60_WEBDB-01)
    *** 2008-07-29 17:36:53 -- Server engine crashed. (Rep60_WEBDB-01)
    *** 2008-07-29 17:38:18 -- Server started up an engine. (Rep60_WEBDB-01)
    *** 2008-07-29 18:39:44 -- Server shutting down an engine. (Rep60_WEBDB-01)
    *** 2008-07-30 09:13:19 -- Server engine cannot be started. (Rep60_WEBDB-01)
    *** 2008-07-30 09:15:24 -- Server engine cannot be started. (Rep60_WEBDB-01)
    *** 2008-07-30 09:17:29 -- Server engine cannot be started. (Rep60_WEBDB-01)
    *** 2008-07-30 09:19:34 -- Server engine cannot be started. (Rep60_WEBDB-01)
    *** Bad load arguments supplied when starting up the Reports Server
    *** Bad load arguments supplied when starting up the Reports Server
    *** Bad load arguments supplied when starting up the Reports Server
    *** Bad load arguments supplied when starting up the Reports Server
    then we changed back our ora file to
    maxconnect=20
    cachedir="d:\Oracle\806\REPORT60\server\cache"
    cachesize=50
    minengine=0
    maxengine=1
    initengine=0
    maxidle=30
    security=1
    englife=50
    And restarted the service which restarted suceesfully.
    My question is i had changed maxengine=5 and minengine=1 on 20- JUL-2008 around 16:00 .Did this happen b'coz of this 2 parameters.
    Kindly advice.
    Thanking You in anticipation.
    Best Regards,
    Devendra

    Hello Mahendraji,
    Thanks for your reply.
    I may ask some basic question please accomodate me.
    <<$RACLE_HOME\reports\conf\apple_report.conf>>
    I have Application server 9i version 1.0.2.0.0 (isuite).
    I have installed in D drive
    In this drive a folder d:\orcale is created.
    Inside of this i don't have any folder called "reports"
    i have folder called "806"
    \\webdb-01\D-Drive\Oracle\806
    Inside of which i have folder "report60"
    \\webdb-01\D-Drive\Oracle\806\REPORT60
    Inside of which i have folder "SERVER"
    \\webdb-01\D-Drive\Oracle\806\REPORT60\SERVER
    In which i found "Rep60_WEBDB-01.ora" , "Rep60_WEBDB-01.log" and "cgicmd.dat"
    and 2 folders "CACHE" and "security".
    I am confused as you said that the file name should be Rep60_WEBDB-01.CONF but i have Rep60_WEBDB-01.ora are they one and the same . If yes is the extension b'coz i have older version of 9i i.e 1.0.2.0.0 (isuite).
    if no where i how i can search this .
    This Rep60_WEBDB-01.ora file doesnot have parameter "engineResponseTimeOut" if i add it will it work.
    Your explanation regarding "engineResponseTimeOut" is clear.
    Maximum Time taken by our report is 20 minutes. But sometimes when report hangs or SQL takes more time than normal due to the environment so the max time might change to 25 or 30 minutes in such a case should we keep it at 45 minutes to avoid any unneccessary termination.
    <<Note:
    It is always better to run batch reports on a separate server with different engineResponseTimeOut values. Do not submit interactive and batch reports to same server.>>
    If i create a seperate application server how can i send reports requested by user to batch in this seperrate server.
    What should be the criteria of report to be redirected to seperate server?
    What do mean by "submit interactive" and "submit batch"
    My interpretation is when we click on submit query button it is "submit interactive" is it correct.
    I am not clear about "submit batch"
    I know there might be some silly questions but please do accomodate.
    Kindly advice.
    Thanks.
    Regards,
    Devendra Shelke

  • OSB: problem when starting a managed server in an OSB cluster

    Hi,
    I used the configuration wizard to setup a very simple domain, containing a cluster with a managed server. When I start the managed server from the console I get prompted for the boot user and password. I specify the values I defined during the installation (weblogic user and custom passwort). After some time the managed server exists with the following exception:
    ####<21.04.2010 19.25 Uhr CEST> <Critical> <WebLogicServer> <DEMUC10525> <ManagedServer1> <main> <<WLS Kernel>> <> <> <1271870735741> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
    weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
         at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    What is its problem and how do I fix it? I have not configured anything special in the domain - just the cluster, a single machine and the managed server and admin server targeted at this machine.
    The admin server starts without these problems. I also tried copying the boot.properties from the admin server to the managed server without any success - the same problem.
    Regards
    Dimo
    Edited by: dimo velev on 21.04.2010 11:24

    Hi Anuj,
    it turned out to be an OSB related problem - WLS forum would not have been able to help.
    The startManagedWebLogic script should be run only within an environment which has been correctly setup using the domain setDomainEnv script. This seems to add some classpaths and stuff like this which, if missing, produces the exception - it actually has absolutely nothing to do with the user and password being wrong.
    If you are using a node manager to start the managed servers then it should also be run within an evironment correctly setup with the domain's setDomainEnv script.
    Best regards
    Dimo

  • Error message seen when starting a managed server (dsp_config.ear)

    Hi ,
    I am having issues when i start the managed server under the admin server.
    Seems like when i undeploy dsp_config.ear the managed server seems to start without any issues.
    But since the dsp_config.ear is removed the dspconsole is messed up.
    The admin server runs fine without any issues with or without dsp_config.ear deployment.
    The error trace
    ####<Jul 27, 2009 9:36:01 AM EDT> <Warning> <DeploymentService> <wdcsn383a> <cashflow1MS1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (
    self-tuning)'> <<WLS Kernel>> <> <> <1248701761543> <BEA-290064> <Deployment service servlet encountered an Exception while handling the deployment service m
    essage for request id "-1" from server "BEAAdminServer". Exception is: "java.lang.ClassNotFoundException: com.bea.wli.config.deployment.server.ServerVersion:
    This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed o
    n a server that is part of a cluster is also deployed on all other members of that cluster
    at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:218)
    at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:85)
    at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:61)
    at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
    at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
    at java.util.HashMap.readObject(HashMap.java:1030)
    at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
    at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
    at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
    at weblogic.deploy.service.internal.DomainVersion.readExternal(DomainVersion.java:180)
    at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
    at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readMessage(DeploymentServiceMessage.java:325)
    at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readExternal(DeploymentServiceMessage.java:301)
    at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
    at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
    at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
    at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
    at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.handleDeploymentServiceMessage(DeploymentServiceServlet.java:618)
    at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.internalDoPost(DeploymentServiceServlet.java:235)
    at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.access$000(DeploymentServiceServlet.java:77)
    at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet$1.run(DeploymentServiceServlet.java:210)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.doPost(DeploymentServiceServlet.java:207)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    Can anybody help me on this one?
    it seems more of ODSI issue than weblogic server issue.

    it sounds like you are deploying dsp_config.ear to a domain/server that is not ODSI-enabled.
    com.bea.wli.config.deployment.server.ServerVersion is in <modules>/com.bea.common.configfwk.wlinterop_10.3.0.0.jar which is referenced by <modules>/features/odsi.server.modules_10.3.0.0.xml and used by com.bea.dsp.management.impl.DomainServiceImpl

  • Multicast Error When Starting Managed Servers

    Environment: HP-UX 11i, Weblogic 8.1 SP1.
              We're getting the following error when we start managed servers in our clustered environment:
              <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
              37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
              java.net.SocketException: Can't assign requested address
              at java.net.PlainDatagramSocketImpl.join(Native Method)
              at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
              at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
              at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
              at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
              at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
              at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
              at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
              at weblogic.Server.main(Server.java:32)
              >
              We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
              1) Different multicast addresses/ports;
              2) The util.multicastTest app.
              3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
              Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
              Thanks in advance for any help...
              Brian
              

    Environment: HP-UX 11i, Weblogic 8.1 SP1.
              We're getting the following error when we start managed servers in our clustered environment:
              <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
              37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
              java.net.SocketException: Can't assign requested address
              at java.net.PlainDatagramSocketImpl.join(Native Method)
              at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
              at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
              at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
              at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
              at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
              at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
              at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
              at weblogic.Server.main(Server.java:32)
              >
              We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
              1) Different multicast addresses/ports;
              2) The util.multicastTest app.
              3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
              Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
              Thanks in advance for any help...
              Brian
              

  • Memleak cannot work when start the management server by ctrlhandler.act

    Hi, all
    I use ctrlhandler.act to start a management server on running system. when start the memleak detector, i got the error message on server output:
    [JRockit] ManagementServer started trend analysis
    java.lang.NullPointerException
    Continuing ...
    java.lang.Exception: discarding statement XMLEncoder0.writeObject(HeapHistogram0);
    Continuing ...
    but when I started the management server with command line -Xmanagement. all is ok. What's the matter?
    Thanks a lot!

    Sorry, the jrocki version is 1.4.2_05 and 1.4.2_08.
    And the os: windows XP professional and Redhat AD 7.2
    And the weblogic server version is 'weblogic8.1 sp3'
    any suggestion? Thank you!

  • Error when I startup the Weblogic server.

    Hi
    Look I chance my proxy configuration 'Cause before I have a free LAN to navigate on internet. Since then, when I want to startup the weblogic service the following error :
    Enter username to boot WebLogic server:weblogic
    Enter password to boot WebLogic server:
    <14-sep-2010 20H08' PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <14-sep-2010 20H08' PET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <14-sep-2010 20H08' PET> <Notice> <Log Management> <BEA-170019> <The server log file /u01/oracle/user_projects/domains/CoreNevadoDomain/servers/CoreNevadoAdminServer/logs/CoreNevadoAdminServer.log is opened. All server side log events will be written to this file.>
    <14-sep-2010 20H08' PET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <14-sep-2010 20H08' PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <14-sep-2010 20H08' PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    *<14-sep-2010 20H14' PET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application '01-eng-CoreNevadoEngine' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(engine-CoreNevadoEngine.jar)*
    *[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:*
    *ParseError at [row,col]:[5,148]*
    Message: Tried all: '2' addresses, but could not connect over HTTP to server: 'www.oracle.com', port: '80'..
    weblogic.application.ModuleException: Exception preparing module: EJBModule(engine-CoreNevadoEngine.jar)
    [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
    ParseError at [row,col]:[5,148]
    Message: Tried all: '2' addresses, but could not connect over HTTP to server: 'www.oracle.com', port: '80'.
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
    Truncated. see log file for complete stacktrace
    javax.xml.stream.XMLStreamException: ParseError at [row,col]:[5,148]
    Message: Tried all: '2' addresses, but could not connect over HTTP to server: 'www.oracle.com', port: '80'
    at com.sun.xml.stream.XMLReaderImpl.next(XMLReaderImpl.java:560)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.isDTDBased(EjbDescriptorReaderImpl.java:451)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.parseWLDD(EjbDescriptorReaderImpl.java:525)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWeblogicEjbJarXML(EjbDescriptorReaderImpl.java:388)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:196)
    Truncated. see log file for complete stacktrace
    >
    14-sep-2010 20:14:48 com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    14-sep-2010 20:14:48 com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    ********* Oracle® BPM - WorkSpace Administrator (Version 10.3.1.0.0 Service Pack 1 Build #94375) is starting *********
    Checking Java Runtime Enviroment ...Ok
    Initializing enviroment...Ok
    Loading Plugins for Workspace Administrator ...Ok
    log4j:WARN No appenders could be found for logger (com.sun.faces.config.ConfigureListener).
    log4j:WARN Please initialize the log4j system properly.
    OpenLog: verbosity level = 2
    OpenLog: Registered application name: OpenControls.srvapptest
    OpenControls.srvapptest
    help me,plz.
    Thanks

    Hi,
    You can write it inside your ManagedServers Start Script or even you can write it in your "setDomainEnv.sh"(if u are in UNIX OS) or in "setDomainEnv.cmd (if it is WINDOWS)"as described in the below Image:
    http://weblogic-wonders.com/weblogic/wp-content/uploads/2010/09/setting_JAVA_JOME_In_script.jpg
    The Only difference will be....in the JAVA_OPTION as below:
    Unix OS case below
    *JAVA_OPTIONS=${JAVA_OPTIONS} -Dhttp.proxyHost=YourProxyHostName -Dhttp.proxyPort=yourProxyPort*
    Windows OS Case below
    set JAVA_OPTIONS=%JAVA_OPTIONS%    -Dhttp.proxyHost=YourProxyHostName  -Dhttp.proxyPort=yourProxyPort
    Thanks
    Jay SenSharma

  • Error  when Start domain in Weblogic 10.3.3 RedHat 5.0 64Bits

    I followed the steps of creating the Domain Patterns, but when I run the start the following error occurs:
    ./startWebLogic.sh
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m
    WLS Start Mode=Development
    CLASSPATH=/usr2/Oracle/Middleware/patch_wls1033/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr2/Oracle/Middleware/patch_ocp353/profiles/default/sys_manifest_classpath/weblog ic_patch.jar:/usr2/jdk1.6.0_21/lib/tools.jar:/usr2/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/usr2/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/usr2/Oracle/Middl eware/modules/features/weblogic.server.modules_10.3.3.0.jar:/usr2/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/usr2/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all. jar:/usr2/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/usr2/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/usr2/Oracle/Middleware/wlserve r_10.3/server/lib/xqrl.jar
    PATH=/usr2/Oracle/Middleware/wlserver_10.3/server/bin:/usr2/Oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/usr2/jdk1.6.0_21/jre/bin:/usr2/jdk1.6.0_21/bin:/usr2/jdk1.6.0_21/bin:/usr/kerb eros/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/dell/srvadmin/bin:/opt/dell/srvadmin/sbin:/root/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_21"
    Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
    Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
    Starting WLS with line:
    /usr2/jdk1.6.0_21/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m -Dweblogic.Name=AdminServer -Djava.security.policy=/usr2/Oracle/Middl eware/wlserver_10.3/server/lib/weblogic.policy -Xverify:none -da -Dplatform.home=/usr2/Oracle/Middleware/wlserver_10.3 -Dwls.home=/usr2/Oracle/Middleware/wlserver_10.3/server -Dweblogic.ho me=/usr2/Oracle/Middleware/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/usr2/Oracle/Middl eware/patch_wls1033/profiles/default/sysext_manifest_classpath:/usr2/Oracle/Middleware/patch_ocp353/profiles/default/sysext_manifest_classpath weblogic.Server
    <Sep 29, 2010 4:01:59 PM BRT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 17.0-b16 from Sun Microsystems Inc.>
    <Sep 29, 2010 4:02:16 PM BRT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
    <Sep 29, 2010 4:02:16 PM BRT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Sep 29, 2010 4:02:16 PM BRT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Sep 29, 2010 4:02:16 PM BRT> <Notice> <LoggingService> <BEA-320400> <The log file /usr2/Oracle/Middleware/user_projects/domains/base_domain3/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <Sep 29, 2010 4:02:16 PM BRT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /usr2/Oracle/Middleware/user_projects/domains/base_domain3/servers/AdminServer/logs/AdminServer.log00002. Log messages will continue to be logged in /usr2/Oracle/Middleware/user_projects/domains/base_domain3/servers/AdminServer/logs/AdminServer.log.>
    <Sep 29, 2010 4:02:16 PM BRT> <Notice> <Log Management> <BEA-170019> <The server log file /usr2/Oracle/Middleware/user_projects/domains/base_domain3/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
    <Sep 29, 2010 4:02:18 PM BRT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError.
    weblogic.security.service.SecurityServiceException: java.lang.ExceptionInInitializerError
    at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)
    at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.ExceptionInInitializerError
    at com.octetstring.vde.util.guid.GuidGenerator.nextGuidInBytes(GuidGenerator.java:125)
    at com.octetstring.vde.util.guid.Guid.<init>(Guid.java:84)
    at com.octetstring.vde.backend.standard.BackendStandard.add(BackendStandard.java:379)
    at com.octetstring.vde.backend.BackendHandler.add(BackendHandler.java:460)
    at com.octetstring.vde.util.LDIF.importLDIF(LDIF.java:279)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.NullPointerException
    at java.lang.System.arraycopy(Native Method)
    at com.octetstring.vde.util.guid.GuidParamGenerator.generateNodeID(GuidParamGenerator.java:47)
    at com.octetstring.vde.util.guid.GuidStateManager.initializeGUIDParameters(GuidStateManager.java:59)
    at com.octetstring.vde.util.guid.GuidStateManager.<init>(GuidStateManager.java:30)
    at com.octetstring.vde.util.guid.GuidStateManager.<clinit>(GuidStateManager.java:23)
    Truncated. see log file for complete stacktrace
    >
    <Sep 29, 2010 4:02:18 PM BRT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Sep 29, 2010 4:02:18 PM BRT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    <Sep 29, 2010 4:02:18 PM BRT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Sep 29, 2010 4:02:18 PM BRT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Sep 29, 2010 4:02:18 PM BRT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Could anyone help me solve this problem?
    Tks.

    You should ensure that the hostname of your machine resolves to an IP address either via DNS or in your hosts file.

  • Getting JMS Exception while starting the managed servers

    Hi ,
    I have Savvion BPM tool hosted on WebLogic server 10.3 version.Before the manage servers coming to Running state its throwing the below mention warning message.Can anybody help me to identify what could be the reason the managed server the below exceptions.
    Thanks in advance...
    <Jun 19, 2012 3:54:32 AM EDT> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server sbmejb2.>
    <Jun 19, 2012 3:54:33 AM EDT> <Notice> <Cluster> <BEA-000164> <Synchronized cluster JNDI tree from server sbmejb2.>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    *<Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLServiceMDB is unable to connect to the J*
    MS destination: jms/BLAdminTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster addres
    s "sbmejb1,sbmejb2">
    <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCacheSyncMDB is unable to connect to the
    JMS destination: jms/BLCacheSyncTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLSessionMDB is unable to connect to the J
    MS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.177.16.126:16103 for pr
    otocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    <Jun 19, 2012 3:54:34 AM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "sbmejb1" for domain "sb
    m76" running in Production Mode>
    <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLBizStoreMDB is unable to connect to the
    JMS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:34 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLCheckDueMDB is unable to connect to the
    JMS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLEmailMDB is unable to connect to the JMS
    destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: BLResumeWSMDB is unable to connect to the
    JMS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: MConsoleServiceMDB is unable to connect to
    the JMS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:41 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EPServiceMDB is unable to connect to the J
    MS destination: jms/SBMTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:42 AM EDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EventReaderBean is unable to connect to th
    e JMS destination: jms/BPAdminTopic. The Error was:
    weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.jms.common.JMSException: could not find Server sbmejb1
    Nested exception: weblogic.messaging.dispatcher.DispatcherException: could not find Server sbmejb1
    Nested exception: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:sbmejb1'. Resolved 'w
    eblogic.messaging.dispatcher'; remaining name 'S:sbmejb1'>
    <Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Jun 19, 2012 3:54:42 AM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

    Hi Rohit,
    Thanks for your response..
    Below is the BLAdminTopic configuration.Please let me know if you need any further info.
    Topic:BLAdminTopic
    Type:Distributed Topic
    JNDI:jms/BLAdminTopic
    Sub Deployment :N/A
    Target:N/A
    BLAdminTopic@jmsnode1BL Topic jms/BLAdminTopic@jmsnode1BL BLAdminTopic@jmsnode1BL jmsnode1BL
    BLAdminTopic@jmsnode2BL Topic jms/BLAdminTopic@jmsnode2BL BLAdminTopic@jmsnode2BL jmsnode2BL
    Regards,
    Jyotiranjan

Maybe you are looking for

  • Reg: consistency check in recordset structure validation

    Hi all, I am doing FCC to FCC scenario, i am getting this error. Help me out, it is very urgent for me. Sender Adapter v2723 for Party '', Service 'bs_text2text': Configured at 2007-08-21 08:00:49 UTC History: - 2007-08-21 09:29:06 UTC: Retry interva

  • IMAGEICON help

    anybody know how to set image icon as a background to put inside a panel..ANybody could give help

  • Costing sheet assignment to notification

    hi there i would like to know if it is possible to assign a CO costing sheet to a quality notification in quality management? this would be purely for analysis purpose. no real postings would be made. thanks

  • Integration Repository 12i & BPEL

    I need to know which services will be exposed in Oracle Integration Repository that will be shipped with Oracle E-Business Suite 12i? Where can I find this catalog? In addition, if I am using Oracle BPEL for my orchestration, is it possible to expose

  • Help after using verify disk with MacBook Pro 2009

    Hello, I was running verify disk and got this massage: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk. Verifying volume "Macintosh HD"