Replication in a Cluster of 2 machines

Hi again,
          I have a cluster of 2 m/c , Requests are being served by A and I bring A
          Down
          'B' takes over , but when I bring up A again , both fail !
          I need some help !
          The Stack traces on A and B are :
          The Stack on A is :
          ++++++++++++++++
          <Jul 31, 2002 5:00:15 PM PDT> <Error> <HTTP Session> <Error looking up
          session for id:9I4trxgFdltJ7Yzz3YjvhEPJd1A5XnlCPm
          4nzIwGny1sytuNGPMT!-388044873!167772203!7001!7002!NONE
          java.lang.NullPointerException:
          Start server side stack trace:
          java.lang.NullPointerException
          at
          weblogic.servlet.internal.session.SessionData.getContext(SessionData.java:34
          1)
          at
          weblogic.servlet.internal.session.ReplicatedSessionData.becomeSecondary(Repl
          icatedSessionData.java:167)
          at weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34)
          at
          weblogic.cluster.replication.ReplicationManager$wroManager.create(Replicatio
          nManager.java:352)
          at
          weblogic.cluster.replication.ReplicationManager.create(ReplicationManager.ja
          va:1083)
          at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown
          Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
          at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
          at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          at
          weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
          java:85)
          at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy152.create(Unknown Source)
          at
          weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationMana
          ger.java:880)
          at
          weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationM
          anager.java:835)
          at
          weblogic.cluster.replication.ReplicationManager.getPrimary(ReplicationManage
          r.java:799)
          at
          weblogic.cluster.replication.ReplicationManager.lookup(ReplicationManager.ja
          va:425)
          at
          weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInterna
          l(ReplicatedSessionContext.java:2
          68)
          at
          weblogic.servlet.internal.ServletRequestImpl.getValidSession(ServletRequestI
          mpl.java:2186)
          at
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          ava:1948)
          at
          weblogic.servlet.security.ServletAuthentication.weak(ServletAuthentication.j
          ava:266)
          at
          weblogic.servlet.security.internal.BasicSecurityModule.checkAuthenticateHead
          er(BasicSecurityModule.java:65)
          at
          weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
          tSecurityManager.java:119)
          at
          weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          ntext.java:2518)
          at
          weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          :2260)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          At B its :
          ++++++
          <Jul 31, 2002 5:00:18 PM PDT> <Warning> <Dispatcher> <RuntimeException
          thrown by
          rmi server: 'weblogic.rmi.internal.BasicServerRef@10 - jvmid:
          '3432093889910090
          597S:10.0.0.33:[7001,7001,7002,7002,7001,7002,-1]:admindomain:server2', oid:
          '16
          ', implementation: 'weblogic.cluster.replication.ReplicationManager@398fe1''
          java.lang.NullPointerException
          at
          weblogic.servlet.internal.session.SessionData.getContext(SessionData.
          java:341)
          at
          weblogic.servlet.internal.session.ReplicatedSessionData.becomeSeconda
          ry(ReplicatedSessionData.java:167)
          at weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34)
          at
          weblogic.cluster.replication.ReplicationManager$wroManager.create(Rep
          licationManager.java:352)
          at
          weblogic.cluster.replication.ReplicationManager.create(ReplicationMan
          ager.java:1083)
          at
          weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown
          Source)
          at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
          at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:274)
          at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >

I hope you are right,
          But its no longer a problem for me after I changed the stuff..
          Thanks though,
          _NR
          "Kumar Allamraju" <[email protected]> wrote in message
          news:[email protected]...
          > First of all the following NPE has nothing to do with using
          > weblogic.servlet.proxy.HttpClusterServlet or
          > weblogic.servlet.internal.HttpClusterServlet. For backward compatibility
          > purposes you can still use weblogic.servlet.internal.HttpClusterServlet
          >
          > The following NPE is a known issue in SP2 and is fixed in SP3.
          >
          > --
          > Kumar
          >
          > [email protected] wrote:
          >
          > > hmmm....
          > >
          > > Again figured it out myself..
          > >
          > > I was using the (depreicated)
          weblogic.servlet.internal.HttpClusterServlet
          > > in the web.xml (Default app for Admin)
          > >
          > > I changed it to weblogic.servlet.proxy.HttpClusterServlet and everythin
          > > works fine !!
          > >
          > > thought this info might be useful !
          > >
          > > --Naggi
          > > PS: Now running WLS 6.1 SP3 with CR081194_61sp3.jar
          > >
          > >
          > >
          > >
          > > <[email protected]> wrote in message
          news:[email protected]...
          > >
          > >>Hi again,
          > >>I have a cluster of 2 m/c , Requests are being served by A and I bring
          A
          > >>Down
          > >>'B' takes over , but when I bring up A again , both fail !
          > >>
          > >>I need some help !
          > >>
          > >>The Stack traces on A and B are :
          > >>
          > >>The Stack on A is :
          > >>++++++++++++++++
          > >><Jul 31, 2002 5:00:15 PM PDT> <Error> <HTTP Session> <Error looking up
          > >>session for id:9I4trxgFdltJ7Yzz3YjvhEPJd1A5XnlCPm
          > >>4nzIwGny1sytuNGPMT!-388044873!167772203!7001!7002!NONE
          > >>
          > >>java.lang.NullPointerException:
          > >>
          > >>Start server side stack trace:
          > >>
          > >>java.lang.NullPointerException
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.internal.session.SessionData.getContext(SessionData.java:34
          > >
          > >>1)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.internal.session.ReplicatedSessionData.becomeSecondary(Repl
          > >
          > >>icatedSessionData.java:167)
          > >>
          > >>at weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.cluster.replication.ReplicationManager$wroManager.create(Replicatio
          > >
          > >>nManager.java:352)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.cluster.replication.ReplicationManager.create(ReplicationManager.ja
          > >
          > >>va:1083)
          > >>
          > >>at weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown
          > >>Source)
          > >>
          > >>at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
          > >
          > >>at
          > >>
          > >>
          > >
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          > >
          > >>2)
          > >>
          > >>at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > >>
          > >>at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >>
          > >>End server side stack trace
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.
          > >
          > >>java:85)
          > >>
          > >>at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:136)
          > >>
          > >>at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          > >>
          > >>at $Proxy152.create(Unknown Source)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.cluster.replication.ReplicationManager.trySecondary(ReplicationMana
          > >
          > >>ger.java:880)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationM
          > >
          > >>anager.java:835)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.cluster.replication.ReplicationManager.getPrimary(ReplicationManage
          > >
          > >>r.java:799)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.cluster.replication.ReplicationManager.lookup(ReplicationManager.ja
          > >
          > >>va:425)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.internal.session.ReplicatedSessionContext.getSessionInterna
          > >
          > >>l(ReplicatedSessionContext.java:2
          > >>
          > >>68)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.internal.ServletRequestImpl.getValidSession(ServletRequestI
          > >
          > >>mpl.java:2186)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          > >
          > >>ava:1948)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.security.ServletAuthentication.weak(ServletAuthentication.j
          > >
          > >>ava:266)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.security.internal.BasicSecurityModule.checkAuthenticateHead
          > >
          > >>er(BasicSecurityModule.java:65)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
          > >
          > >>tSecurityManager.java:119)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          > >
          > >>ntext.java:2518)
          > >>
          > >>at
          > >>
          > >>
          > >
          weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          > >
          > >>:2260)
          > >>
          > >>at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > >>
          > >>at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >>
          > >>
          > >>
          > >>At B its :
          > >>++++++
          > >>
          > >><Jul 31, 2002 5:00:18 PM PDT> <Warning> <Dispatcher> <RuntimeException
          > >>thrown by
          > >> rmi server: 'weblogic.rmi.internal.BasicServerRef@10 - jvmid:
          > >>'3432093889910090
          > >>597S:10.0.0.33:[7001,7001,7002,7002,7001,7002,-1]:admindomain:server2',
          > >>
          > > oid:
          > >
          > >>'16
          > >>', implementation:
          > >>
          > > 'weblogic.cluster.replication.ReplicationManager@398fe1''
          > >
          > >>java.lang.NullPointerException
          > >> at
          > >>weblogic.servlet.internal.session.SessionData.getContext(SessionData.
          > >>java:341)
          > >> at
          > >>weblogic.servlet.internal.session.ReplicatedSessionData.becomeSeconda
          > >>ry(ReplicatedSessionData.java:167)
          > >> at
          > >>
          > > weblogic.cluster.replication.WrappedRO.<init>(WrappedRO.java:34)
          > >
          > >> at
          > >>weblogic.cluster.replication.ReplicationManager$wroManager.create(Rep
          > >>licationManager.java:352)
          > >> at
          > >>weblogic.cluster.replication.ReplicationManager.create(ReplicationMan
          > >>ager.java:1083)
          > >> at
          > >>weblogic.cluster.replication.ReplicationManager_WLSkel.invoke(Unknown
          > >> Source)
          > >> at
          > >>weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
          > >> at
          > >>weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > >>a:274)
          > >> at
          > >>weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > >>.java:22)
          > >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >>
          > >>
          > >>
          > >>
          > >>
          > >>
          > >>
          > >
          > >
          >

Similar Messages

How to Delete the node from cluster when the machine crashed?

In an three nodes Rac of 11g r2,How to delete the node from cluster when the machine crashed?
There is now way to repair the machine and have to add a new one.
What is step to follow up?

hi
IF YOU WANT TO DELETE RAC1 NODE
check $./olsnodes
1) delete the instance using dbca from any active nodes
crs_stat -t
srvctl stop asm -n rac1
2) delete listener
3) delete oracle_home from oracle user
$ORACLE_HOME/bin/runInstaller -updatenodelist ORACLE_HOME=<db_home> "CLUSTER_NODES={RAC1}
4)delete asm home
$ORACLE_HOME/bin/runInstaller -updatenodelist ORACLE_HOME=<asm_home> "CLUSTER_NODES={RAC1}
5) update cluster node
$ORACLE_HOME/bin/runInstaller -updatenodelist ORACLE_HOME=<db_home> "CLUSTER_NODES={active nodes like rac2,rac3}
6) update ASm home
$ORACLE_HOME/bin/runInstaller -updatenodelist ORACLE_HOME=<asm_home> "CLUSTER_NODES={active nodes like rac2,rac3}
cd $ORA_CRS_HOME
cd crs/opmn/conf
check for
$cat ons.config
remoteport=6200
cd crs_home/bin
$./racgons remove_config rac1:6200
$ go to crs home
and $ORA_CRS_HOME/crs/install/rootdelete.sh
$ORA_CRS_HOME/crs/install/rootdeletenode.sh
check for ./olsnodes

Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
Any suggestion on resolving this problem?
Thanks
Ikad

Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
Ikad

Constantly "Cluster resource 'Virtual Machine' in clustered service or application 'SERVER' failed

Hi...
I have an IBM BladeCenter S with 3 blades and an IBM System Storage DS3300 (ISCSI).
In each blade is running Windows Server 2008 R2 with
HYPER-V,
Failover Clustering with Cluster Shared Volumes.
I have observed that many errors occur constantly in "Failover Cluster Manager" and some VM´s are relocated to another blade automatically, however thoses VM´s sometimes no longer responds to network activity.
The errors I have observed in the "Failover Cluster Manager" are:
Source: Microsoft-Windows-FailoverClusting
Event ID: 1069
Description:
Cluster resource 'Virtual Machine' in clustered service or application 'SERVER' failed.
Source: Microsoft-Windows-FailoverClusting
Event ID: 1205
Description:
The Cluster service failed to bring clustered service or application 'SV-DBURAS' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Another error (warning type) that is constantly generated in the SYSTEM events (Mirage is the storage name):
Source:        ds4dsm
Event ID:      769
Description:
IO error being retried via alternate controller Mirage:1
Source:        ds4dsm
Event ID:      10
Description:
Mirage:0 Failover command issued.
Source:        ds4dsm
Event ID:      801
Description:
Failover succeeded to Mirage:0.
Thank you in advance any help!

Hi,
I suggest referring to the following articles:
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc773525(WS.10).aspx
Tim Quan - MSFT

Cluster on one machine?

This may sound weird, but I am trying to setup a cluster on one machine. it has 2 nic's, I can assign 2 IP Adresses. The reason behind this, is we need to do testing in a clustering environment, but we don't have any spare machines for this.
          The hardware is Sun 250, 2 NICS running Solaris 2.7.


use ..
          weblogic.system.bindAddr = <ip_address>
          to any one of your weblogic.properties file .....
          That will make sure that blogic starts up only binding to that ip.
          "Kevin Enslow" <[email protected]> wrote in message
          news:39b5953e$[email protected]..
          > This may sound weird, but I am trying to setup a cluster on one machine.
          it has 2 nic's, I can assign 2 IP Adresses. The reason behind this, is we
          need to do testing in a clustering environment, but we don't have any spare
          machines for this.
          >
          > The hardware is Sun 250, 2 NICS running Solaris 2.7.

Http session replication fails in cluster

Hello everybody.
I have some problems with HTTP session replication in WebLlogic cluster environment. I have a cluster with 2 nodes and application deployed there. Application is configured with:
<session-param>
<param-name>PersistentStoreType</param-name>
<param-value>replicated</param-value>
</session-param>
in weblogic.xml
WebLogic plug-in for Apache webserver is configured properly as described in documentation.
But when I try to make experiment to enter the application, make some activities, look in console where I was redirected by apache proxy and manually shut down the node where request was sent, I loose my HTTP session with all data there (all the beans stored in session are Serializable). Replication doesn't work correctly. May be I've missed something in configuration? How can I configure my application to provide correctness session replication?
Thanks for advice.
Thanks

Thanks for response!
I'm using WebLogic 8.1 SP 4 and configured Apache proxy as described in documentation for load balancing. The only section I have in httpd.conf is next:
<Location /HTTPClnt>
     SetHandler weblogic-handler
</Location>
<IfModule mod_weblogic.c>
     WebLogicCluster serv1:7541,serv2:7541
     MatchExpression *.*
     Debug ON
     WLLogFile /www/tmp/global_proxy.log
     WLTempDir "/www/tmp"
     DebugConfigInfo On
     KeepAliveEnabled ON
     KeepAliveSecs 15
</IfModule>
<Location /myApp>
     SetHandler weblogic-handler
     WebLogicCluster serv1:7541,serv2:7541
</Location>and the string to include weblogic proxy module for apache:
LoadModule weblogic_module     modules/mod_wl_20.soI've configured CookiesEnabled=true in weblogic.xml, but it didn't help. About session specification in httpd.conf - where can I read about that? I've just configured apache according to manual from here:
[url http://e-docs.bea.com/wls/docs92/plugins/apache.html]http://e-docs.bea.com/wls/docs92/plugins/apache.html
Thanks

JNDI replication within a cluster

Hi to all of you,
we successfully enabled HTTP Session replication and tested the failover. We would also like to setup a JNDI replication, so that we can use it as a storage for some shared data -- as stated in http://download.oracle.com/docs/cd/B10464_05/web.904/b10324/cluster.htm this should be enabled automatically, once EJB replication is enabled.
With some problems we finally enabled EJB replication (we configured it through orion-application.xml) and the required replication policy is propagated to our statful beans. Anyway, the JNDI is still not replicated over the machines.
We are running latest OAS 10g, cluster is MultiCast on RedHat Enterprise, replication policy for Stateful beans is set to 'onRequestEnd' (we tried all the options :), our application is normal ear with 1 ejb and 1 war archive and apart from JNDI replication, it works as expected.
Is there some trick that is not mentioned or that we may overlooked in documentation to enable JNDI replication?
Kind Regards,
Martin

Hopefully solved -- though the documentation explicitly mentions rebinding as not working, after any changes made to value stored in JNDI context you should just re-bind the value to the JNDI context; the value is replicated to other JNDI contexts.
m.

Question on potential configurations for resource cluster as virtual machine server / beowulf / render farm

I am looking for a starting point on where to focus my efforts in researching a desired configuration. Of course anyone who spends anytime researching in forums knows that one thing that people hate is for people
to ask questions that can be easily answered with a simple Google search, so let me start by saying I have done many hours of research on this already. The problem I am having is that although there is a huge amount of information out there on what I
am looking to do, I don't believe many people have attempted this on as small of a scale as a single user system. Also, the amount of routes to go down seems endless, which for me so far has led to many hours of wasted trial and error. So keep
in mind that I am not so much looking for a handout on answers but rather a more narrowed path of searching and researching.
What I am looking to do is take the current equipment that I have and consolidate it into a 9-12U server rack using mounted 2 or 3U atx cases so that I can have a more organized, space saving setup. That is the
easy part, what I have been looking into though is the combining of cores and processing power to make a "super computer" yet I use this term very loosely. From what I have read, the closest thing I can compare the idea in my head to is referred
to as a Beowulf Cluster, or a Render farm but I believe as the name suggests that this is more dedicated to a single task of rendering. I like the idea of a virtual machine server where I would never actually locally use this machine but rather set up
many virtual machines that I can remote into. I started to compile a ProxMox Server, and this was the right idea, however when running a VM, that VM is constrained to the hardware resources of the single node that it is assigned to. If there is
a way to be able to have a machine that would utilize the 20 some odd cores that I would have in the cluster, along with the 40-50 gigs of ram, well that would be ideal but sounds too good to be possible. Also, ProxMox isnt quite there in compatibility for
a home/home office user. I understand that the programs that are used have to be written in a way where the architecture allows for such, but if it could even be used for speeding up my render time with Adobe and Autodesk (which I know do have such functionality)
that would be wonderful.
So without writing a whole book I am looking for suggestions on how to proceed. Can I literally build a "super computer" that is not really that super... more mediocre super... or am I better off just consolidating the hardware but not the
OS's and programs. Also, I do currently use three or four different distros of Linux, mostly for ethical hacking and security type work like pen testing. One thing I have never been a fan of though is dual booting. Perhaps investing
in a hot-swap HDD chassis that I could load all the different OS's on where I could just pop in whatever OS I am looking to use. As you can see I am far from knowing where to spend my efforts in research.... THANK YOu for ANY help.
I was recently suggested Microsoft HPC Pack as a platform? Anything?
Here is what I currently have:
these are all fully built)
Intel i5 3.7 quad core
Nvidia (ASUS) GTX-760
16 Gb DDR3 @ 1600 Corsair
ASUS Sabertooth Z87 MoBo
Autodesk - Inventor, Revit, 3Ds Max, Maya, Fusion 360, Flow, etc.
Adobe - PhotoShop, After Effects, Dreamweaver, Illustrator, etc.
Basically as you can see this is used for my work in 3d modeling, rendering, and drafting along with 3D printing.
Sys. #2
AMD 4.7-5.0 8 Core
Nvidia GTX 760 (Same as sys #1)
16 Gb DDR3 @ 2400 Mhz
ASUS Crosshair V Formula Z
Various programs for programming, app development, gaming, etc. (This is my daily driver)
Sys #3
AMD 4.5-4.7 8 core
16 Gb DDR3 @ 1600 Mhz
Asus Crosshair V Formula Z MoBo
Not currently using this one but is fully functional.
Sys #4
HP built i5 3.4 quad core
12 Gb DDR3 @ 1600
Nothing Special - this is the one I was using for school work but being that school and programming became one and the same I have all but abandoned it.
THANK YOU AGAIN TO ANYONE WHO HAS MADE IT THIS FAR in reading this.

The cluster works only for standalone webcache and httpserver installations types.
If you want to do this you have to use dcmctl command to change from one farm to another.
try checking with dcmctl command with out options an dyou will get a full list of options.
then run dcmctl usage(orhelp) option to see what you need.
As far as I remember
you have to check the farm id of the server you want to be the master
then in the second, you have to run dcmctl joinfarm or something like that.
Regards.

Weblogic Cluster on a machine with multiple NIC

Out Setup
          One Quad Machine
          2 NIC - one ip address on each
          Two weblogic installations
          Each Instance is listening on one address and port 7001.(managed servers)
          Admin Server on one of the ip and port 8001
          Both managed servers part of a cluster.
          While i check weblogic console i see both the managed server
          having almost same number of frames incoming and outgoing.
          If i check 4 processers all 4 of them working eqaully same
          during out load test..(almost 85%)
          But i check NICs only one of them seems to be working really hard..
          and another one so..so.. what could be the problem??


          Weblogic 7 has a new concept called network channel, where there is a section talking
          about clustering over multiple NIC cards. I was confused by the cluster address in
          customized network channel (no example there). I tried to use multiple NIC cards
          for the purpose of network failover, but failed in clustering environment, although
          I succeed in single server environment.
          Kumar Allamraju <[email protected]> wrote:
          >You can set Interface address via admin console's
          >Cluster >> {Cluster Name }
          >
          >on the right hand side you will find InterfaceAddress box.
          >
          >--
          >Kumar
          >
          >zevit wrote:
          >
          >>>It's the JVM & OS who will take adv. of multiple NIC's. We don't have
          >>>anything in WLS that does this thing.
          >>>
          >>>Alternatively you can bind each WLS instance to a specific NIC card
          >>>to effeciently utilize each NIC card.
          >>>
          >>
          >> thank u kumar.. Could u please tell me how do i bind each WSL instance
          >> to a specific NIC ?
          >>
          >

Can't set up cluster - wont accept machines from service browser

Hi, I hope someone can help me with this as I have spent the whole afternoon trying to sort this out and nothing has worked.
I have a G5 quad as the main computer and two G4's.
Each has qmaster installed with the update. Each of the three is running os 10.4.11
I have set the Qmaster preferences on each machine as detailed in http://visionstudios.ca/RenderFarm/RenderFarmleft.html
I have got to the part where I drag and drop the three computers into the services window but it doesn't work.
I can drag the main computer but trying to drag the other two results in Qadministrator hanging for a very long time and then finally rejecting them.
Can anyone tell me what is going on? I'm using a Netgear DS516 stackable 10/100 switch/hub to link the machines.
I did change the "shared cluster storage" location on the two slave machines (to two different locations). Is this a problem. The locations a local to each of the three machines.
I already read a similar posting on here but the solution (resetting all services and restarting on all machines) has had no effect.
Thanks in advance for any help.

HI, many of these kinds of issues are linked to Qmaster's use *of a NETWORK paths to its nodes*.
So in a perfect world you want to try and STOP queue master from looking outside you local lLAN (subnet) for the other macs. You can see most likely a load of queue master chatty whinging that it can find stuff on the network (console.app).
Anyways, here's a workaround that I do every time when transcoding with qmaster. I have my nodes connected via ethernet in an elcheapo GbE hub.
SIMPLY *turn off the AIRPORTS on all you macs*. If you are not using airports, then DISENGAGE the router paths of set up a new "system prefs/network/loation/ for "qmaster" that does NOT permit your network to go out to another high level network. (Make the network isolated or closed). I know many post houses that do his anyway.
THis will be a good start to islolatng your issues especially when clusters dont connect and they dont appear in COMPRESSOR and so on.
I hope Apple fixes this implementation in rumoured FCS3.
*PLAN B* - look at all the /var/logs for Qmaster instances and see what it is moaning about. Use the /applications/utilities/console.app
also make sure you have the SOURCE and TARGET file systems mounted on all nodes and specify to compressor in the prefs "never copy the source"..
Lots of other things to tweak.
AS alsways *search these forums* and you will get all the expertise from years and plenty of fixes and work arounds.
you're not alone!.
post your results.
w
HK

DFSr supported cluster configurations - replication between shared storage

I have a very specific configuration for DFSr that appears to be suffering severe performance issues when hosted on a cluster, as part of a DFS replication group.
My configuration:
3 Physical machines (blades) within a physical quadrant.
3 Physical machines (blades) hosted within a separate physical quadrant
Both quadrants are extremely well connected, local, 10GBit/s fibre.
There is local storage in each quadrant, no storage replication takes place.
The 3 machines in the first quadrant are MS clustered with shared storage LUNs on a 3PAR filer.
The 3 machines in the second quadrant are also clustered with shared storage, but on a separate 3PAR device.
8 shared LUNs are presented to the cluster in the first quadrant, and an identical storage layout is connected in the second quadrant. Each LUN has an associated HAFS application associated with it which can fail-over onto any machine in the local cluster.
DFS replication groups have been set up for each LUN and data is replicated from an "Active" cluster node entry point, to a "Passive" cluster node that provides no entry point to the data via DFSn and a Read-Only copy on it's shared cluster
storage.
For the sake of argument, assume that all HAFS application instances in the first quadrant are "Active" in a read/write configuration, and all "Passive" instances of the HAFS applications in the other quadrants are Read-Only.
This guide: http://blogs.technet.com/b/filecab/archive/2009/06/29/deploying-dfs-replication-on-a-windows-failover-cluster-part-i.aspx defines
how to add a clustered service to a replication group. It clearly shows using "Shared storage" for the cluster, which is common sense otherwise there effectively is no application fail-over possible and removes the entire point of using a resilient
cluster.
This article: http://technet.microsoft.com/en-us/library/cc773238(v=ws.10).aspx#BKMK_061 defines the following:
DFS Replication in Windows Server 2012 and Windows Server 2008 R2 includes the ability to add a failover cluster
as a member of a replication group. The DFS Replication service on versions of Windows prior to Windows Server 2008 R2
is not designed to coordinate with a failover cluster, and the service will not fail over to another node.
It then goes on to state, quite incredibly: DFS Replication does not support replicating files on Cluster Shared Volumes.
Stating quite simply that DFSr does not support Cluster Shared Volumes makes absolutely no sense at all after stating clusters
are supported in replication groups and a technet guide is provided to setup and configure this configuration. What possible use is a clustered HAFS solution that has no shared storage between the clustered nodes - none at all.
My question: I need some clarification, is the text meant to read "between" Clustered
Shared Volumes?
The storage configuration must to be shared in order to form a clustered service in the first place. What
we am seeing from experience is a serious degradation of
performance when attempting to replicate / write data between two clusters running a HAFS configuration, in a DFS replication group.
If for instance, as a test, local / logical storage is mounted to a physical machine the performance of a DFS replication group between the unshared, logical storage on the physical nodes is approaching 15k small files per minute on initial write and even high
for file amendments. When replicating between two nodes in a cluster, with shared clustered storage the solution manages a weak 2,500 files per minute on initial write and only 260 files per minute when attempting to update data / amend files.
By testing various configurations we have effectively ruled out the SAN, the storage, drivers, firmware, DFSr configuration, replication group configuration - the only factor left that makes any difference is replicating from shared clustered storage, to another
shared clustered storage LUN.
So in summary:
Logical Volume ---> Logical Volume = Fast
Logical Volume ---> Clustered Shared Volume = ??
Clusted Shared Volume ---> Clustered Shared Volume = Pitifully slow
Can anyone explain why this might be?
The guidance in the article is in clear conflict with all other evidence provided around DFSr and clustering, however it seems to lean towards why we may be seeing a real issue with replication performance.
Many thanks for your time and any help/replies that may be received.
Paul

Hello Shaon Shan,
I am also having the same scenario at one of my customer place.
We have two FileServers running on Hyper-V 2012 R2 as guest VM using Cluster Shared Volume. Even the data partition drive also a part of CSV.
It's really confusing whether the DFS replication on CSV are supported or not, then what would be consequence if using.
In my knowledge we have some customers they are using Hyper-V 2008 R2 and DFS is configured and running fine on CSV since more than 4 years without any issue.
Appreciate if you can please elaborate and explain in details about the limitations on using CSV.
Thanks in advance,
Abul

In-memory replication of http session is not working in BEA7 cluster

          Hi everyone,
          I have 3 managed servers in Bea7.0 SP4 in a cluster. The client requests are sent
          through apache web server. I have given cluster address as URL in httpd.conf of
          apache server which sends the client requests for dynamic pages such as JSPs and
          servlets to the weblogic cluster.
          Load balancing is working fine. I ensured this from the log files of all the 3
          servers. All the 3 servers are getting different client requests and thus load
          balancing is working.
          Now, I wanted to achieve Fail-over. I do not think that i should use proxy plug-in
          for this. I feel the cluster itself will handle fail-over provided i make the
          http session as memory replicated.
          I updated the weblogic.xml with the following entry :
          <session-descriptor>
          <param-name>PersistentStoreType</param-name>
          <param-value>replicated</param-value>
          </session-param>
          </session-descriptor>
          I guess this is sufficient to make the http session as cluster aware.
          But when I shutdown server1, the user connected to server1 will be kicked out
          of the session and come to login page through server2 or server3 which are running
          fine.
          Could anyone help me to achieve http session as cluster aware. Does it indicate
          that I have to go for WLS proxy – HttpClusterServlet to achieve fail over for
          http session ?
          BTW, for your info, i am using setAttribute() and getAttribute() while manipulating
          the session.
          thanks in advance.


          Hi Ryan,
          Thanks for ur valuable input.
          I can see failover working.
          But, I can not continue with the same session in my application.
          I printed session Ids before and after failover, I found both are different.
          I guess session replication is a responsibility of weblogic/apache plugin.
          If not please let me know which all settings I should do to make failover working?
          Thanks again.
          Plad
          "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
          >Plad,
          >
          >Are you trying to gracefully shut down the server? If you are then the
          >problem that you say you can't identify is simply the server's default
          >behavior which is to wait for all non-replicated sessions to be dropped
          >or
          >timed out before killing the process. Try forcing the shutdown: kill
          >-9 the
          >PID or CTRL-C if you started the server from the command line. You can
          >also
          >check the ``Ignore Sessions During Shutdown" checkbox under the server's
          >control tab in the admin console, this should allow you to shut down
          >gracefully without waiting for session timeout. BTW your sequence is
          >off
          >in #5 below, the replication doesn't occur upon failure, the replication
          >has
          >already happened once you created the session object on the first server,
          >I
          >think maybe you're confusing replication with failover.
          >
          >~RU
          >
          >"Plad" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi,
          >> I have 2 managed servers in a cluster.
          >>
          >> 1. I have got a DNS name configured which maps to these 2 managed server's
          >IP
          >> addresses.
          >> 2. I can browse my site using this DNS name.
          >> In HTTPD.conf I have :
          >>
          >> ServerName dev.a.b.net
          >>
          >> <IfModule mod_weblogic.c>
          >> WebLogicCluster 10.1.38.232:7023,10.1.34.51:7023
          >> MatchExpression *.*
          >> </IfModule>
          >>
          >> LoadModule weblogic_module modules/mod_wl_20.so
          >>
          >> 3. I have adeded session descriptor in weblogic.xml , also enabled
          >proxy
          >plugin
          >> in weblogic console.
          >>
          >> 4. I tested accessing my application using DNS url after shutting down
          >alternatively
          >> each manaed server. I can access application.
          >>
          >> 5. Now, problem comes when I access a managed server1 , keeping server2
          >down.
          >> I am able to access my application.
          >> Now, I start the server2.
          >> (Here I am supposing that replication should occur)
          >> Then I am shutting down server1.
          >> But, this time the server log shows me following:
          >>
          >>
          >> 9:58:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
          >non-replicated
          >> sessions after 2 minutes of initiating SUSPEND. Waiting for non-replicated
          >sessions
          >> to finish.
          >> 10:00:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
          >non-replicated
          >> sessions after 4 minutes of initiating SUSPEND. Waiting for non-replicated
          >sessions
          >> to finish.
          >>
          >> I am unable to make out where the problem is?
          >> Can it be a problem of Liecense? Is there any specialcluster liecense
          >for
          >weblogic8?
          >>
          >> Hoping to get replies.
          >> Thanx.
          >> Plad
          >>
          >> "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
          >> >See my reply to your first post, but I've also added a few comments
          >here.
          >> >
          >> >"jyothi" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> I guess someone from bea support team only can answer both your
          >question
          >> >and mine.
          >> >> As per my knowledge, we do not need to do any setup at Apache
          >side
          >> >regarding
          >> >> cluster other than mentioning cluster address as URL while
          >contacting
          >> >WLS
          >> >> from apache.
          >> >>
          >> >> I hope someone from Bea, will help us. I do not think that we
          >> >go for
          >> >WLS
          >> >> proxy plug-in using HttpClusterServlet for making session replication.
          >> > I
          >> >strongly
          >> >> feel that the cluster itself be able to manage the fail-over of
          >> >http
          >> >sessions
          >> >> provided we put the entry "PersistentStoreType" in weblogic.xml
          >> >regarding
          >> >> the session replication.
          >> >>
          >> >
          >> >The cluster does handle the management of Sessions. The clustered
          >> >applications still create the Session objects and the cluster manages
          >> >them
          >> >as per your deployment descriptor settings (replicated, JDBC, File)
          >however
          >> >the proxy has to be aware of which server the client has an affinity
          >> >for
          >> >(only with replicated sessions) and it does that by reading a cookie
          >> >passed
          >> >back from the server that handled the initial request and created
          >the
          >> >primary session object. The proxy has a list of both the primary
          >and
          >> >secondary server locations from this cookie that it can use to failover
          >> >the
          >> >request if the primary server fails. Clusters _DO NOT_ failover nor
          >> >do they
          >> >load balance, that's the job of your proxy, whether you're using the
          >> >HTTPClusterServlet, WLS Plug-in or a more sophisticated hardware load
          >> >balancer like Big IPs F5
          >> >
          >> >> jyothi
          >> >>
          >> >
          >> >~RU
          >> >
          >> >
          >>
          >
          >

10.5 machine cannot send to cluster

I have a cluster set up that works fine when other computers running OS 10.4 submit to it. However, there is only one machine that is running 10.5 on the network and whenever I try to send a job to the cluster with that machine it just gets stuck on Copying Source File. I don't know why this happens - the computer has access to the cluster storage, and the Compressor preferences are set to Copy as Needed, and I have tried the Copy at Submission (High) checkbox but it still does the same thing. I have tried exporting to Compressor directly from FCP, as well as sending self-contained files to the cluster as well. Same problem either way.
Cluster details:
Node 1 - G5 Quad-Core @ 2.5 GHz, OS 10.4.11 FCP Studio 1, Compressor 2.3.1
Node 2 - G5 Quad-Core @ 2.5 GHz, OS 10.4.11 FCP Studio 1, Compressor 2.3.1
Node 3 - Mac Pro 8 Core @ 3 GHz, OS 10.5.5 FCP Studio 1, Compressor 2.3.1
Cluster Controller - Xserve Dual Core @ 2.3 GHz, OS 10.4.11 Server, Only Qmaster Node package is installed
Computer trying to submit with:
OS 10.5.5 FCP Studio 1, Compressor 2.3.1
I am stumped as to why this isn't working. I have tried all the usual tricks: restarting services on the nodes, rebuilt the cluster a couple of times, permissions seem to be correct on the submitting machine, etc. Any thoughts or ideas on why this is occurring would be greatly appreciated. Thanks

Figured it out. In my System Preferences > Apple Qmaster > Advanced I had to select which interface to use. It only shows one interface in the drop-down, but ifconfig shows several others being used by VMware Fusion for my virtual machines. Console logs showed that qmaster was trying to use one of the VM interfaces rather than my main ethernet connection, which was causing these problems. All good now.

SOA 11.1.1.5 two Node Cluster BAM not starting on the second Machine

Hi,
I have installed Oracle SOA 11.1.1.5 in a 2 Node Cluster. Both SOA Managed Servers are coming up fine. BAM Managed Server installed on the primary HOST also comes up fine. But my second BAM Managed Server is not starting. I don't see anything in the logs and on the Console the status is showing as Starting but it never starts. I can access the BAM Console for the one installed on the primary HOST but when giving the URL for the second HOST it doesn't come up as the I don't see an option the server is running.
I have 2 machines for this cluster setup
On machine one with IP Address: *192.168.2.2* all below servers come-up fine
Admin
BAM1
SOA1
On machine two with IP Address: *192.168.3.3* have the below servers and only the SOA is coming up fine BAM not starting
BAM2 not starting
SOA2 coming up fine also
After giving user/password this is what I see in the terminal window and it never moves looks like getting stuck:
<Mar 8, 2012 12:31:40 PM EST> <Info> <Security> <BEA-090065> <Getting boot ident
ity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Mar 8, 2012 12:32:58 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Mar 8, 2012 12:33:01 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Mar 8, 2012 12:33:01 PM EST> <Info> <WorkManager> <BEA-002900> <Initializing se
lf-tuning thread pool>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320400> <The log fi
le C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BA
M2.log will be rotated. Reopen the log file if tailing has stopped. This can hap
pen on some platforms like Windows.>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320401> <The log fi
le has been rotated to C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\
servers\BAM2\logs\BAM2.log00001. Log messages will continue to be logged in C:\o
racle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BAM2.log.
>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\
logs\BAM2.log is opened. All server side log events will be written to this file
.>
<Mar 8, 2012 12:33:09 PM EST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STANDBY>
<Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Mar 8, 2012 12:33:26 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional
package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.applcore.
model, Specification-Version: 0.1, Implementation-Version: 11.1.1.0.0, reference
d from: C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tm
p\_WL_user\usermessagingserver\wehyzl]. Make sure the referenced optional packag
e has been deployed as a library.>
<Mar 8, 2012 12:33:28 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageRe
ceiverBean(Application: usermessagingserver, EJBComponent: sdpmessagingengine.ja
r), the value for the activation config property 'connectionFactoryJNDIName' wil
l be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFacto
ry';>
<Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-012035> <The Remote interface
method: 'public abstract void oracle.ucs.userprefs.DefaultFactStore.setBusiness
FactValue(java.lang.String,java.lang.String,java.lang.Object) throws oracle.ucs.
userprefs.UserPrefsException' in EJB 'UserPrefsDefaultFactStore' contains a para
meter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Use
rPrefsDefaultFactStore' has call-by-reference set to false, this parameter is no
t Serializable and hence will be passed by reference. A parameter can be passed
using call-by-value only if the parameter type is Serializable.>
<Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageDi
spatcherBean(Application: usermessagingserver, EJBComponent: sdpmessagingclient-
ejb-parlayx.jar), the value for the activation config property 'connectionFactor
yJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueC
onnectionFactory';>
<Mar 8, 2012 12:33:37 PM EST> <Warning> <Connector> <BEA-190110> <Resource Adapt
er is calling BootstrapContext.createTimer() and allocating a Timer Thread that
is not managed by WebLogic Server. This may adversely impact the performance/ope
ration of WebLogic Server.>
<Mar 8, 2012 12:33:37 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB DriverDis
patcherBean(Application: usermessagingdriver-email, EJBComponent: sdpmessagingdr
iver-dispatcher-ejb.jar), the value for the activation config property 'connecti
onFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDP
M/QueueConnectionFactory';>
<Mar 8, 2012 12:33:43 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-adc-ejb.jar/META-INF/ejb-jar.xml. A version attribut
e is required, but this version of the Weblogic Server will assume that the JEE5
is used. Future versions of the Weblogic Server will reject descriptors that do
not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-ems-ejb.jar/META-INF/ejb-jar.xml. A version attribut
e is required, but this version of the Weblogic Server will assume that the JEE5
is used. Future versions of the Weblogic Server will reject descriptors that do
not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-eventengine-ejb.jar/META-INF/ejb-jar.xml. A version
attribute is required, but this version of the Weblogic Server will assume that
the JEE5 is used. Future versions of the Weblogic Server will reject descriptors
that do not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-reportcache-ejb.jar/META-INF/ejb-jar.xml. A version
attribute is required, but this version of the Weblogic Server will assume that
the JEE5 is used. Future versions of the Weblogic Server will reject descriptors
that do not specify the JEE version.>
<Mar 8, 2012 12:33:52 PM EST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-
26024> <Registration of driver Email-Driver did not complete; will retry periodi
cally until messaging server responds.>This is what I see in the diagnostic log
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> And this is what I see in the log
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048125> <BEA-149059> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014021> <The EJB 'BamAdcServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-adc-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014022> <******** oracle.bam.adc.ejb.BamAdcServerRemote is bound with JNDI name:BamAdcServerBean#oracle.bam.adc.ejb.BamAdcServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-adc-ejb_jarBamAdcServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149060> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149059> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> Any help is appreciated.
Thanks

Hi,
I have installed Oracle SOA 11.1.1.5 in a 2 Node Cluster. Both SOA Managed Servers are coming up fine. BAM Managed Server installed on the primary HOST also comes up fine. But my second BAM Managed Server is not starting. I don't see anything in the logs and on the Console the status is showing as Starting but it never starts. I can access the BAM Console for the one installed on the primary HOST but when giving the URL for the second HOST it doesn't come up as the I don't see an option the server is running.
I have 2 machines for this cluster setup
On machine one with IP Address: *192.168.2.2* all below servers come-up fine
Admin
BAM1
SOA1
On machine two with IP Address: *192.168.3.3* have the below servers and only the SOA is coming up fine BAM not starting
BAM2 not starting
SOA2 coming up fine also
After giving user/password this is what I see in the terminal window and it never moves looks like getting stuck:
<Mar 8, 2012 12:31:40 PM EST> <Info> <Security> <BEA-090065> <Getting boot ident
ity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Mar 8, 2012 12:32:58 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<Mar 8, 2012 12:33:01 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Mar 8, 2012 12:33:01 PM EST> <Info> <WorkManager> <BEA-002900> <Initializing se
lf-tuning thread pool>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320400> <The log fi
le C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BA
M2.log will be rotated. Reopen the log file if tailing has stopped. This can hap
pen on some platforms like Windows.>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <LoggingService> <BEA-320401> <The log fi
le has been rotated to C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\
servers\BAM2\logs\BAM2.log00001. Log messages will continue to be logged in C:\o
racle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\logs\BAM2.log.
>
<Mar 8, 2012 12:33:01 PM EST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\
logs\BAM2.log is opened. All server side log events will be written to this file
.>
<Mar 8, 2012 12:33:09 PM EST> <Notice> <Security> <BEA-090082> <Security initial
izing using security realm myrealm.>
<Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STANDBY>
<Mar 8, 2012 12:33:15 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Mar 8, 2012 12:33:26 PM EST> <Warning> <J2EE> <BEA-160140> <Unresolved optional
package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.applcore.
model, Specification-Version: 0.1, Implementation-Version: 11.1.1.0.0, reference
d from: C:\oracle\Middleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tm
p\_WL_user\usermessagingserver\wehyzl]. Make sure the referenced optional packag
e has been deployed as a library.>
<Mar 8, 2012 12:33:28 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageRe
ceiverBean(Application: usermessagingserver, EJBComponent: sdpmessagingengine.ja
r), the value for the activation config property 'connectionFactoryJNDIName' wil
l be ignored since it is overridden with the value 'OraSDPM/QueueConnectionFacto
ry';>
<Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-012035> <The Remote interface
method: 'public abstract void oracle.ucs.userprefs.DefaultFactStore.setBusiness
FactValue(java.lang.String,java.lang.String,java.lang.Object) throws oracle.ucs.
userprefs.UserPrefsException' in EJB 'UserPrefsDefaultFactStore' contains a para
meter of type: 'java.lang.Object' which is not Serializable. Though the EJB 'Use
rPrefsDefaultFactStore' has call-by-reference set to false, this parameter is no
t Serializable and hence will be passed by reference. A parameter can be passed
using call-by-value only if the parameter type is Serializable.>
<Mar 8, 2012 12:33:32 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB MessageDi
spatcherBean(Application: usermessagingserver, EJBComponent: sdpmessagingclient-
ejb-parlayx.jar), the value for the activation config property 'connectionFactor
yJNDIName' will be ignored since it is overridden with the value 'OraSDPM/QueueC
onnectionFactory';>
<Mar 8, 2012 12:33:37 PM EST> <Warning> <Connector> <BEA-190110> <Resource Adapt
er is calling BootstrapContext.createTimer() and allocating a Timer Thread that
is not managed by WebLogic Server. This may adversely impact the performance/ope
ration of WebLogic Server.>
<Mar 8, 2012 12:33:37 PM EST> <Warning> <EJB> <BEA-015036> <In the EJB DriverDis
patcherBean(Application: usermessagingdriver-email, EJBComponent: sdpmessagingdr
iver-dispatcher-ejb.jar), the value for the activation config property 'connecti
onFactoryJNDIName' will be ignored since it is overridden with the value 'OraSDP
M/QueueConnectionFactory';>
<Mar 8, 2012 12:33:43 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-adc-ejb.jar/META-INF/ejb-jar.xml. A version attribut
e is required, but this version of the Weblogic Server will assume that the JEE5
is used. Future versions of the Weblogic Server will reject descriptors that do
not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-ems-ejb.jar/META-INF/ejb-jar.xml. A version attribut
e is required, but this version of the Weblogic Server will assume that the JEE5
is used. Future versions of the Weblogic Server will reject descriptors that do
not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-eventengine-ejb.jar/META-INF/ejb-jar.xml. A version
attribute is required, but this version of the Weblogic Server will assume that
the JEE5 is used. Future versions of the Weblogic Server will reject descriptors
that do not specify the JEE version.>
<Mar 8, 2012 12:33:44 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element ejb-jar in the deployment descriptor in C:\oracle\M
iddleware\user_projects\domains\EP_SOA_DOMAIN\servers\BAM2\tmp\_WL_user\oracle-b
am_11.1.1\ert5kb\oracle-bam-reportcache-ejb.jar/META-INF/ejb-jar.xml. A version
attribute is required, but this version of the Weblogic Server will assume that
the JEE5 is used. Future versions of the Weblogic Server will reject descriptors
that do not specify the JEE version.>
<Mar 8, 2012 12:33:52 PM EST> <Warning> <oracle.sdp.messaging.driver.base> <SDP-
26024> <Registration of driver Email-Driver did not complete; will retry periodi
cally until messaging server responds.>This is what I see in the diagnostic log
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> And this is what I see in the log
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048125> <BEA-149059> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014021> <The EJB 'BamAdcServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-adc-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-014022> <******** oracle.bam.adc.ejb.BamAdcServerRemote is bound with JNDI name:BamAdcServerBean#oracle.bam.adc.ejb.BamAdcServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-adc-ejb_jarBamAdcServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149060> <Module oracle-bam-adc-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048359> <BEA-149059> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014021> <The EJB 'EMSServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-ems-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-014022> <******** oracle.bam.ems.ejb.EMSServerRemote is bound with JNDI name:EMSServerBean#oracle.bam.ems.ejb.EMSServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-ems-ejb_jarEMSServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149060> <Module oracle-bam-ems-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048390> <BEA-149059> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014021> <The EJB 'EventEngineServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-eventengine-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-014022> <******** oracle.bam.eventengine.ejb.EventEngineServerRemote is bound with JNDI name:EventEngineServerBean#oracle.bam.eventengine.ejb.EventEngineServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-eventengine-ejb_jarEventEngineServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149060> <Module oracle-bam-eventengine-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048437> <BEA-149059> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014021> <The EJB 'ReportCacheServerBean(Application: oracle-bam#11.1.1, EJBComponent: oracle-bam-reportcache-ejb.jar)' has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-014022> <******** oracle.bam.reportcache.ejb.ReportCacheServerRemote is bound with JNDI name:ReportCacheServerBean#oracle.bam.reportcache.ejb.ReportCacheServerRemote ********>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-010009> <EJB Deployed EJB with JNDI name oracle-bam#11_1_1oracle-bam-reportcache-ejb_jarReportCacheServerBean_Home.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149060> <Module oracle-bam-reportcache-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048484> <BEA-149059> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name StatusListenerEJB.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module oracle-bam-statuslistener-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149059> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] is transitioning from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010009> <EJB Deployed EJB with JNDI name MessagingClientBAM.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <EJB> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-010223> <EJB Deployed Message Driven Bean: MessageDispatcherBean>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Deployer> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048500> <BEA-149060> <Module sdpmessagingclient-ejb.jar of application oracle-bam [Version=11.1.1] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server BAM2.>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001516> <Connection Pool "BAMDataSource" connected to Database: "Oracle", Version: "Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <JDBC> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-001517> <Connection Pool "BAMDataSource" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Mar 8, 2012 12:34:08 PM EST> <Info> <Common> <humzalpt> <BAM2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <> <0000JNnNotlFg4WFLzrI8A1FMEpP000001> <1331228048859> <BEA-000628> <Created "1" resources for pool "BAMDataSource", out of which "1" are available and "0" are unavailable.> Any help is appreciated.
Thanks

Can't get remote cluster machine to encode video - getting 'Media Server application unexpectedly quit'

Hi
Using Compressor 4 / Apple QuarterMaster admin etc, I have set up a Cluster and it works well to Share > Export Using Compressor Settings. That took some doing, and I'm happy that it works.
If I do all my processing in the foreground, or alternatively in the background on my FCPX computer, ie without running or using any cluster in the background, it all goes well. Quick, error free.
If I activate the cluster and only put my local machine's compressor services into it, and then send my compressor batch to the cluster, it works perfectly well. But that defeats the point of having a cluster. I want the remote machine to do all the work so my local machine doesn't slow down.
Unfortunately, if I add the remote machine's services into the cluster, the encoding always fails with 'Media Server application unexpectedly quit' in the error log. I know that the cluster is distributing segments of the file to the remote machine - this can be seen in the Share Monitor, but they never get processed and sit there waiting until I get the error message.
The remote machine is a modern 4G core 2 duo MacBook. It's never been used for this before. It has Compressor 4 and the Pro Apps Update installed and both appear to work. Both machines are running 10.6.8. The remote machine has Compressor services initialised in Apple QMaster sharing. The QMasterAdmin sees these services. They are accessible over Bonjour and appear in the Cluster. Compressor services from both the local and the remote machine are configured exactly the same way. The same QT codecs exist on both machines. I've restarted, shift-restarted, etc etc.
So I am at a loss here. The remote machine just won't compress anything it is sent.
Any ideas? Must both have FCPX installed?
Anyone actually got a remote machine in a cluster to work with Compressor 4? I can't figure it out.
Chris.

OK... finally sorted it out.
It's a bug, as far as I can tell.
Any job entered directly into Compressor 4 in the normal Compressor manner will be successfully rendered by any working cluster from any machine that can access the cluster. That's good. It means that the underlying distributed processing model works well.
HOWEVER - any job forwarded to a Compressor 4 cluster that includes non-local compressor services (ie compressor services not resident on the same machine), using Share > Export Using Compressor Settings direct from FCPX will fail.
To confirm this bug, I made a cluster on a remote machine. It was a dual core machine, so I enabled 2 compressor services on that machine, and that's all the cluster was. Simple.
I then manually entered a video file (ProRess 422 720p) into Compressor on the remote machine. I did this by physically setting up new job using the compressor user interface. A bog standard ProRes422 720p file rendered fine this way on the remote machine. As did anything else I gave it. Good.
Then on my main machine, I opened Compressor and made a job based on the same file and settings, and sent it to the remote machine's cluster. No problem at all! Great!
So now I know that both Compressor versions, and the clustering model, are working fine. In fact I can send all sorts of files to the cluster, from any other version of compressor, and have them processed on the remote machine, and get the result back on my desktop later on. Excellent.
But, if I try put this same file into a FMPX timeline, and go Share > Export Using Compressor Settings.... and select a cluster with remote (non-local) compressor services, it does not work. Rendering the video segments on the remote machine times out and fails, every time. It doesn't matter what file format I use, it just fails.
So it's a bug.
From what I can tell, Final Cut Pro X somehow messes up the Share > Export Using Compressor settings where the cluster includes non-local compressor services, causing all jobs to fail. The same Share > Export Using Compressor Settings will work quite happily if all the services on the cluster are on the same machine as FCPX, or if the job is sent to This Computer in the background. But any attempt to send files to a cluster using any remote services will fail.
I hope this saves some people from wasting as much time as I have!
One workaround is to export to ProRes then put this file manually into Compressor, sending the job to the remote cluster. This is a two step process with a large intermediary ProRes file. If one goes Export as QuickTime movie, generating the intermediary file prevents further FCPX work being done.
To get the intermediary in the background one could use Share > Export Using Compressor Settings via either This Computer, or to a cluster using only local services. Then once complete, manually add it to a compressor job.
So this is a FCPX bug as far as I can tell.
Chris.

Replication in a Cluster of 2 machines

Similar Messages

Maybe you are looking for