Problems starting WLS 6.1 on solaris...

I have installed WLS in the sun solaris machine and have problems starting up a mydomain
test server. I am getting:
weblogic.management.configuration.ConfigurationException: - with nested exception:
[weblogic.security.internal.FileUtilsException: couldn't create temporary file for
SerializedSystemIni.dat, .new, /config/mydomain - with nested exception:
[java.io.IOException: No such file or directory]]
I am suspecting the problem might be that we have installed it as root and then change
the rights to weblogic. Any pointers are greatly appreciated.
Thanks.

I'm guess you changed owner of config/mydomain to weblogic? To
confirm - try touching/create a test file in config/mydomain,
i.e. touch mytest.perm;ls -l mytest.perm;rm mytest.perm
You could start weblogic with truss:
truss -t open -o /tmp/truss.out -f "your start command"
Then examine /tmp/truss.out
"Dariusz" <[email protected]> wrote in message news:<3d08b130$[email protected]>...
I have installed WLS in the sun solaris machine and have problems starting up a mydomain
test server. I am getting:
weblogic.management.configuration.ConfigurationException: - with nested exception:
[weblogic.security.internal.FileUtilsException: couldn't create temporary file for
SerializedSystemIni.dat, .new, /config/mydomain - with nested exception:
[java.io.IOException: No such file or directory]]
I am suspecting the problem might be that we have installed it as root and then change
the rights to weblogic. Any pointers are greatly appreciated.
Thanks.

Similar Messages

  • Problems starting WLS 7 server ... checkLicense NullPointerException

    Hi there,
    We have a clustered environment running WebLogic Server 7.0 Service Pack 4. In our cluster we're running two WLS instances essentially as webservers, to serve up static content.
    Starting and stopping the WLS instances is done using scripts written by a group of now-departed developers (we are not using NodeManager).
    The problem that we're having is that the "webserver" instances are very difficult to start up, and may require seven or eight attempts to start properly. Most of the time, we see the following NullPointerException in the server log:
    ====================================================
    <9-Nov-04 12:36:30 EST PM> <Notice> <WebLogicServer> <000360> <Server started in RUNNING mode>
    <9-Nov-04 12:36:30 EST PM> <Emergency> <WebLogicServer> <000209> <ListenThread.run() failed: java.lang.NullPointerException
    java.lang.NullPointerException
         at weblogic.t3.srvr.ListenThread.checkLicense(ListenThread.java:595)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:333)
    >
    <9-Nov-04 12:36:30 EST PM> <Emergency> <WebLogicServer> <000210> <The WebLogic Server is no longer listening for connections. You should probably restart it.>
    ====================================================
    If WebLogic was having a hard time finding the license.bea file, I would expect that something more user-friendly than a NullPointerException would occur. Also, a simple problem with locating the license file doesn't really explain why the server eventually does come up properly, despite the fact that it can sometimes take many attempts.
    Unfortunately, since these servers are running in production we don't have the luxury to start and stop them at will to perform testing.
    Does anyone have any hints as to what might be causing this issue? Any advice would be much appreciated.
    Regards,
    jodym

    I'm guess you changed owner of config/mydomain to weblogic? To
    confirm - try touching/create a test file in config/mydomain,
    i.e. touch mytest.perm;ls -l mytest.perm;rm mytest.perm
    You could start weblogic with truss:
    truss -t open -o /tmp/truss.out -f "your start command"
    Then examine /tmp/truss.out
    "Dariusz" <[email protected]> wrote in message news:<3d08b130$[email protected]>...
    I have installed WLS in the sun solaris machine and have problems starting up a mydomain
    test server. I am getting:
    weblogic.management.configuration.ConfigurationException: - with nested exception:
    [weblogic.security.internal.FileUtilsException: couldn't create temporary file for
    SerializedSystemIni.dat, .new, /config/mydomain - with nested exception:
    [java.io.IOException: No such file or directory]]
    I am suspecting the problem might be that we have installed it as root and then change
    the rights to weblogic. Any pointers are greatly appreciated.
    Thanks.

  • Problems starting WLS on XP - Unable to bind to port

    Hi
    I recently changed my development environment from W2000 to XP.
    Apparently everything works as before.
    However, when I start WLS again shortly after stopping it (either by console or
    CTRL^C) I get the following error
    <01-10-2003 14:48:40 CEST> <Emergency> <WebLogicServer> <BEA-000351> <Unable to
    create a server socket on Channel Default for port: 28041. j
    ava.net.BindException: Address in use Perhaps another process is using port 28041.>
    <01-10-2003 14:48:40 CEST> <Emergency> <Security> <BEA-090085> <Server failed
    to bind to the configured port. The port may already be used b
    y another process.>
    <01-10-2003 14:48:40 CEST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to
    initialize the server: Server failed to bind to the requeste
    d port. See preceeding log message for details.>
    This situation times out after an unpredictable delay (5-20 min) - and I can restart
    my WLS.
    Does anybody know how to resolve this problem.
    Regards
    Peter

    Hi Werner,
    SYSLOG is UDP port 514.  Normally this means that some other program is running and using port 514.
    Some of the TFTP servers are also SYSLOG servers and will "listen" on this port.
    You can see if port 514 is listening with Fabric Manager not running.
    To find out what is using port 514:
    (a)     Open a command prompt window.  From Start / Run enter: cmd
    (b)     From the command prompt enter: netstat -ano
    (c)      Note the PID (process identifier) associated with the ports you are  concerned about.  (Also note the Local Address, Foreign Address,  Protocol and State.)
    (d)     Then do ctrl-alt-del to bring up the Windows Task Manager.
    (e)     In Windows Task Manager, select the Processes tab.
    (f)      Look for the PID you noted when you did the netstat in step (c).  Look  to left to the image name and that tells you which process has that PID.
    - If you dont see a PID column, click on View / Select Columns.  Make sure PID is selected.  Click OK.
    - Make sure Show processes from all users is selected.
    Now you can see what process is using port 514.  FM would be listed as javaw.exe ( java exec without a console window ).
    Best regards,
    Jim

  • Problem Starting WLS 5.1 from windows 2000 program group

    Hi
    I couldn't able to start Weblogic server 5.1 from windows 2000 program
    group(start > Programs > Weblogic 5.10 > Weblogic Server). I can start WLS
    without any problem from the console . I've check every configuration and
    environment setting, the problem still come out. Whenever I start WLS from
    program group , a window dialog with error messages will come out , here's
    the error messages :
    wlserver.exe - Application Error
    The instruction at "0x04d5d0d6" referenced memory at
    "0x00000000". The memory could not be "written".
    Click on OK to terminate the program
    Click on CANCEL to debug the program
    Any suggestions/solution will be appreciated .
    Thanks
    Chew Leong
    [email protected]

    look for weblogic.system.password property in your weblogic.properties
    file and see what's in there.
    Shailesh Mungikar wrote:
    I am trying to install WLS 5.1 SP12 on my Windows 2000 machine.
    I have WLS 6.1 already installed my PC.
    When I try to install, at the very end when
    "System" password required
    dialog pops up, I get another dialog box saying
    WLPASS~1.exe Application Error
    The exception Floating point division by zero (0xc000008e) occured in
    the application at location 0x50147c14
    When I press OK, it kill the "System password" dialog.
    The installation seems to be complete.
    If I go ahead and try to start weblogic, I get Exceptio
    java.security.AccessControlException: access denied
    (java.lang.RuntimePermission createSecurityManager)
    Any solution/workaround?
    thanks,
    _shailesh

  • Problem starting wls 6.1 sp2

    Hi
    I have developed an appliaction using wls 6.1 sp2 on w2k, which I want to migrate
    to Solaris 8.
    I have modified my windows statup scripts to Solaris, but I get a strange error
    when starting weblogic. I am starting the server as root and my weblogic.policy
    file is modified according to my installation.
    Has anybody encountered anything similar?
    <Feb 20, 2002 12:08:09 PM CET> <Critical> <Management> <Unable to deploy an internal
    management web application - <all-internal-apps>. Managed servers may be unable
    to start.
    java.io.FileNotFoundException: ./config/Certifikat/.wlstaging/wl_management_internal2.war
    (No such file or directory)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:62)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:132)
    at weblogic.management.mbeans.custom.ApplicationManager.stageGlobalWarFile(ApplicationManager.java:398)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:334)
    at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy35.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
    at weblogic.management.Admin.finish(Admin.java:561)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
    at weblogic.Server.main(Server.java:35)
    >
    My startup script is as follows
    bash-2.03$ more startWeblogic.sh
    #!/usr/bin/bash
    # Set user-defined variables.
    export PROJECT=postdanmark
    export ENVIRONMENT=test
    export RELEASE_DIR=/opt/projects/$PROJECT/$ENVIRONMENT/lib
    export JAVA_HOME=/opt/jdk/j2sdk1_3_1_02
    export WEBLOGIC_HOME=/opt/bea/weblogic/6.1
    export PATH=$WEBLOGIC_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:.:$PATH
    export CLASSPATH=$RELEASE_DIR/internal/util/1.0/Util.jar
    export CLASSPATH=$CLASSPATH:$WEBLOGIC_HOME/lib/weblogic.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/sun/jaxb/1.0ea/lib/jaxb-rt-1.0-ea.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/postdanmark/1.0/PostDanmarkPC.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/EntrustCAEjb/1.0/EntrustCAEjb.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/websupport/1.0/WebSupport.jar
    export CLASSPATH=$CLASSPATH:/opt/projects/$PROJECT/$ENVIRONMENT/batch/properties
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/corba/interfaces/entrustca/1.2/EntrustCA.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/mysql/jdbc/2.0.4/mm.mysql-2.0.4-bin.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entbase.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entuser.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entp7.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entmisc.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entcertlist.jar
    echo off
    echo *********************************************
    echo * Starting weblogic application server *
    echo *********************************************
    # Set WLS_PW equal to your system password for no password prompt server startup.
    export WLS_PW=certifikat
    # Set Production Mode. When set to true, the server starts up in production mode.
    When set to false, the server starts up i
    n development mode. The default is false.
    export STARTMODE=false
    export WEBLOGIC_OPTIONS='-Dweblogic.Domain=Certifikat'
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.Name=PostDanmarkServer"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.discover=false"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dbea.home=/opt/bea/weblogic/6.1"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.home=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.dir=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.password=$WLS_PW"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.ProductionModeEnabled=$STARTMODE"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.security.policy=$WEBLOGIC_HOME/lib/weblogic.policy"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.RootDirectory=/opt/projects/$PROJECT/$ENVIRONMENT/weblogic"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.util.logging.config.file=/opt/projects/$PROJECT/$ENVIRONMENT/batch/proper
    ties/logging.properties"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.library.path=$WEBLOGIC_HOME/lib/solaris:$WEBLOGIC_HOME/lib/solaris/oci816
    _8"
    export JAVA_OPTIONS='-hotspot -ms64m -mx64m -classpath '
    export JAVA_OPTIONS=${JAVA_OPTIONS}$CLASSPATH
    echo on
    echo "using JAVA OPTIONS : "$JAVA_OPTIONS"
    echo "using WEBLOGIC OPTIONS : "$WEBLOGIC_OPTIONS"
    "$JAVA_HOME/bin/java" $JAVA_OPTIONS $WEBLOGIC_OPTIONS weblogic.Server

    Hi.
    Try placing the wl_management_internal2.war file from the mydomain/.wlstaging directory into the directory your server is expecting.
    Regards,
    Michael
    Peter Buus wrote:
    Hi
    I have developed an appliaction using wls 6.1 sp2 on w2k, which I want to migrate
    to Solaris 8.
    I have modified my windows statup scripts to Solaris, but I get a strange error
    when starting weblogic. I am starting the server as root and my weblogic.policy
    file is modified according to my installation.
    Has anybody encountered anything similar?
    <Feb 20, 2002 12:08:09 PM CET> <Critical> <Management> <Unable to deploy an internal
    management web application - <all-internal-apps>. Managed servers may be unable
    to start.
    java.io.FileNotFoundException: ./config/Certifikat/.wlstaging/wl_management_internal2.war
    (No such file or directory)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:62)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:132)
    at weblogic.management.mbeans.custom.ApplicationManager.stageGlobalWarFile(ApplicationManager.java:398)
    at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:334)
    at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
    at $Proxy35.start(Unknown Source)
    at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
    at weblogic.management.Admin.finish(Admin.java:561)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
    at weblogic.Server.main(Server.java:35)
    >
    My startup script is as follows
    bash-2.03$ more startWeblogic.sh
    #!/usr/bin/bash
    # Set user-defined variables.
    export PROJECT=postdanmark
    export ENVIRONMENT=test
    export RELEASE_DIR=/opt/projects/$PROJECT/$ENVIRONMENT/lib
    export JAVA_HOME=/opt/jdk/j2sdk1_3_1_02
    export WEBLOGIC_HOME=/opt/bea/weblogic/6.1
    export PATH=$WEBLOGIC_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:.:$PATH
    export CLASSPATH=$RELEASE_DIR/internal/util/1.0/Util.jar
    export CLASSPATH=$CLASSPATH:$WEBLOGIC_HOME/lib/weblogic.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/sun/jaxb/1.0ea/lib/jaxb-rt-1.0-ea.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/postdanmark/1.0/PostDanmarkPC.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/EntrustCAEjb/1.0/EntrustCAEjb.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/websupport/1.0/WebSupport.jar
    export CLASSPATH=$CLASSPATH:/opt/projects/$PROJECT/$ENVIRONMENT/batch/properties
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/corba/interfaces/entrustca/1.2/EntrustCA.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/mysql/jdbc/2.0.4/mm.mysql-2.0.4-bin.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entbase.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entuser.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entp7.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entmisc.jar
    export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entcertlist.jar
    echo off
    echo *********************************************
    echo * Starting weblogic application server *
    echo *********************************************
    # Set WLS_PW equal to your system password for no password prompt server startup.
    export WLS_PW=certifikat
    # Set Production Mode. When set to true, the server starts up in production mode.
    When set to false, the server starts up i
    n development mode. The default is false.
    export STARTMODE=false
    export WEBLOGIC_OPTIONS='-Dweblogic.Domain=Certifikat'
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.Name=PostDanmarkServer"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.discover=false"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dbea.home=/opt/bea/weblogic/6.1"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.home=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.dir=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.password=$WLS_PW"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.ProductionModeEnabled=$STARTMODE"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.security.policy=$WEBLOGIC_HOME/lib/weblogic.policy"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.RootDirectory=/opt/projects/$PROJECT/$ENVIRONMENT/weblogic"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.util.logging.config.file=/opt/projects/$PROJECT/$ENVIRONMENT/batch/proper
    ties/logging.properties"
    export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.library.path=$WEBLOGIC_HOME/lib/solaris:$WEBLOGIC_HOME/lib/solaris/oci816
    _8"
    export JAVA_OPTIONS='-hotspot -ms64m -mx64m -classpath '
    export JAVA_OPTIONS=${JAVA_OPTIONS}$CLASSPATH
    echo on
    echo "using JAVA OPTIONS : "$JAVA_OPTIONS"
    echo "using WEBLOGIC OPTIONS : "$WEBLOGIC_OPTIONS"
    "$JAVA_HOME/bin/java" $JAVA_OPTIONS $WEBLOGIC_OPTIONS weblogic.Server--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Problem starting WLS server  in Oracle VM Viirtualbox

    Hi,
    I am new to Oracle SOASuite.I am trying my hands on with Oracle VM Viirtualbox to which I have imported theoracle soa suite/bpm appliances and I am successful with it.The problem arises when I try to start the WLS server.It failed to start and gave the following exception in logs:
    <Failed to initialize the application 'soademoDatabase' due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:327)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.common.ResourceException: Listener refused the connection with the following error:
    ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
         at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:500)
         at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:177)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1310)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1227)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:250)
         Truncated. see log file for complete stacktrace
    >
    <Jul 2, 2012 4:49:20 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'wlsbjmsrpDataSource' due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
         at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:327)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         Truncated. see log file for complete stacktrace
    Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error:
    ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:283)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1310)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1227)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:250)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1330)
         Truncated. see log file for complete stacktrace
    Please help me debug the issue.
    Edited by: DivyaHabin on Jul 2, 2012 10:04 PM

    Thanks for the reply Eric.
    Initially I didn't start db server before starting Admin server.But now as per your reply, I started db and then started the server.It got started.So does that mean I should start the Oracle Database first and then start server?
    The exception are still there in log.
    Exception1:<Failed to initialize the application 'soademoDatabase' due to error weblogic.application.ModuleException: .
    Exception2: <Failed to initialize the application 'wlsbjmsrpDataSource' due to error weblogic.application.ModuleException: .
    Edited by: DivyaHabin on Jul 3, 2012 1:18 AM

  • Problem starting WLS 5.1 in RH Linux

    I have RH Linux 6.2 and just downloaded Sun JDK1.3 and BEA WLS 5.1. There
    were a couple of problems with the install:
    1) The case statemement in startWebLogic.sh did not pick up Linux using
    uname -s, but I fixed that by commenting out all the other Unixes and the
    case and esac. And LD_LIBRARY_PATH was defined as
    /home/wlogic/weblogic/lib/linux
    2) The second problem I have not been able to resolve. This is the
    stackdump:
    LD_LIBRARY_PATH=/home/wlogic/weblogic/lib/linux
    Exception in thread "main" java.security.AccessControlException: access
    denied (
    java.lang.RuntimePermission createSecurityManager)
    at
    java.security.AccessControlContext.checkPermission(AccessControlContext.java
    :272)
    at
    java.security.AccessController.checkPermission(AccessController.java:399)
    at
    java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
    at java.lang.SecurityManager.<init>(SecurityManager.java:301)
    at
    weblogic.boot.ServerSecurityManager.<init>(ServerSecurityManager.java:11)
    at weblogic.Server.main(Server.java:59)
    at weblogic.Server.main(Server.java:55)
    Comments pls someone. Many thanks.
    Kenny

    Try modifying your weblogic.polic file so that the paths in that file
    match your environment.
    John
    Kenny Kon wrote:
    >
    I have RH Linux 6.2 and just downloaded Sun JDK1.3 and BEA WLS 5.1. There
    were a couple of problems with the install:
    1) The case statemement in startWebLogic.sh did not pick up Linux using
    uname -s, but I fixed that by commenting out all the other Unixes and the
    case and esac. And LD_LIBRARY_PATH was defined as
    /home/wlogic/weblogic/lib/linux
    2) The second problem I have not been able to resolve. This is the
    stackdump:
    LD_LIBRARY_PATH=/home/wlogic/weblogic/lib/linux
    Exception in thread "main" java.security.AccessControlException: access
    denied (
    java.lang.RuntimePermission createSecurityManager)
    at
    java.security.AccessControlContext.checkPermission(AccessControlContext.java
    :272)
    at
    java.security.AccessController.checkPermission(AccessController.java:399)
    at
    java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
    at java.lang.SecurityManager.<init>(SecurityManager.java:301)
    at
    weblogic.boot.ServerSecurityManager.<init>(ServerSecurityManager.java:11)
    at weblogic.Server.main(Server.java:59)
    at weblogic.Server.main(Server.java:55)
    Comments pls someone. Many thanks.
    Kenny--
    Jesus M. Salvo, Jr.
    Senior Consultant
    PowerServe Pty Ltd
    Level 2, 116 Miller Street
    North Sydney 2060
    New South Wales, Australia
    Ph: (61-2) 9492 4800
    Direct (61-2) 9492 4853
    Fax: (61-2) 9492 4899
    http://www.powerserve.com.au
    Email: [email protected]
    This email is from PowerServe Pty Limited (ACN 069 037 056)
    The information contained in this email (including any attached files)
    may be privileged and confidential intended for the use of the
    person/persons named above. If you are not the intended recipient, you
    are advised that any use, distribution or copying of the information is
    strictly prohibited. If you have received this transmission in error,
    please notify PowerServe Pty Limited immediately on (61 3) 9618 1222 or
    reply by email to the sender.
    PowerServe Pty Limited does not represent or warrant that this email or
    any attached files are free from computer viruses or other defects. Any
    attached files are provided, and may only be used, on the basis that the
    user assumes all responsibility for

  • Problems starting WLS 5.1 on Linux

    I am new to WLS, so this may be obvious, but these are the errors I get
    when trying to start WebLogic Server 5.1 after my first attempt to
    install and configure WLS 5.1:
    1st error
    java.lang.UnsatisfiedLinkError: no jsafe in java.library.path
    2nd error
    Sun Oct 15 22:54:27 EDT 2000:<A> <SSLListenThread> ListenThread.run()
    failed:
    java.lang.UnsatisfiedLinkError:
    /usr/local/weblogic/lib/linux/libweblogicunix1.so:
    /usr/local/weblogic/lib/linux/libweblogicunix1.so: undefined symbol:
    makeCString
    I have checked and rechecked classpaths, etc. Here is the configuration
    on this machine:
    RedHat Linux 6.0 (kernel 2.2.5-22)
    glibc upgraded to 2.1.3-21
    Sun JDK 1.3.0
    (I've seen other posts on this newsgroup that say WLS will run with RH
    6.0 and others that say it'll work with JDK 1.3.0.)
    I would appreciate any hints. Thanks in advance for advice on this
    newbie question.
    Pete Pierce

    The first error usually happens with WLS 5.1 wihout any service packs.
    Apply the latest and it'll go away, and possibly the second one as well.
    "Peter J. Pierce" wrote:
    >
    I am new to WLS, so this may be obvious, but these are the errors I get
    when trying to start WebLogic Server 5.1 after my first attempt to
    install and configure WLS 5.1:
    1st error
    java.lang.UnsatisfiedLinkError: no jsafe in java.library.path
    2nd error
    Sun Oct 15 22:54:27 EDT 2000:<A> <SSLListenThread> ListenThread.run()
    failed:
    java.lang.UnsatisfiedLinkError:
    /usr/local/weblogic/lib/linux/libweblogicunix1.so:
    /usr/local/weblogic/lib/linux/libweblogicunix1.so: undefined symbol:
    makeCString
    I have checked and rechecked classpaths, etc. Here is the configuration
    on this machine:
    RedHat Linux 6.0 (kernel 2.2.5-22)
    glibc upgraded to 2.1.3-21
    Sun JDK 1.3.0
    (I've seen other posts on this newsgroup that say WLS will run with RH
    6.0 and others that say it'll work with JDK 1.3.0.)
    I would appreciate any hints. Thanks in advance for advice on this
    newbie question.
    Pete Pierce--
    Jesus M. Salvo, Jr.
    Senior Consultant
    PowerServe Pty Ltd
    Level 2, 116 Miller Street
    North Sydney 2060
    New South Wales, Australia
    Ph: (61-2) 9492 4800
    Direct (61-2) 9492 4853
    Fax: (61-2) 9492 4899
    http://www.powerserve.com.au
    Email: [email protected]
    This email is from PowerServe Pty Limited (ACN 069 037 056)
    The information contained in this email (including any attached files)
    may be privileged and confidential intended for the use of the
    person/persons named above. If you are not the intended recipient, you
    are advised that any use, distribution or copying of the information is
    strictly prohibited. If you have received this transmission in error,
    please notify PowerServe Pty Limited immediately on (61 3) 9618 1222 or
    reply by email to the sender.
    PowerServe Pty Limited does not represent or warrant that this email or
    any attached files are free from computer viruses or other defects. Any
    attached files are provided, and may only be used, on the basis that the
    user assumes all responsibility for

  • Problem with start WLS

    Peace!
    I'm developing servlets that invoke ejb object under WLE.
    I include in classpath for starting WLS 4 jar in udataobj of WLE.
    When I try to start server there are problem and it doesn't start.
    What do I include to run a client of EJB?
    PS: I think that there are conflict problem between WLE classes and WLS
    classes.
    Thanks.

    Giuseppe -
    Are you using WLE 5.1? If no, I'd recommend you upgrade.
    WLE 5.1 includes examples of how to access EJBs on the T-Engine from the
    J-Engine, or WLS, and addresses some issues you may be encountering.
    Will
    Giuseppe Villanova wrote:
    Peace!
    I'm developing servlets that invoke ejb object under WLE.
    I include in classpath for starting WLS 4 jar in udataobj of WLE.
    When I try to start server there are problem and it doesn't start.
    What do I include to run a client of EJB?
    PS: I think that there are conflict problem between WLE classes and WLS
    classes.
    Thanks.

  • Problems starting AdminServer WLS 10 on linux

    Hello All,
    We have upgraded our environment to platform 10.2 and we have now problems starting the AdminServer on that environment after upgrading the database (oracle 10g).
    Errors indicate that the boot.properties -file is not correct. I've tried to remove the one from AdminServer security -directory and deleted the ldap -directory, but these doesn't help.
    What should I do and in which order to make the server start again ?

    I recommend a support case. You have not provided enough detail here and they are best equipped to handle these types of issues.

  • Database Connection problem in WLS 7.0 Service Pack 7

    Hi Guys,
    I am a newbie in this forum. Currently, I tested running application using WLS 7.0 Service Pack 7 in Development environment. And for database I used Oracle 9i Release 2 v9.2.0.6 which is running on AIX OS. After WLS started, I had some error in connecting to database. This is the error that I found from log file :
    java.sql.SQLException: Bigger type length than Maximum
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:161)
    at oracle.jdbc.driver.DatabaseError.check_error(DatabaseError.java:884)
    at oracle.jdbc.driver.T4CMAREngine.buffer2Value(T4CMAREngine.java:2230)
    at oracle.jdbc.driver.T4CMAREngine.unmarshalUB2(T4CMAREngine.java:1047)
    at oracle.jdbc.driver.T4CTTIdcb.receiveCommon(T4CTTIdcb.java:111)
    at oracle.jdbc.driver.T4CTTIdcb.receiveFromRefCursor(T4CTTIdcb.java:103)
    at oracle.jdbc.driver.T4CResultSetAccessor.unmarshalOneRow(T4CResultSetAccessor.java:165)
    at oracle.jdbc.driver.T4CTTIrxd.unmarshal(T4CTTIrxd.java:787)
    at oracle.jdbc.driver.T4CTTIrxd.unmarshal(T4CTTIrxd.java:704)
    at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:526)
    at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:179)
    at oracle.jdbc.driver.T4CCallableStatement.execute_for_rows(T4CCallableStatement.java:782)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1027)
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2887)
    at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:2978)
    at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4102)
    at weblogic.jdbc.pool.Statement.execute(Statement.java:298)
    at EJB.Engine.EAIManagerBean.mtdRequest(EAIManagerBean.java:204)
    at EJB.Engine.EAIManagerBean_lt8oqo_EOImpl.mtdRequest(EAIManagerBean_lt8oqo_EOImpl.java:46)
    So, I need someone to solve my problem. Thanks...

    First thing, most of BEA's forums are terrible as people rarely reply. I noticed your post through google searching for the same fix. You have likely done the same things as me and have learned that your Oracle JDBC Client driver has some bugs interacting with certain version of Oracle Server. For us, this problem occured when we migrated from Solaris to AIX. We were able to fix this by downloading the latest version of ojdbc14.zip from oracle's site. You can either replace the current ojdbc14 file in the bea installation or make sure it is visible in the classpath for WLS before the old version.
    Here is a good link which describes the problem, good luck.
    http://www.dbtalk.net/comp-databases-oracle-server/java-sql-sqlexception-bigger-type-289015.html

  • Problems starting Server on OSB 11g

    Hi Everybody,
    I have a problem, I just installed the Service Bus 11g on Red Hat and I have problems when I start the server.
    I particular first I start the Admin_Server without any exception and then I start the Server but I get this excedption:
    PATH=/app/olg/wlserver-10.3/wlserver_10.3/server/bin:/app/olg/wlserver-10.3/modules/org.apache.ant_1.7.1/bin:/app/jrmc-3.1.2-1.6.0//jre/bin:/app/jrmc-3.1.2-1.6.0//bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/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_14"
    Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
    BEA JRockit(R) (build R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32, compiled mode)
    Starting WLS with line:
    /app/jrmc-3.1.2-1.6.0//bin/java -jrockit -Xms256m -Xmx512m -Xmanagement -Dcom.sun.management.jmxremote -Djava.rmi.server.hostname=10.31.57.61 -Dcom.sun.management.jmxremote.port=17001 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder -Djava.awt.headless=true -Dweblogic.Name=Server_1 -Djava.security.policy=/app/olg/wlserver-10.3/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/app/olg/wlserver-10.3/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/app/olg/wlserver-10.3/wlserver_10.3 -Dwls.home=/app/olg/wlserver-10.3/wlserver_10.3/server -Dweblogic.home=/app/olg/wlserver-10.3/wlserver_10.3/server -Ddomain.home=/app/olg/bea-olgfwdomain/olgfwdomain -Dcommon.components.home=/app/olg/wlserver-10.3/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=/app/olg/wlserver-10.3/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.domain.config.dir=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig -Doracle.server.config.dir=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/servers/Server_1 -Doracle.security.jps.config=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/carml -Digf.arisidstack.home=/app/olg/bea-olgfwdomain/olgfwdomain/config/fmwconfig/arisidprovider -Dweblogic.alternateTypesDirectory=/app/olg/wlserver-10.3/oracle_common/modules/oracle.ossoiap_11.1.1,/app/olg/wlserver-10.3/oracle_common/modules/oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=false -Dweblogic.management.server=t3://10.31.57.61:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/olg/wlserver-10.3/patch_wls1033/profiles/default/sysext_manifest_classpath:/app/olg/wlserver-10.3/patch_ocp353/profiles/default/sysext_manifest_classpath weblogic.Server
    [JRockit] Management server started on port 17001, ssl=false, authenticate=false.
    <Dec 1, 2010 1:00:03 PM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>
    <Dec 1, 2010 1:00:05 PM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
    <Dec 1, 2010 1:00:07 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Dec 1, 2010 1:00:07 PM CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Dec 1, 2010 1:00:07 PM CET> <Notice> <Log Management> <BEA-170019> <The server log file /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/logs/Server_1.log is opened. All server side log events will be written to this file.>
    <Dec 1, 2010 1:00:12 PM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Dec 1, 2010 1:00:14 PM CET> <Warning> <Store> <BEA-280101> <The persistent file store "_WLS_Server_1" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
    <Dec 1, 2010 1:00:16 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Dec 1, 2010 1:00:16 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Dec 1, 2010 1:00:23 PM CET> <Warning> <Store> <BEA-280101> <The persistent file store "Reporting-FileStore_Server_1" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
    <Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'ALSB Domain Singleton Marker Application' is not targeted>
    <Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'ALSB Domain Singleton Marker Application' is not targeted>
    <Dec 1, 2010 1:00:28 PM CET> <Warning> <AppUtils> <BEA-000000> <Application 'Message Reporting Purger' is not targeted>
    <Dec 1, 2010 1:00:29 PM CET> <Alert> <OSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security realm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service account support.>
    <Dec 1, 2010 1:00:30 PM CET> <Warning> <OSB Kernel> <BEA-398316> <Error getting the Result Cache /osb/service/ResultCache because the OSB Coherence Cache Provider has not been initialized.
    Additional error messages at server startup should point to the root cause for this error.>
    <Dec 1, 2010 1:00:30 PM CET> <Warning> <OSB Kernel> <BEA-398315> <Service Result Caching functionality is disabled because the result cache is unavailable.
    Additional error messages at server startup should point to the root cause for this. If you require Service Result Caching functionality, please fix the errors and restart the server.>
    <Dec 1, 2010 1:00:31 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: ftptransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Ftp Transport Provider/elek28]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:31 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: emailtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Email Transport Provider/tbi712]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: filetransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/File Transport Provider/qwi4ym]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: ejbtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/EJB Transport Provider/kyabv]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: tuxedotransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/Tuxedo Transport Provider/9oa5mj/APP-INF/lib/tuxedo_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: aldsp_transport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALDSP Transport Provider/i3u01o/APP-INF/lib/aldsp_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: sftptransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/SFTP Transport Provider/d4v5rl]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: wstransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/WS Transport Provider/wuaaoy]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: flow-transport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/FLOW Transport Provider/kgaw7k]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:32 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: bpel10gtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/BPEL 10g Transport Provider/7iyhcx]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: jcatransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m], [Extension-Name: wsif, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m], [Extension-Name: JCAFrameworkImpl, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JCA Transport Provider/q9xf1m]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:33 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'JCA Transport Provider' due to error java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType.
    java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType
    at com.bea.wli.sb.transports.jca.JCATransportProvider.loadAdapterList(JCATransportProvider.java:960)
    at com.bea.wli.sb.transports.jca.JCATransportProvider.getInstance(JCATransportProvider.java:80)
    at com.bea.wli.sb.transports.jca.JCATransportAppListener.preStart(JCATransportAppListener.java:16)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.NoClassDefFoundError: oracle/tip/adapter/sa/api/JCABindingInterface$AdapterType
    at com.bea.wli.sb.transports.jca.JCATransportProvider.loadAdapterList(JCATransportProvider.java:960)
    at com.bea.wli.sb.transports.jca.JCATransportProvider.getInstance(JCATransportProvider.java:80)
    at com.bea.wli.sb.transports.jca.JCATransportAppListener.preStart(JCATransportAppListener.java:16)
    at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: jejbtransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JEJB Transport Provider/xyxmad], [Extension-Name: jejbtransport-jar, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/JEJB Transport Provider/xyxmad]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:33 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'JEJB Transport Provider' due to error weblogic.management.DeploymentException: .
    weblogic.management.DeploymentException:
    at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
    at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
    Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: com.bea.wli.sb.transports.jejb.JEJBTransportAppListener
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:140)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:33 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: soatransport-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/SOA-DIRECT Transport Provider/16k7ar/APP-INF/lib/soa_transport.jar]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2], [Extension-Name: xbusrouting-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Routing/lhkfe2]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Routing' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c], [Extension-Name: xbustransform-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Transform/5h7v5c]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Transform' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: stage-utils, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3], [Extension-Name: sbconsole-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3], [Extension-Name: xbuslogging-l10n, referenced from: /app/olg/bea-olgfwdomain/olgfwdomain/servers/Server_1/tmp/_WL_user/ALSB Logging/48dcw3]. Make sure the referenced optional package has been deployed as a library.>
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Logging' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: com.bea.wlp.lwpf.console.app, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'ALSB Test Framework' due to error weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: testfwk-l10n, exact-match: false]..
    weblogic.management.DeploymentException: [J2EE:160149]Error while processing library references. Unresolved application library references, defined in weblogic-application.xml: [Extension-Name: testfwk-l10n, exact-match: false].
    at weblogic.application.internal.flow.CheckLibraryReferenceFlow.prepare(CheckLibraryReferenceFlow.java:26)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    Truncated. see log file for complete stacktrace
    >
    <Dec 1, 2010 1:00:36 PM CET> <Emergency> <Deployer> <BEA-149259> <Server 'Server_1' in cluster 'Cluster-1' is being brought up in administration state due to failed deployments.>
    Dec 1, 2010 1:00:37 PM oracle.dms.app.ServerInitializer oracle.dms.app.ServerInitializer
    INFO: DMS startup class is not started. DMS runs with reduced functionality.
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Ftp Transport Provider, EJBComponent: ftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.ftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.ftp, the provider URL is null>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Email Transport Provider, EJBComponent: emailtransport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.email. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.email, the provider URL is null>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: File Transport Provider, EJBComponent: filepoll.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.file. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.file, the provider URL is null>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: SFTP Transport Provider, EJBComponent: sftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.sftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Dec 1, 2010 1:00:40 PM CET> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
    Can not get destination information. The destination JNDI name is wlsb.internal.transport.task.queue.sftp, the provider URL is null>
    <Dec 1, 2010 1:00:41 PM CET> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Dec 1, 2010 1:00:41 PM CET> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    <Dec 1, 2010 1:00:41 PM CET> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster-1.>
    I tried to find something on internet but nothing suitable for me.
    Thanks

    From the error messages it does not seem to find any of the transport related jars (ftp, jca, email, etc..). Looks like there was an issue while creating the domain.
    Can you retry creating the domain and let us know if you are still getting the same error?
    Regards,
    Patrick

  • How to start WLS in RedHat 6.2

    Hi everyone,
    Everytime when I try to start WLS in RedHat with the command -
    ./startWebLogic.sh in command line console,
    an error - "Don't know how to set the shared library for Linux" is displyed.
    Could anyone help me solve this problem at your earliest convenience sine
    it is quite urgent to me to solve this problem?
    Thanks in advance

    Open startWebLogic.sh
    look for label LINUX)
    substitute the line with
    LINUX | Linux)
    and try again.
    Marco.
    Rex Law <[email protected]> wrote in message
    news:[email protected]..
    Hi everyone,
    Everytime when I try to start WLS in RedHat with the command -
    ./startWebLogic.sh in command line console,
    an error - "Don't know how to set the shared library for Linux" isdisplyed.
    >
    Could anyone help me solve this problem at your earliest conveniencesine
    it is quite urgent to me to solve this problem?
    Thanks in advance

  • Problem Starting Managed Servers

    Hi,
    I am trying to start Managed Server on Sun Solaris. My admin Server and managed Server
    are on the same Machine.
    My admin Server starts up with out any problem. WhenI try to bring up my Managed
    Server its not reading the command line arguments which I supplied through the Console:
    Servers -> serverName -> Remote Start->Arguments. For some reason these command arguments
    are not read and so I am having errors like Unable to load libraries, etc.
    Also when I saw the log file for managed server the class path and the arguments
    are printed in a different way than I have set. I dont know if thats a problem or
    not. I am copying part of that for your reference.
    classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblogic6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
    serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.security.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
    I have checked the config.xml file and what ever I have set in the console is being
    saved properly in the xml file.
    Can any one know why the back slash is printed above even though I havent typed that
    in the console. Has any one have experince with setting the command line arguments
    and class path through console for Managed servers.
    I am stuck up at this point. Any help in this regard will be greatly appreciated.
    Thanks,
    Kiran

    Seems a method signature does not match with the implementation in the
    library either due to namemangling or incompatible versions of libraries.
    You are loading your own custom native libraries for security.
    Best would be use the default startManagedServer -- once the server has
    started, copy and paste the entire value of java.library.path into the
    startup arguments for Remote start.
    For instance in my server log file:
    ####<Apr 10, 2002 6:47:10 PM PDT> <Info> <Management> <mountview> <myserver>
    <main> <system> <> <141034> <Java system property: java.library.path =
    /home/sabha/600sp2only/jdk130/jre/bin/../lib/sparc/hotspot:/home/sabha/600sp
    2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlserver6.0/lib/so
    laris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/usr/lib>
    I would set that as the arguments :
    -Djava.library.path=/home/sabha/600sp2only/jdk130/jre/lib/sparc/hotspot:/hom
    e/sabha/600sp2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlser
    ver6.0/lib/solaris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/
    usr/lib
    If this does not work, then java for some reason is not taking library paths
    set as java.library.path and I dont know how to set LD_LIBRARY_PATH as part
    of arguments to java. Another thing is before starting the NodeManager, set
    the LD_LIBRARY_PATH to point the library directories and see if this helps.
    regards,
    Sabha
    "Kiran" <[email protected]> wrote in message
    news:[email protected]...
    >
    Sabha,
    I am trying to start the managed server via remote start. After readingyour reply
    I have cleaned up the argument list for remote start. Now I am gettingaltogether
    a different error.(Surpsisingly I was able to start the managed serversusing srartManagedServer.sh.
    I dont know why I am having trouble to do the same through the remotestart).
    >
    I am getting a unsatisfied link error. In your reply you have asked me toadd -Djava.library.path
    to the argument liist which I did. Below you can find the exact error Ihave got:
    >
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.UnsatisfiedLinkError:/export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:
    ld.so.1: /usr/bin/../java/bin/../bin/sparc/native_threads/java: fatal:relocation
    error: file /export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:symbol Opsys_oneWayCryptCmpApi:
    referenced symbol not found
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1382)
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1306)
    at java.lang.Runtime.loadLibrary0(Runtime.java:749)
    at java.lang.System.loadLibrary(System.java:820)
    atamdocs.APILink.accesscontrol.sum.EncryptApi.<clinit>(EncryptApi.java:20)
    atamdocs.APILink.accesscontrol.sum.UserJoltBackend.<clinit>(UserJoltBackend.ja
    va:52)
    >
    atamdocs.APILink.accesscontrol.sum.SumManagerImpl.<init>(SumManagerImpl.java:5
    9)
    >
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    atamdocs.uamsimpl.server.storage.multi.MultiManagerImpl.<init>(MultiManagerImp
    l.java:208)
    >
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    atamdocs.uamsimpl.server.storage.cache.CachingManagerImpl.<init>(CachingManage
    rImpl.java:81)
    >
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    at amdocs.uams.UamsSystem.getUamsManager(UamsSystem.java:156)
    atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:61)
    atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:55)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    at amdocs.uamsimpl.server.ejb.wl6.WLUamsRealm.<init>(WLUamsRealm.java:42)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    at weblogic.security.acl.Realm.getRealm(Realm.java:84)
    at weblogic.security.acl.Realm.getRealm(Realm.java:62)
    atweblogic.security.SecurityService.initializeRealm(SecurityService.java:258)
    at weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:402)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    >
    >
    Please let me know if you need more description.
    Thanks,
    Kiran
    "Sabha" <[email protected]> wrote:
    Either you are attempting to start a managed server through its
    NodeManager
    for which the remote startup arguments are not correct or something else
    is
    wrong. How are you starting the server? The remote start is only when you
    want to start the server through NodeManager and not for normalinvocation
    of the startManagedServer script.
    Does the server really start? can you paste the startup arguments for the
    remote start of the managed server as saved in the config.xml.
    What is the log generated when the managed server is startedup.
    -Sabha
    "Kiran" <[email protected]> wrote in message
    news:[email protected]...
    Sabha,
    The main problem is:
    What ever I am trying to give in the command line arguments through theConsole:
    Servers -> serverName -> Remote Start->Arguments.
    is not being read during managed server start up.
    I have all the libraries defined defined in java.lib.path. I dont knowwhy
    its not
    being read by managed server during start up. Am I missing something.
    -Kiran
    "Sabha" <[email protected]> wrote:
    If its unable to load the performance packs, try setting
    java.library.path
    to the solaris lib directories. /usr/lib, /home/oracle/lib paths -- oryou
    can just copy what is in the admin weblogic.log file for the
    java.library.path (make sure the paths are correct and applicable forthe
    maanged server box also) and pass that as an argument as
    in -Djava.library.path=/usr/lib:/bea/wlserver6.1/lib/solaris...
    -Sabha
    "Kiran" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I am trying to start Managed Server on Sun Solaris. My admin Server
    and
    managed Server
    are on the same Machine.
    My admin Server starts up with out any problem. WhenI try to bring
    up
    my
    Managed
    Server its not reading the command line arguments which I supplied
    through
    the Console:
    Servers -> serverName -> Remote Start->Arguments. For some reason
    these
    command arguments
    are not read and so I am having errors like Unable to load
    libraries,
    etc.
    Also when I saw the log file for managed server the class path and
    the
    arguments
    are printed in a different way than I have set. I dont know if thats
    a
    problem or
    not. I am copying part of that for your reference.
    classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblog
    i
    c
    6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
    serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.secur
    i
    t
    y.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
    I have checked the config.xml file and what ever I have set in the
    console
    is being
    saved properly in the xml file.
    Can any one know why the back slash is printed above even though I
    havent
    typed that
    in the console. Has any one have experince with setting the command
    line
    arguments
    and class path through console for Managed servers.
    I am stuck up at this point. Any help in this regard will be greatlyappreciated.
    Thanks,
    Kiran

  • Problem starting OSB

    Ok, that's weird....I had trace and a question here.
    At any rate, I'm having trouble starting up OSB from a newly created domain. This is the output with so many errors I'm not even sure where to look. Any ideas?
    [tkiesii@bur65017fwks bin]$ ./startWebLogic.sh
    JAVA Memory arguments: -Xms512m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -XX:MaxPermSize=160m
    WLS Start Mode=Development
    CLASSPATH=:/home/tkiesii/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/tkiesii/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/tkiesii/bea/patch_cie670/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/tkiesii/bea/patch_alsb1031/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/tkiesii/bea/jdk160_05/lib/tools.jar:/scratch/tkiesii/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/scratch/tkiesii/bea/wlserver_10.3/server/lib/weblogic.jar:/home/tkiesii/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/scratch/tkiesii/bea/wlserver_10.3/server/lib/webservices.jar:/home/tkiesii/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/home/tkiesii/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/scratch/tkiesii/bea/wlserver_10.3/../modules/features/osb.server.modules_10.3.1.0.jar:/scratch/tkiesii/bea/osb_10.3/lib/flow/sb-flow.jar:/scratch/tkiesii/bea/wlserver_10.3/../modules/com.bea.core.jaxen_1.0.1.0_1-1-1.jar:/scratch/tkiesii/bea/osb_10.3/lib/version.jar:/scratch/tkiesii/bea/osb_10.3/lib/alsb.jar:/scratch/tkiesii/bea/osb_10.3/3rdparty/lib/j2ssh-ant.jar:/scratch/tkiesii/bea/osb_10.3/3rdparty/lib/j2ssh-common.jar:/scratch/tkiesii/bea/osb_10.3/3rdparty/lib/j2ssh-core.jar:/scratch/tkiesii/bea/osb_10.3/3rdparty/lib/j2ssh-dameon.jar:/scratch/tkiesii/bea/osb_10.3/3rdparty/classes:/scratch/tkiesii/bea/wlserver_10.3/../modules/com.bea.core.apache.commons.logging_1.1.0.jar:/scratch/tkiesii/bea/osb_10.3/lib/transports/jca/jca-binding-api.jar:/scratch/tkiesii/bea/osb_10.3/lib/transports/jca/bpm-infra.jar:/scratch/tkiesii/bea/osb_10.3/lib/transports/jca/log4j_1.2.8.jar:/scratch/tkiesii/bea/osb_10.3/lib/transports/jca/xmlparserv2.jar:%WL_HOME/server/ext/jdbc/oracle/orai18n.jar::/scratch/tkiesii/bea/wlserver_10.3/common/eval/pointbase/lib/pbembedded57.jar:/scratch/tkiesii/bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/scratch/tkiesii/bea/wlserver_10.3/server/lib/xqrl.jar::
    PATH=/scratch/tkiesii/bea/wlserver_10.3/server/bin:/home/tkiesii/bea/modules/org.apache.ant_1.6.5/bin:/home/tkiesii/bea/jdk160_05/jre/bin:/home/tkiesii/bea/jdk160_05/bin:/usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/local/packages/idb_remote/9.1.039/bin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/usr/local/ade/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:
    Listening for transport dt_socket at address: 8453
    java version "1.6.0_05"
    Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
    Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
    Starting WLS with line:
    /home/tkiesii/bea/jdk160_05/bin/java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -XX:MaxPermSize=160m -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/scratch/tkiesii/bea/wlserver_10.3 -Dwls.home=/scratch/tkiesii/bea/wlserver_10.3/server -Dweblogic.home=/scratch/tkiesii/bea/wlserver_10.3/server -Dweblogic.management.discover=true -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/home/tkiesii/bea/patch_wlw1030/profiles/default/sysext_manifest_classpath:/home/tkiesii/bea/patch_wls1030/profiles/default/sysext_manifest_classpath:/home/tkiesii/bea/patch_cie670/profiles/default/sysext_manifest_classpath:/home/tkiesii/bea/patch_alsb1031/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=/scratch/tkiesii/bea/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
    Listening for transport dt_socket at address: 8453
    <Sep 21, 2009 1:05:32 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
    <Sep 21, 2009 1:05:33 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 380194 Fri Oct 24 13:20:13 IST 2008
    WebLogic Server Temporary Patch for 8408837 Fri Apr 03 17:01:18 EDT 2009
    WebLogic Server Temporary Patch for CR378781, CR380313 Fri Sep 19 13:34:16 PDT 2008
    WebLogic Server Temporary Patch for CR381056 Mon Oct 06 10:48:50 EDT 2008
    WebLogic Server Temporary Patch for CR374413, CR378680 Tue Sep 02 09:55:36 PDT 2008
    WebLogic Server Temporary Patch for CR378102 Wed Sep 10 23:28:48 PDT 2008
    WebLogic Server Temporary Patch for CR378741 Tue Sep 09 13:08:51 PDT 2008
    WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
    <Sep 21, 2009 1:05:35 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Sep 21, 2009 1:05:35 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Sep 21, 2009 1:05:36 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /scratch/tkiesii/bea/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
    <Sep 21, 2009 1:05:42 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Sep 21, 2009 1:05:47 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Sep 21, 2009 1:05:47 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Sep 21, 2009 1:05:47 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:48 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:49 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:50 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:51 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:52 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'cgDataSource' due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
    at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:289)
    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
    weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
    at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
    Truncated. see log file for complete stacktrace
    >
    <Sep 21, 2009 1:05:52 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:53 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:54 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:55 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:56 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:57 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'cgDataSource-nonXA' due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
    at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:289)
    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
    weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
    at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
    Truncated. see log file for complete stacktrace
    >
    <Sep 21, 2009 1:05:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "wlsbjmsrpDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "wlsbjmsrpDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:05:59 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "wlsbjmsrpDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:06:00 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "wlsbjmsrpDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:06:01 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "wlsbjmsrpDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    <Sep 21, 2009 1:06:02 PM EDT> <Critical> <JTA> <BEA-110482> <A logging last resource failed during initialization. The server cannot boot unless all configured logging last resources (LLRs) initialize. Failing reason:
    weblogic.common.ResourceException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    weblogic.common.ResourceException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1197)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
    at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
    at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:146)
    Truncated. see log file for complete stacktrace
    weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
    at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
    Truncated. see log file for complete stacktrace
    >
    <Sep 21, 2009 1:06:02 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'wlsbjmsrpDataSource' due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
    at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:289)
    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
    weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:253)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1033)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:214)
    at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1051)
    Truncated. see log file for complete stacktrace
    >
    <Sep 21, 2009 1:06:10 PM EDT> <Alert> <OSB Security> <BEA-387068> <There is no PKI credential mapper provider configured in your security realm. Service key provider management will be disabled. Configure a PKI credential mapper provider if you need service provider support. This is typically the case if you have Oracle Service Bus proxy services with web service security enabled or outbound 2-way SSL connections.>
    <Sep 21, 2009 1:06:19 PM EDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'ReportingMDB', class com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Sep 21, 2009 1:06:19 PM EDT> <Warning> <EJB> <BEA-010001> <While deploying EJB 'PurgingMDB', class com.bea.wli.reporting.jmsprovider.runtime.PurgingMDB was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.>
    <Sep 21, 2009 1:06:23 PM EDT> <Warning> <WliSbTransports> <BEA-381917> <MQ Transport could not be registered due to : Missing MQ Library>
    Oracle Service Bus Debugger listening on port 7453.
    <Sep 21, 2009 1:06:32 PM EDT> <Error> <OSB-Reporting> <BEA-473500> <JMS Reporting Data Manager failed to deploy during server start up javax.naming.NameNotFoundException: Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
    javax.naming.NameNotFoundException: Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    Truncated. see log file for complete stacktrace
    >
    <Sep 21, 2009 1:06:32 PM EDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'JMS Reporting Provider'.
    javax.naming.NameNotFoundException: Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    Truncated. see log file for complete stacktrace
    javax.naming.NameNotFoundException: Unable to resolve 'wlsbjmsrpDataSource'. Resolved ''; remaining name 'wlsbjmsrpDataSource'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    Truncated. see log file for complete stacktrace
    >
    <Sep 21, 2009 1:06:38 PM EDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Sep 21, 2009 1:06:39 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [JTAExceptions:119002]A logging last resource failed during initialization. The server cannot boot unless all configured logging last resources (LLRs) initialize. Failing reason:
    weblogic.common.ResourceException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
    >
    <Sep 21, 2009 1:06:39 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Sep 21, 2009 1:06:39 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Sep 21, 2009 1:06:39 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <Sep 21, 2009 1:06:39 PM EDT> <Error> <netuix> <BEA-423443> <Exception while initializing SingleFileServlet: [java.lang.reflect.InvocationTargetException].
    java.lang.reflect.InvocationTargetException
    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 com.bea.netuix.servlets.manager.SingleFileServlet.reinitInternal(SingleFileServlet.java:178)
    Truncated. see log file for complete stacktrace
    java.lang.IllegalStateException: Unable to extract name from ServletContext.
    at com.bea.p13n.management.ApplicationHelper.getWebAppName(ApplicationHelper.java:300)
    at com.bea.netuix.servlets.services.WlsLightCommonWebappServices._getWebAppName(WlsLightCommonWebappServices.java:163)
    at com.bea.netuix.servlets.services.WlsLightCommonWebappServices.getWebAppName(WlsLightCommonWebappServices.java:63)
    at com.bea.portlet.container.AppContainer.<init>(AppContainer.java:141)
    at com.bea.portlet.container.AppContainer.getAppContainer(AppContainer.java:112)
    Truncated. see log file for complete stacktrace
    >
    Mon Sep 21 13:06:40 EDT 2009 <INFO> Instantiating inbound part of Adapter Framework instance: OraSB
    Mon Sep 21 13:06:40 EDT 2009 <INFO> Stopping inbound part of Adapter Framework instance: OraSB
    Stopping PointBase server...
    PointBase server stopped.
    Edited by: [email protected] on Sep 21, 2009 10:34 AM added the meaty stuff
    Edited by: [email protected] on Sep 21, 2009 10:36 AM

    I wound up killing all of the java processes as a last ditch effort to see if there was a collision from another user (three use the machine). The domain came up successfully after doing that. I'll need to sort out at some point what the problem was exactly, but for now it seems resolved.

Maybe you are looking for