Losing Session for Weblogic 7.0.2 in Cluster env

          PROBLEM: We are losing our session when running in our app in a clustered environment.
          The user can use the app for a while, but then weird stuff starts happening. In
          some cases, the login check that we do at the begining of each request fails,
          because it tries to check for a login token in the session, and the session has
          been wiped out. The user gets forwarded to the login page.
          Our configuration is: WLS 7.0.2 (OS = Windows 2000) Admin Server and a managed
          server A at APP1 (physical machine), another managed server B at APP2 (physical
          machine), A and B is in one cluster. We had 6 Apache Servers 2.0.45 (OS = Linux)
          and each works together with Weblogic Plugin. The weblogic plugin has the following
          configuration: <Location /sample> SetHandler weblogic-handler WeblogicCluster
          10.1.1.11:7010,10.1.1.12:7010 Idempotent ON CookieName JSESSIONID </Location>
          The server A and B use round-robin loadblancing, and we have a hardware loadblancer
          infront of Apache to do loadblancing for our 6 web servers.
          In weblogic.xml we config our application to use replicated for session failover.
          Losing session is randomly happened.
          Anyone of you have any idea?
          Thanks in advance.
          Harry
          

The advice on version numbers given above is quite generic. While JDK 1.4 may work, if you want to run a supported configuration the answer to this question depends on what OS you're running. Further, BEA supports different JDK versions for running the server and for client applications. Here is the whole chart:
http://e-docs.bea.com/platform/suppconfigs/configs70/70_over/overview.html
Be sure to click on your operating system to get the specific information about what JDK is "fully-supported" and what is "client-only".
Hope that helps,
Justin

Similar Messages

  • Weblogic Integration failed to build Cluster ENV

    Dear buddies,
    I have used WL for months, WLS works pretty good with cluster support. but I failed to create WLI cluster.could you guys give me a hand and tell me how to create an WLI cluster?Thanks a lot!!!
    Here is the process how I created WLI cluster:
    ENV:RedHat9+ WL8.1_SP4
    Machine: 172.16.4.238(adminServer), 172.16.4.237/236(236/237 are in the same physical machine, one Network interface card listen to two ip address)
    BEA_HOME=/opt/bea/
    1.executed /opt/bea/weblogic81/common/bin/config.sh on 172.16.4.238 and create an admin server(cgServer,172.16.4.238:7001) and a cluster(TestCluster) inclued two managedServers(mServer1/172.16.4.236:7001,mServer2/172.16.4.237:7001)
    and I didn't create extra JDBC POOL except the standard one.
    2. I exectued same command on 172.16.4.236,create an admin Server(mServer1) and a cluster(TestCluster)with mServer2 included. and the other settings are just same as step1.
    Now I am having following problem.
    1.admin Server(cgServer) can startup without any problem
    2.mServers (mServer1 and mServer2)can't start up(detail output pasted later) it seems pointbase didn't start up correctly on port 9093
    3.so I start up point base on mServers machine with command "/opt/bea/weblogic81/common/eval/pointbase/tools/startPointBase.sh"
    but seems the pointbase only listen 9092!!
    4.I can't even startup adminserver and pointbase DB with Jrockit, but Sun's JVM seems works.
    below are detailed output when I startManagedServers:
    command:
    [root@localhost integration]# ./startManagedWebLogic.sh mServer1 http://172.16.4.238:7001
    ####<Dec 27, 2005 2:12:05 PM EST> <Notice> <Log Management> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-170019> <The server log file /opt/bea/user_projects/domains/integration/mServer1/mServer1.log is opened. All server side log events will be written to this file.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000415> <System has file descriptor limits of - soft: 1,024, hard: 1,024>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000416> <Using effective file descriptor limit of: 1,024 open sockets/files.>
    ####<Dec 27, 2005 2:12:05 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000406> <PosixSocketMuxer was built on May 22 2003 15:43:24>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000436> <Allocating 3 reader threads.>
    ####<Dec 27, 2005 2:12:06 PM EST> <Info> <Socket> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000440> <NativeIO Enabled>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server mServer1 for security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <Security> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Notice> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000328> <Starting WebLogic Managed Server "mServer1" for domain "integration">
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "mServer1" version:
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic Integration 8.1 SP4 Tue Nov 30 10:34:16 PST 2004 471877 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <WebLogicServer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000215> <Loaded License : /opt/bea/license.bea>
    ####<Dec 27, 2005 2:12:14 PM EST> <Info> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "mServer1"
    Listen Address          172.16.4.236:7001
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Dec 27, 2005 2:12:14 PM EST> <Debug> <RJVM> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "mServer1"
    Channel Weight          50
    Accept Backlog          50
    Login Timeout          5000ms
    Max Message Size     10000000
    Message Timeout     60s
    Idle Timeout          65s
    Tunneling Timeout     40s
    Tunneling Ping          45s>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <XML> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
    ####<Dec 27, 2005 2:12:17 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <Connector> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
    ####<Dec 27, 2005 2:12:18 PM EST> <Info> <IIOP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mServer1.>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101052> <[HTTP mServer1] Initialized>
    ####<Dec 27, 2005 2:12:19 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101135> <mServer1 is the default Web server.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <J2EE> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
    ####<Dec 27, 2005 2:12:21 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
    ####<Dec 27, 2005 2:12:23 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:24 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=20975280,name=uddi,context-path=/uddi)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=23108345,name=uddiexplorer,context-path=/uddiexplorer)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server mServer1.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<anonymous>> <> <BEA-101047> <[ServletContext(id=13608238,name=wl_management_internal1,context-path=/wl_management_internal1)] WebServiceServlet: init>
    ####<Dec 27, 2005 2:12:25 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000138> <Listening for announcements from cluster TestCluster on 237.0.0.1:7001.>
    ####<Dec 27, 2005 2:12:25 PM EST> <Notice> <Cluster> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000133> <Waiting to synchronize with other running members of TestCluster.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JTA> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JMS> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101238> <HTTP log rotation is size based for the Web server: mServer1.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <HTTP> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-101051> <[HTTP mServer1] started>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <WebService> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Deployer> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001177> <Creating Connection Pool named bpmArchPool, URL = jdbc:pointbase:server://localhost:9093/workshop, Properties = {user=weblogic}.>
    ####<Dec 27, 2005 2:12:56 PM EST> <Info> <Common> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-000625> <The application has disabled periodic testing of free resources in pool "bpmArchPool".>
    ####<Dec 27, 2005 2:12:57 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:57 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:58 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:58 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:12:59 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:12:59 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
         at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
         at weblogic.Server.main(Server.java:32)
    >
    ####<Dec 27, 2005 2:13:00 PM EST> <Warning> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001129> <Received exception while creating connection for pool "bpmArchPool": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
    ####<Dec 27, 2005 2:13:00 PM EST> <Info> <JDBC> <localhost.localdomain> <mServer1> <main> <<WLS Kernel>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
         at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
         at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
         at com.pointbase.net.netJDBCDriver.getConnection(Unknown Source)
         at com.pointbase.net.netJDBCDriver.connect(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
         at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
         at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:171)
         at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1018)
         at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:142)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:306)
         at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:180)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:337)
         at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:597)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:575)
         at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
         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:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:754)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:733)
         at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:509)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1560)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1528)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:988)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:946)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7691)
         at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
         at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
         at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)

    Since a couple of days we see the same in our project. Same release. It started when we added versioning to our ~140 processes. A hint would be great. We too didn't find anything helpful on the web.

  • Is there a way to disable concurrent Weblogic Admin Console sessions for the same user?

    A coworker on another workstation and I are able to log into same user account on the Weblogic Admin Console at the same time. I would like to restrict access so only one session per user account can be logged in to the Admin Console. Is this possible?
    Alternatively, is there a way to log identifiable information (IP/workstation) when multiple sessions for one account occur at the same time?
    I am using 10.3.6.0

    Hi,
    You could also check the http access logs for such info. There you could see records for the received requests, with each record starting with the source IP that initiated the request.
    The default location for access logs is ${DOMAIN_HOME}/servers/${SERVER_NAME}/logs. Of course in your case, the ${SERVER_NAME} would be your admin server name (AdminServer if left as default).
    Regards,
    Mohab

  • Possible to create a JAX-WS, session-bean-based webservice for WebLogic 10?

    All,
    sorry - but I'm going a bit crazy here. I have been unable to figure out the secret hand-shakes for developing a session-bean-based web service that will run properly under Weblogic 10.0. There are examples out there on how to create webservices that exists within a war file - but none that I can find that reside within a session bean (an ear file).
    I can't even figure out how to do with this Bea Workshop for WebLogic Platform 10.0! Is this possible? I can't find any examples anywhere on how to do this. I must be missing something...
    Does WebLogic 10.0 support web services within session beans? I've figured out how to do this with JBoss, Sun App Server, and Glassfish - but no luck so far with WebLogic.
    If anyone can please point me in the proper direction it would be very appreciated. My company likes WebLogic, but we have to be able to do this in order to continue using it.
    Thanks,
    -john

    Yeah - I've tried that. Everything builds fine - but when I deploy to WebLogic 10, I get the stack below. It looks like it is looking for the class examples.webservices.jaxws.jaxws.SayHello - but there isn't such a class in the example...
    Any thoughts? I'm completely stuck!
    <Apr 16, 2007 4:15:45 PM PDT> <Error> <HTTP> <BEA-101216> <Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    Truncated. see log file for complete stacktrace
    >
    <Apr 16, 2007 4:15:45 PM PDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1176765341457' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
    Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
    Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
    [HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
    at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
    at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
    at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
    at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
    Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
    Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
    [HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
    at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
    at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
    at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
    at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    Truncated. see log file for complete stacktrace
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    Truncated. see log file for complete stacktrace
    >
    <Apr 16, 2007 4:15:46 PM PDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application '_appsdir_WL6_ear'.>
    <Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_WL6_ear'.>
    <Apr 16, 2007 4:15:46 PM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception activating module: EJBModule(WL6-ejb.jar)
    Unable to deploy EJB: SimpleEjbImpl from WL6-ejb.jar:
    Unable to deploy EJB: WL6-ejb.jar from WL6-ejb.jar:
    [HTTP:101216]Servlet: "WSEE_SERVLET" failed to preload on startup in Web application: "/SimpleEjbImpl".
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    at com.sun.xml.ws.server.EndpointFactory.createSEIModel(EndpointFactory.java:229)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:161)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:291)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:315)
    at weblogic.wsee.jaxws.JAXWSServlet.registerEndpoint(JAXWSServlet.java:125)
    at weblogic.wsee.jaxws.JAXWSServlet.init(JAXWSServlet.java:64)
    at javax.servlet.GenericServlet.init(GenericServlet.java:241)
    at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
    at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
    at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
    at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
    at weblogic.wsee.deploy.WseeWebappModule.activate(WseeWebappModule.java:139)
    at weblogic.wsee.deploy.WSEEEjbModule.activate(WSEEEjbModule.java:371)
    at weblogic.wsee.deploy.WsEJBDeployListener.activate(WsEJBDeployListener.java:52)
    at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1414)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:464)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
    Truncated. see log file for complete stacktrace
    class: examples.webservices.jaxws.jaxws.SayHello could not be found
    at com.sun.xml.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:272)
    at com.sun.xml.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:566)
    at com.sun.xml.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:513)
    at com.sun.xml.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:358)
    at com.sun.xml.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:245)
    Truncated. see log file for complete stacktrace
    >

  • Losing session with WLS 7.02 in cluster env

              PROBLEM: We are losing our session when running in our app in a clustered environment.
              The user can use the app for a while, but then weird stuff starts happening. In
              some cases, the login check that we do at the begining of each request fails,
              because it tries to check for a login token in the session, and the session has
              been wiped out. The user gets forwarded to the login page.
              Our configuration is:
              WLS 7.0.2 (OS = Windows 2000)
              Admin Server and a managed server A at APP1 (physical machine), another managed
              server B
              at APP2 (physical machine), A and B is in one cluster. We had 6 Apache Servers
              2.0.45 (OS = Linux) and each works together with Weblogic Plugin. The weblogic
              plugin has the following configuration:
              <Location /sample>
              SetHandler weblogic-handler
              WeblogicCluster 10.1.1.11:7010,10.1.1.12:7010
              Idempotent ON
              CookieName JSESSIONID
              </Location>
              The server A and B use round-robin loadblancing, and we have a hardware loadblancer
              infront of Apache to do loadblancing for our 6 web servers.
              In weblogic.xml we config our application to use replicated for session failover.
              Losing session is randomly happened.
              Anyone of you have any idea?
              Thanks in advance.
              Harry
              

    To verify that it is WL and not your app logic, try using a different
              session replication implementation for testing, such as the one that comes
              with Coherence for Servlet 2.3 containers:
              http://www.tangosol.com/coherence.jsp
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com/coherence.jsp
              Tangosol Coherence: Clustered Replicated Cache for Weblogic
              "Harry Yu" <[email protected]> wrote in message
              news:[email protected]...
              >
              > PROBLEM: We are losing our session when running in our app in a clustered
              environment.
              > The user can use the app for a while, but then weird stuff starts
              happening. In
              > some cases, the login check that we do at the begining of each request
              fails,
              > because it tries to check for a login token in the session, and the
              session has
              > been wiped out. The user gets forwarded to the login page.
              >
              > Our configuration is:
              > WLS 7.0.2 (OS = Windows 2000)
              > Admin Server and a managed server A at APP1 (physical machine), another
              managed
              > server B
              > at APP2 (physical machine), A and B is in one cluster. We had 6 Apache
              Servers
              > 2.0.45 (OS = Linux) and each works together with Weblogic Plugin. The
              weblogic
              > plugin has the following configuration:
              > <Location /sample>
              > SetHandler weblogic-handler
              > WeblogicCluster 10.1.1.11:7010,10.1.1.12:7010
              > Idempotent ON
              > CookieName JSESSIONID
              > </Location>
              >
              > The server A and B use round-robin loadblancing, and we have a hardware
              loadblancer
              > infront of Apache to do loadblancing for our 6 web servers.
              >
              > In weblogic.xml we config our application to use replicated for session
              failover.
              >
              > Losing session is randomly happened.
              >
              > Anyone of you have any idea?
              >
              > Thanks in advance.
              >
              > Harry
              >
              

  • Deployig to a Cluster without losing session.

    Hi,
              We have a cluster setup with 4 servers. We use HttpSession and
              StatefulSessionBeans in the cluster with in-memory replication. Is it
              possible to redeploy the application to a cluster without losing
              session ?.
              Thanks,
              -Senthil.
              

    We have a cluster setup with 4 servers. We use HttpSession and          > StatefulSessionBeans in the cluster with in-memory replication. Is it
              > possible to redeploy the application to a cluster without losing
              > session ?.
              Not with WebLogic session replication. The session replication is "lazy"
              (only when something happens) so the best approach is to make sure there are
              no imcompatibilities and then cycle the cluster one server at a time, maybe
              one server every hour (or whatever your session timeout is).
              Peace,
              Cameron Purdy
              Tangosol, Inc.
              http://www.tangosol.com/coherence.jsp
              Tangosol Coherence: Clustered Replicated Cache for Weblogic
              "Senthil" <[email protected]> wrote in message
              news:[email protected]..
              > Hi,
              >
              >
              > Thanks,
              > -Senthil.
              

  • BPM for Weblogic configuration is failed

    1, I install BPM for Weblogic.
    2, I create a domain for weblogic using config tool and start it.
    3, I create a new directory.
    However, the configuration is failed.
    The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
    The log is as follows:
    For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
    changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
    The edit lock associated with this edit session is released
    once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear, to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear, to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed. at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48) at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185) at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536) at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160) at org.python.core.PyMethod.__call__(PyMethod.java:96) at org.python.core.PyObject.__call__(PyObject.java:248) at org.python.core.PyObject.invoke(PyObject.java:2016) at org.python.pycode._pyx17.deploy$8(<iostream>:223) at org.python.pycode._pyx17.call_function(<iostream>) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:404) at org.python.core.PyFunction.__call__(PyFunction.java:184) at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:256) at org.python.core.PyFunction.__call__(PyFunction.java:169) at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyCode.call(PyCode.java:14) at org.python.core.Py.runCode(Py.java:1135) at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167) at weblogic.management.scripting.WLST.main(WLST.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at weblogic.WLST.main(WLST.java:29)
    Exiting WebLogic Scripting Tool.
    <Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
    Do you want to cancel this wizard?

    Hi,
    Thanks for your reply. I change the file and reconfigure the BPM for weblogic. However, it is still failed in 70-72%.
    -------------------log message-------------------------------
    TO_MSG PATH=/root/bea/wlserver_10.3/server/bin:/root/bea/modules/org.apache.ant_1.6.5/bin:/root/bea/jrockit_160_05/jre/bin:/root/bea/jrockit_160_05/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
    TO_MSG
    TO_MSG Your environment has been set.
    TO_MSG
    TO_MSG CLASSPATH=/root/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/jrockit_160_05/lib/tools.jar:/root/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/root/bea/wlserver_10.3/server/lib/weblogic.jar:/root/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/root/bea/wlserver_10.3/server/lib/webservices.jar:/root/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/root/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/root/OraBPMwlHome/lib/fuego.boot.jar:/root/OraBPMwlHome/bin/./:/root/OraBPMwlHome/bin/./lax.jar::/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbembedded57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbtools57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar
    TO_MSG
    TO_MSG Initializing WebLogic Scripting Tool (WLST) ...
    TO_MSG
    TO_MSG Welcome to WebLogic Server Administration Scripting Shell
    TO_MSG
    TO_MSG Type help() for help on available commands
    TO_MSG
    TO_MSG Starting server BPMServer
    TO_MSG Please see the server log files for startup messages available at /root/weblogic3/bpm
    TO_MSG Starting weblogic server ...
    TO_MSG WLST-WLS-1249792014056: [WARN ] -XX:MaxPermSize=256m is not a valid VM option. Ignoring
    TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ26¥ネニ58￧ᄃメ CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ00￧ᄃメ CST> <Info> <Management> <BEA-140013> </root/weblogic3/bpm/config/config.xml not found>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ00￧ᄃメ CST> <Info> <Management> <BEA-141254> <Generating new domain directory in /root/weblogic3/bpm>
    TO_MSG .....WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ12￧ᄃメ CST> <Info> <Management> <BEA-141255> <Domain generation completed in 12,326 milliseconds.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ13￧ᄃメ CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
    TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ15￧ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ15￧ᄃメ CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ16￧ᄃメ CST> <Notice> <Log Management> <BEA-170019> <The server log file /root/weblogic3/bpm/servers/BPMServer/logs/BPMServer.log is opened. All server side log events will be written to this file.>
    TO_MSG ...WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ24￧ᄃメ CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    TO_MSG ....WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ34￧ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ34￧ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ34￧ᄃメ CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ35￧ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ35￧ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ35￧ᄃメ CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ35￧ᄃメ CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "BPMServer" for domain "bpm" running in Development Mode>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ36￧ᄃメ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ36￧ᄃメ CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    TO_MSG Server started successfully.
    TO_MSG Started Server. Trying to connect to the server ...
    TO_MSG Connecting to t3://localhost.localdomain:7001 with userid weblogic ...
    TO_MSG Successfully connected to Admin Server 'BPMServer' that belongs to domain 'bpm'.
    TO_MSG
    TO_MSG Warning: An insecure protocol was used to connect to the
    TO_MSG server. To ensure on-the-wire security, the SSL port or
    TO_MSG Admin port should be used instead.
    TO_MSG
    TO_MSG Location changed to edit tree. This is a writable tree with
    TO_MSG DomainMBean as the root. To make changes you will need to start
    TO_MSG an edit session via startEdit().
    TO_MSG
    TO_MSG For more help, use help(edit)
    TO_MSG
    TO_MSG Starting an edit session ...
    TO_MSG Started edit session, please be sure to save and activate your
    TO_MSG changes once you are done.
    TO_MSG creating mbean of type JMSServer ...
    TO_MSG creating mbean of type JMSSystemResource ...
    TO_MSG creating mbean of type SubDeployment ...
    TO_MSG creating mbean of type Queue ...
    TO_MSG creating mbean of type Topic ...
    TO_MSG creating mbean of type ConnectionFactory ...
    TO_MSG creating mbean of type ConnectionFactory ...
    TO_MSG creating mbean of type Server ...
    TO_MSG creating mbean of type JDBCSystemResource ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type JDBCSystemResource ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Property ...
    TO_MSG creating mbean of type Realm ...
    TO_MSG creating mbean of type RoleMapper ...
    TO_MSG creating mbean of type CredentialMapper ...
    TO_MSG creating mbean of type CertPathProvider ...
    TO_MSG creating mbean of type Authorizer ...
    TO_MSG creating mbean of type Adjudicator ...
    TO_MSG creating mbean of type AuthenticationProvider ...
    TO_MSG creating mbean of type AuthenticationProvider ...
    TO_MSG setting attributes for mbean type JMSServer
    TO_MSG setting attributes for mbean type JMSSystemResource
    TO_MSG setting attributes for mbean type SubDeployment
    TO_MSG setting attributes for mbean type Queue
    TO_MSG setting attributes for mbean type Topic
    TO_MSG setting attributes for mbean type JMSConnectionFactory
    TO_MSG setting attributes for mbean type JMSConnectionFactory
    TO_MSG setting attributes for mbean type Server
    TO_MSG setting attributes for mbean type JDBCSystemResource
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
    TO_MSG setting attributes for mbean type JDBCDriverParams
    TO_MSG setting attributes for mbean type JDBCDataSource
    TO_MSG setting attributes for mbean type DefaultIdentityAsserter
    TO_MSG setting attributes for mbean type SecurityConfiguration
    TO_MSG setting attributes for mbean type SecurityParams
    TO_MSG setting attributes for mbean type EmbeddedLDAP
    TO_MSG setting attributes for mbean type SecurityParams
    TO_MSG setting attributes for mbean type Domain
    TO_MSG setting attributes for mbean type JDBCDataSource
    TO_MSG setting attributes for mbean type JDBCXAParams
    TO_MSG setting attributes for mbean type JDBCDataSourceParams
    TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
    TO_MSG setting attributes for mbean type JDBCDriverParams
    TO_MSG setting attributes for mbean type JDBCDataSourceParams
    TO_MSG setting attributes for mbean type JDBCSystemResource
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG setting attributes for mbean type JDBCProperty
    TO_MSG Saving all your changes ...
    TO_MSG Saved all your changes successfully.
    TO_MSG Your edit session is not stopped, you can continue your edits.
    TO_MSG Activating all your changes, this may take a while ...
    TO_MSG The edit lock associated with this edit session is released
    TO_MSG once the activation is completed.
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute InternalAppsDeployOnDemandEnabled on weblogic.management.configuration.DomainMBeanImpl@fffe8220([bpm]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@1759a12([bpm]/Log[bpm]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute ListenAddress on weblogic.management.configuration.ServerMBeanImpl@2ddd7637([bpm]/Servers[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@2df105fa([bpm]/Servers[BPMServer]/Log[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.WebServerLogMBeanImpl@2df106e5([bpm]/Servers[BPMServer]/WebServer[BPMServer]/WebServerLog[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ27¥ネニ53￧ᄃメ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
    TO_MSG
    TO_MSG The following non-dynamic attribute(s) have been changed on MBeans
    TO_MSG that require server re-start:
    TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Log,Server=BPMServer
    TO_MSG Attributes changed : RotateLogOnStartup
    TO_MSG
    TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Server
    TO_MSG Attributes changed : ListenAddress
    TO_MSG
    TO_MSG MBean Changed : com.bea:Name=bpm,Type=Log
    TO_MSG Attributes changed : RotateLogOnStartup
    TO_MSG
    TO_MSG MBean Changed : com.bea:Name=bpm,Type=Domain
    TO_MSG Attributes changed : InternalAppsDeployOnDemandEnabled, ProductionModeEnabled
    TO_MSG
    TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=WebServerLog,Server=BPMServer,WebServer=BPMServer
    TO_MSG Attributes changed : RotateLogOnStartup
    TO_MSG
    TO_MSG Activation completed
    TO_MSG Creating a user ...
    TO_MSG
    TO_MSG Created user successfully
    TO_MSG Deploying application from /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ28¥ネニ01￧ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear], to BPMServer .>
    TO_MSG .Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ28¥ネニ08￧ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine [archive: /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear], to BPMServer .>
    TO_MSG .................Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ29¥ネニ48￧ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 08-workspace-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear], to BPMServer .>
    TO_MSG .Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ30¥ネニ45￧ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 09-feeds-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear], to BPMServer .>
    TO_MSG .Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ31¥ネニ00￧ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 06-workspaceadmin-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear], to BPMServer .>
    TO_MSG .Completed the deployment of Application with status completed
    TO_MSG Current Status of your Deployment:
    TO_MSG Deployment command type: deploy
    TO_MSG Deployment State : completed
    TO_MSG Deployment Message : no message
    TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear to targets BPMServer (upload=true) ...
    TO_MSG <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ31¥ネニ31￧ᄃメ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 07-papiws-wls103-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear], to BPMServer .>
    TO_MSG ..WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ31¥ネニ48￧ᄃメ CST> <Error> <HTTP> <BEA-101220> <Error occurred while setting document root for "weblogic.servlet.internal.WebAppServletContext@30302d0 - appName: '07-papiws-wls103-XAFDIDS.ear', name: 'papiws', context-path: '/papiws', spec-version: '2.5'" to "/root/weblogic3/bpm/servers/BPMServer/tmp/_WL_user/07-papiws-wls103-XAFDIDS.ear/f0r1c0/papiws.war".>
    TO_MSG WLST-WLS-1249792014056: <2009-8-9 ¦ᄌヒ¥ヘネ12₩ラᄊ31¥ネニ48￧ᄃメ CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249792304208' for task '5'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'papiws''
    TO_MSG WLST-WLS-1249792014056: weblogic.application.ModuleException: Failed to load webapp: 'papiws'
    TO_MSG WLST-WLS-1249792014056:      at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    TO_MSG WLST-WLS-1249792014056:      Truncated. see log file for complete stacktrace
    TO_MSG WLST-WLS-1249792014056: java.io.IOException: Error opening file
    TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.open(Native Method)
    TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.<init>(ZipFile.java:117)
    TO_MSG WLST-WLS-1249792014056:      at java.util.zip.ZipFile.<init>(ZipFile.java:133)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.classloaders.ZipClassFinder.<init>(ZipClassFinder.java:23)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.application.io.ArchivedWar$WebInfClassesFinder.<init>(ArchivedWar.java:290)
    TO_MSG WLST-WLS-1249792014056:      Truncated. see log file for complete stacktrace
    TO_MSG WLST-WLS-1249792014056: >
    TO_MSG WLST-WLS-1249792014056: java.io.FileNotFoundException: /root/weblogic3/bpm/config/config.xml (Too many open files)
    TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.open(Native Method)
    TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
    TO_MSG WLST-WLS-1249792014056:      at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.FileUtils.writeToFile(FileUtils.java:115)
    TO_MSG WLST-WLS-1249792014056:      at weblogic.utils.Fil

  • Configuration is failed - BPM for Weblogic 10.3.1

    1, I install BPM for Weblogic.
    2, I create a domain for weblogic using config tool and start it.
    3, I create a new directory.
    However, the configuration is failed.
    The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
    The log is as follows:
    For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
    changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
    The edit lock associated with this edit session is released
    once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear], to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 [archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear], to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed.      at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)      at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185)      at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536)      at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429)      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)      at java.lang.reflect.Method.invoke(Method.java:597)      at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)      at org.python.core.PyMethod.__call__(PyMethod.java:96)      at org.python.core.PyObject.__call__(PyObject.java:248)      at org.python.core.PyObject.invoke(PyObject.java:2016)      at org.python.pycode._pyx17.deploy$8(<iostream>:223)      at org.python.pycode._pyx17.call_function(<iostream>)      at org.python.core.PyTableCode.call(PyTableCode.java:208)      at org.python.core.PyTableCode.call(PyTableCode.java:404)      at org.python.core.PyFunction.__call__(PyFunction.java:184)      at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623)      at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py)      at org.python.core.PyTableCode.call(PyTableCode.java:208)      at org.python.core.PyTableCode.call(PyTableCode.java:256)      at org.python.core.PyFunction.__call__(PyFunction.java:169)      at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738)      at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py)      at org.python.core.PyTableCode.call(PyTableCode.java:208)      at org.python.core.PyCode.call(PyCode.java:14)      at org.python.core.Py.runCode(Py.java:1135)      at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)      at weblogic.management.scripting.WLST.main(WLST.java:129)      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)      at java.lang.reflect.Method.invoke(Method.java:597)      at weblogic.WLST.main(WLST.java:29)
    Exiting WebLogic Scripting Tool.
    <Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
    Do you want to cancel this wizard?

    Hi Ye,
    I noticed this afternoon that Oracle's refering to Oracle WebLogic 10.3.1 as "Oracle WebLogic 11g".
    Know this comes as no surprise to you, but when I tried to install Oracle BPM 10gR3 Enterprise on WebLogic 11g (WebLogic 10.3.1) this afternoon it failed. A friend pointed out to me that Oracle WebLogic 11g does not support the DataDirect JDBC driver. Since Oracle BPM Enterprise 10gR3 uses this driver to connect to both its Engine database and Directory Service databases, he's thinking this might be the cause of our problem.
    It would be worth verifying this with Support. Here's what I think they'll point you to. The Oracle BPM 10gR3 release notes(http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/relnotes/release_notes_OracleBPM10gR3.htm#N65589) indicate that the only WebLogic application servers supported are Oracle WebLogic 10.3 (10gR3), Oracle WebLogic 10.0 MP1.
    Again, talk to Support, but I don't think there's a workaround. The only thing I think you can do is to uninstall WebLogic 10.3.1 and then install WebLogic 10.3 if you want to install Oracle BPM 10gR3 Enterprise on it.
    Dan

  • Multiple sessions for the same user

    Hi,
    The scenario is like this. The user is logged into the system using JAAS and
    has a session object created. I want to create a new session for the same user
    with the already available credentials. This is to provide the same user the access
    to the application in another window with different session object. How can do
    that in Weblogic 8.1 server ?
    thanks in advance,
    Krishna.

    Hi
    I think it would be easier to enable session time out settings using GPO considering you work in a domain environment..
    Having session timeouts settings you could say... hey after 15 min of inactivity disconnect the user and then after 15 min of disconnected session log him off
    Take a look at this URL: http://technet.microsoft.com/en-us/library/cc754272.aspx
    Hope this helps
    Best regards
    Joaquin Camarero Muñoz

  • What's the available value for weblogic.jsp.encoding in web application.

    Hi,
              I'm using chinese windows nt 4.0 and weblogic 5.1 sp6.When I did not set
              weblogic.jsp.encoding to GB2312 , when the jsp file contain's chinese , the
              output will be error .And when I did not set it , the output is correct, but
              when I use request.getParameter("SomeFormElement")(the element inputed
              chinese), the return value is error.
              How should I set weblogic.jsp.encoding value to satisfy all this problem?
              When I set the value to ISO-8859, there is an exception:
              java.io.UnsupportedEncodingException: Charset: 'ISO-8859' not recognized,
              and there is no alias for it in the weblogic.httpd.charsets property. So
              What's the available value for weblogic.jsp.encoding in web application?
              Pan
              

    hi ,
    i think the best way is to create java beans ,in that bean call your EJB ,
    and check the validation over there.
    and make that bean scope to session.
    in each and everypage try to check the session ,if it is not valid then forward to your login page...
    otherwise continue to give access to him like guest
    Regards,
    AfTaB

  • Unique session key  weblogic portal 9.2

    Hi,
    Is there a way I can generate unique session key to ensure correct session is tracking between every desktop with different user.
    Is this right way to handle session in weblogic portal 9.2?

    Hi
    what exactly do you want to do? A session does have an id which is guaranteed unique while the server is running (you dont need to do anything special for this). HttpSession.getId.
    Note However normally this value gets stored as a cookie on the browser (with the default name of JSESSIONID) and you must ensure that different webapps on the same domain dont overwrite this value
    regards
    deepak

  • Writing a plugin for Weblogic

    Hi,
    Is it possible to add a mechanism to Weblogic which would intercept
    EJB lookups and requests (on a per bean and per method basis), and
    perform custom access control logic? This mechanism should be seamless
    and transparent to client code so that existing apps would not have to
    be modified. In effect, I would like to create a plugin for Weblogic
    in much the same way as you can create a plugin for web servers like
    Apache, IIS, etc.
    Alternatively, if this effect could be achieved simply through
    configuration changes, then even better. Customized security realms do
    not exactly fit what I want to do because they have to be manually
    created per client, and I would also like to perform additional logic
    besides access control.
    Thanks in advance,
    Steve Au

    Wouldn't EJB clients have to be rewritten to access this proxy bean instead? What
    would prevent clients from accessing the "secured" EJBs directly?
    Thanks.
    "Michael Girdley" <----> wrote:
    We do not offer such an interface natively to write your own security
    interceptors. But, I can imagine someone writing a session bean proxy
    that
    intercept all EJB calls in this way before forwarding them along.
    We plan to offer such functionality in a future release without requiring
    any kludges.
    Michael Girdley
    BEA Systems
    Learning WebLogic? http://learnweblogic.com
    Buy the only book covering J2EE & WebLogic 6:
    http://www.amazon.com/exec/obidos/ASIN/0130911119/learnweblogic/103-9227026-
    4636613
    "Steve Au" <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    Is it possible to add a mechanism to Weblogic which would intercept
    EJB lookups and requests (on a per bean and per method basis), and
    perform custom access control logic? This mechanism should be seamless
    and transparent to client code so that existing apps would not haveto
    be modified. In effect, I would like to create a plugin for Weblogic
    in much the same way as you can create a plugin for web servers like
    Apache, IIS, etc.
    Alternatively, if this effect could be achieved simply through
    configuration changes, then even better. Customized security realmsdo
    not exactly fit what I want to do because they have to be manually
    created per client, and I would also like to perform additional logic
    besides access control.
    Thanks in advance,
    Steve Au

  • SUn Policy Agent 2.2 for Weblogic 92

    We are using SUN POlicy agent 2.2. (for Weblogic) for Access Manager 6.3
    For this particular application I intermittantly get SSOToken invald message
    Its a sporadic behavior (sometimes work sometime does not)
    error -
    02/02/2007 12:22:41:057 PM EST: Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads]
    SSOTokenValidator.validate(): Exception caught
    com.iplanet.sso.SSOException: AQIC5wM2LY4Sfcw k8CIsj Jujq92ltM5fNZJxh2qFYpAyw=@AAJTSQACMDE=# Invalid session ID.AQIC5wM2LY4Sfcw k8CIsj Jujq92ltM5fNZJxh2qFYpAyw=@AAJTSQACMDE=#

    check the patch level of AM 6.3, it should be higher than 1

  • Regarding New for weblogic portal

    hi every one.
    My name is krishnarjun yada. I am the new for weblogic portal applicatons and i have a training on next weak. But i don't know much more about on portal.I mean which topics are there and how to work. I have knowledge on WebspherePortalServer. Please guide me anyone it's very need for me.
    Please reply to <email address removed by moderator> ASAP.

    *** moderator note ***
    I've removed your email address from the post because a) you are likely to get lots of spam in your email by publishing it in public and b) responses to issues should be posted on the forum, as this is not a personal support service where people should be contacting you directly.
    Also please note that this is a forum of volunteers doing their own jobs, and leading their own lives, so to request help "ASAP" or "Urgently" etc. is not appropriate and considered very rude by many people.  Such urgent issues suggest a live system that has got problems and a company is losing money or people's lives are at risk, in which case the issue should be raise via My Oracle Support (MOS) which is the paid-for support channel for Oracle.
    The description of your issue, wanting to know more about a product before your training, is not an urgent issue. (Surely the point of the training is to learn it?)
    *** end of moderator note ***

  • How do i configure mail session in Weblogic 8.1

    Hi all,
    I am having dead end here,
    I have tried to configure a mail session in weblogic 8.1
    I have created a mail service (service/mail) in weblogic console, with the JNDI named mail/MailFolderClientSession.
    and properties like this :
    mail.store.protocol=pop3
    mail.user=test@wiyanto
    mail.transport.protocol=smtp
    mail.smtp.host=11.2.145.64
    mail.debug=true
    mail.from=test@wiyanto
    mail.host=11.2.145.64
    mail.smtp.auth=false
    mail.smtp.user=test@wiyanto
    mail.pop3.host=11.2.145.64
    wiyanto is my computer name
    11.2.145.64 is my IP address
    and I used Imail as my mail server
    in the weblogic-ejb-jar.xml i have added this :
    <weblogic-enterprise-bean>
         <ejb-name>Email</ejb-name>
         <reference-descriptor>
              <resource-description>
                   <res-ref-name>EmailSession</res-ref-name>
                   <jndi-name>mail/MailFolderClientSession</jndi-name>
              </resource-description>
         </reference-descriptor>
         <jndi-name>ejb/EmailHome</jndi-name>
    </weblogic-enterprise-bean>
    and I have set the mail session to run automatically when i start the weblogic server.
    but i still encounter this :
    MailFolderClient: MessagingException in connectToMailStore [javax.mail.AuthenticationFailedException]
    MailFolderClient: login: Connection to mailstore failed
    Please tell me what is wrong with this, b'cause I met dead end on every search on google :(
    Any suggestion is more than welcome.

    To join the domain, you can follow these steps:
    1.Open System by swiping in from the right edge of the screen, tapping Search (or if you're using a mouse, pointing to the upper-right corner of the screen, moving the mouse pointer down, and then clicking Search), entering System in the search box, and
    tapping or clicking System.
    2.Under Computer name, domain, and workgroup settings, click Change settings. Administrator permission required You might be asked for an admin password or to confirm your choice.
    3.Click Network ID and follow the steps on your screen.
    Alex Zhao
    TechNet Community Support

Maybe you are looking for

  • Is there any function module which will upload storage locations for a mat

    Hi gurus,   Is there any function module or BAPI to extend the storage locations of material which is done through <b>MMSC</b> transaction. I need to write a program to upload new storage locations for some materials.Please advise. Thanks , Sam.

  • TS1702 Some of my purchased apps are not showing in iTunes...

    I'm using the latest version of iTunes for Win8. 1 day after restoring a backup on my iPhone 5, some of the apps that was previously loaded in from the restoration disappeared somehow. Later on when I tried to download the apps from iTunes, they did

  • HT1766 Wifi button grayed out

    My wifi button is grayed out, therefore I cannot backup my iphone. What should I do?

  • Setting up diskgroups in ASM

    Hello - I'm trying to setup diskgroups in an ASM instance, but get an error indicating the disks do not exist. I'm testing the setup of this using ASM on top of Unix file systems. I'm testing on Solaris 9. Do I reference a physical LUN on the SAN, or

  • Problems logging in when trying to create ringtones

    I recently purchased the iPhone, and followig the instructions, set up my iTunes to convert some of my iTunes-purchased songs to ringtones. However, when iTunes prompts me to log-in to my Apple iTunes account, it won't accept my password. I checked,