Cloning BAM/SOA enviroment

I am developing a BAM solution to a client using BAM 11.1.1.3 build 8533.
I started using version 11.1.1.4, in my development environment, and before to deploy at client's homologation environment, I tried to deploy in my own test environment, with version 11.1.1.3, in a VM hosted in Amazon servers.
After import the xml files generated with icommand, the dashboards are displayed normally, but when i try to edit them, a problem occurs.
The Properties tabs are shown normally, but the Data tabs are shown without text, blank (different of shown on http://download.oracle.com/docs/cd/E16764_01/integration.1111/e10230/img/bam_as_chart_general.gif), and are not selectable. So I cannot to change view's data informations, like group by, calculated fields, and so on.
Is there a way to configure BAM/SOA to ensure full compatibility between the two environments?
This can be a problem that is not of configuration?
Thanks.
Luciano

OK. So what version is the other server?
You can check if the second server is using the correct version of jdk . It isn't using JROCKIT right?
Normally it is the jdk that is not compatible and I do know that we saw some issues on jrockit 1.6.20 during testing.
I do not believe there is a specific file that you can refer to .
There are a few other things that were noted in the release notes that apply to previous versions of BAM as well as IE so take a look
http://download.oracle.com/docs/cd/E17904_01/doc.1111/e14770/bam.htm#CFHCEJAD
section 21.1.5 --21.1.7

Similar Messages

Cloning the Retek Enviroment

Hi Gents
I want to clone our PROD environment, so please guide me and provide em any documents available
Module to be cloned:
Database: 10g
Application: RMS, RPM, SIM, ReIM,RWMS, RA
Waiting your help
Regards
[email protected]

I don't know what specific documents might be available, but I suggest starting here: http://www.oracle.com/retek/index.html

SOA Suite on WLS - backup and cloning strategy

Hello everybody.
Is there any best practices for implementing backups and cloning for SOA Suite instances deployed on WLS 9.2 ?

It has been a long time since I looked at this, try this location.
BEA_HOME\user_projects\domains\SOADomain\servers\OracleSOAServer\logs\OracleSOAServer.log
The path maybe slightly differerent for you depending on some of the parameters you set at install time.
From memory I think you need to increase logging levels from the admin console but I'm not 100%
cheers
James

Pre-Built EBS Analytics with BAM and EBS adapters on FM

Are there any pre-built business analytics dashboards/ reports installable in BAM SOA 11g for Oracle EBS 11.5.10?
If so, where do I download and what other components are required to publish these?
Thanks
Edited by: user6739500 on May 21, 2010 3:08 PM

Hi there
I have a Technote that shows how the information can be published from EBS to BAM. In addition you could create an end to end visibility across the products e.g. B2B - BPEL - EBS - Financials etc by raising the events to BAM .
There is no out of the box dashboards available today. However, i have a number of customers who are doing this use case by themselves or through some SI/Oracle consulting.
can we contact you offline to discuss your requirement?
http://www.oracle.com/technology/products/integration/bam/11g/technotes11g/whitepaperBAM_E-BusinessSuiteIntegration.pdf
There are certified adapters available for EBS to FM as well.
Regards
Payal
Edited by: PayalS on May 21, 2010 4:25 PM

SOA 11.1.1.5 install got can't write cache file

Hi,
I installed 2 node cluster of SOA 11.1.1.5 on linux and during domain configuration I got errors i.e.
**sys-package-mgr: can't write cache file for**
Installation was done and all the servers start/stop fine am able to deploy the processes, am able to access all the urls fine everything coming up fine BAM, SOA, OSB etc . Just wondering if the error above have any effect on the installation or any piece that might not work. As I have already did the installation and ignored those errors above so just wanted to see if anything I need to look for.
Thanks

Hi,
It's a cluster install and took sometime to do the full install so it will be a pain to re-install everything over. Currently have tested the processes and seems to be working fine.
Also I don't find
/var/tmp/wlstTemp
I do see wlstTemp appended with linux users who did Oracle SOA install.
Also in-future when creating a new environment besides the above chmod 777 on /var/tmp/wlstTemp is there any parameter we can supply when running config.sh. I read some where that in-order to get by these errors at the time of domain creation we can also pass some parameter.
Thanks

Installation of 11g SOA Suite

Hello All,
I have installed the
ORacle 11g DB
RCU to create schema
Oracle 11g SOA suite
Two Domains for BAM and SOA suite (without) selecting the Admin Option as referred in QUick install guide.
I have query on these two weblogic domains as both of them have the same port 7001, how can I run both the domains ?
Have you found the .xml files as mentioned in page no. 49. of the guide ?

Hello Baskar,
I did refer Quick installation while installing and followed the steps, hence created two domains with the understanding that BAM component probably needs a separate domain (BEA) as it could be bit heavy weight component.
I believe if BAM, SOA and EM can run in a single domain, even now it is NOT too late, there is a option to configure domain and I will use the SOA domain create to check the BAM component also into it and start only this domain. But the quick installation guide seems to have a conflicting guidance steps.
http://download.oracle.com/docs/cd/E12839_01/install.1111/e14318/qisoa.htm
Refer the Installation Guide and the steps for configuring BAM and configuring SOA, they had been given in two step activity with different domains.

WebLogic domain spread across two machines

Hi All,
I have a weblogic domain that spreads across two machines. First machine hosts the Admin server, (BAM , SOA) managed servers and the second machine hosts the (APPs and FIN) managed servers. As you can see the managed servers hosts different applications and not related with clustering. I want to know in such a setup do we need to have separate weblogic installation on both first and second machines or just have WebLogic installation on the first machine and have the second machine reference the first's WL installation.
What's the best practice.
Regards

I mean for a domain spread over two machines, I need to have weblogic installation on both machines and not just the one running admin server. I read somewhere WebLogic installations have 1 to N relation with domains. Seems like for a domain spread across two machines, two WL installations and two licences. Am I right?

How to configure Node manager on Linux on ssl port

Hi,
I have installed SOA BPM 11.1.1.3 on linux with ssl enabled. I am trying to configure Node Manager but it's not working.
Here are the steps I did to configure.
1. Created a machine
2. Added managed servers to the machine i.e. soa,bam
3. Enroll domain using nmEnroll using
cd $BEA_HOME/user_projects/domains/<domain_name>/bin/
. setDomainEnv.sh
java weblogic.WLST
wls> connect(’weblogic’,'weblogic1’, ‘t3://mymachine.mydomain:7001’)
wls> nmEnroll(’$BEA_HOME/user_projects/domains/<domain_name>’, ‘$BEA_HOME/wlserver_<version>/common/nodemanager’)
here 7001 is the admin server non-ssl port but when I try 7002 ssl port it doesn't connect. But I need to enroll it on ssl port as I have ssl enabled.
4. reset the node manager user/password same as weblogic console
5. started the node manager using $WL_HOME\server\bin\startNodeManager.sh
But when I log back into console and try to start my manage server it gives the following error
SEVERE: java.io.FileNotFoundException: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/./config/jps-config.xml (No such file or directory)
<Aug 6, 2010 5:30:16 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.I did not add my Admin server to be part of the machine.
Any help if I am missing anything or doing anything wrong.
Thanks

Hi,
Do I need to add Admin Server also part of the Machine where I added bam,soa servers. I tried again following the steps but gets the below error again. Appreciate if someone can list the steps as the docs are a bit vague:
<Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh >
Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
INFO: Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh
<Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Working directory is '/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain'>
Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
'/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/servers/bam_server1/logs/bam_server1.out'
<Aug 6, 2010 6:14:02 PM> <INFO> <wcbpm_domain> <bam_server1> <Server failed during startup so will not be restarted>
Aug 6, 2010 6:14:02 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Aug 6, 2010 6:14:02 PM> <WARNING> <Exception while starting server 'bam_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
        at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
        at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
        at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
        at weblogic.nodemanager.server.Handler.run(Handler.java:70)
        at java.lang.Thread.run(Thread.java:619)
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
Unknown option or illegal argument: -XX:+UseParallelGC.
Please check for incorrect spelling or review documentation of startup options.
Could not create the Java virtual machine.
<Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <Waiting for the process to die: 590>
<Aug 6, 2010 6:14:02 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>Don't know if I hve missed any steps in node manager configuration.
Thanks

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

I have SOA suite and Jdeveloper, what do i need more for BAM ?

Hi
Thank you for reading my post
I have installed both soa suite and latest version of jdeveloper
I can see BAM node under connections node but i do not know how should i add the bam server connection.
so my questions are :
-should i install the bam server seperately or it come with ORACLE SOA suite?
-if i should install seperately, where is hould find it?
-if it is inside the SOA suite How i can activate it and add it to my Jdeveloper?
thanks

\BAM is part of SOA suite, but BAM should be installed separately, Go to http://www.oracle.com/technology/products/integration/bam/index.html for details.

SOA 11g: Intergation with BAM 11g failed with ThreadPool has stuck threads

Hi,
I have installed BAM and SOA server on local host. Now while integrating BAM with BAMAdapter it's going into long running state and finally failing with below error.
<Notice> <Diagnostics> <mars.as.local> <soa_server1> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <c82d73b0a2a7776f:37a0afd7:130d1278d97:-8000-0000000000028a7f> <1309264042380> <BEA-320068> <Watch 'StuckThread' with severity 'Notice' on server 'soa_server1' has triggered at Jun 28, 2011 1:27:22 PM BST. Notification details:
WatchRuleType: Log
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-000337') OR (MSGID = 'BEA-000337'))
WatchData: DATE = Jun 28, 2011 1:27:22 PM BST SERVER = soa_server1 MESSAGE = *[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "638" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@16e92176[*
*POST /soa-infra/services/default/BAMInsert/bpelprocess1_client_ep HTTP/1.1*
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: Oracle HTTPClient Version 10h
SOAPAction: "process"
Accept-Encoding: gzip, x-gzip, compress, x-compress
ECID-Context: 1.c82d73b0a2a7776f:2ced6156:130d1186ef6:-8000-00000000000046b2;kYjE0ZJOoOTLkKPOoLRKlSODoITT_G
Content-type: text/xml; charset=UTF-8
Content-Length: 270
*]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:*
*Thread-139 "[STUCK] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, sleeping, priority=1, DAEMON> {*
*java.lang.Thread.sleep(Thread.java:???)*
oracle.bam.common.remoting.BamEjbClient.getSession(BamEjbClient.java:973)
oracle.bam.common.remoting.BamEjbClient.getADCSession(BamEjbClient.java:350)
oracle.bam.adc.api.util.Context.<init>(Context.java:270)
oracle.bam.adapter.adc.CachedConnection.<init>(CachedConnection.java:134)
oracle.bam.adapter.adc.ADCManagedConnectionFactory.getCachedConnection(ADCManagedConnectionFactory.java:490)
^-- Holding lock: java.lang.String@13416588[fat lock]
What could be root cause of this? Can anyone please help to find the solution?
Even though both servers on same host why BAM connection is getting to much time and Putting server in warning state like :
+[STUCK] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'+
*Do i need to modify any config file at Admin or BAM level? if Yes, what parameter Do i need to change?*
Please guide.
Thanks,
Sagar.

Further Updates on this :
I further debugged and found out few more things. This might help.
In Weblogic Admin console Home > Summary of Deployments >oracle-bam(11.1.1)
MDB application oracle-bam is NOT connected to messaging system with below error.
EJBs
MessageDispatcherBean - Error java.lang.IllegalArgumentException: Getting Deployment configuration...
connectionFactoryJNDIName - Red Cross with warning
destinationJNDIName - Red Cross with warning
resourceAdapterJNDIName - Red Cross with warning
Modules
Also please check out another similar thread and please update.
BAMAdapter Issue : java.rmi.ConnectException: Destination unreachable;
Thanks,
Sagar

Cloning SOA Suite 11.1.1.2.0

Hello,
Please let me know if you have any pointer to cloning procedure of SOA Suite 11.1.1.2.0, Oracle documentation for this version is not complete.
Any help that you could provide on this will be highly appreciated.
Thansk!

Hello,
Please let me know if you have any pointer to cloning procedure of SOA Suite 11.1.1.2.0, Oracle documentation for this version is not complete.
Any help that you could provide on this will be highly appreciated.
Thansk!

BAM Doesn't exist in SOA 11.1.1.5.0 Installer

Hi
I'm installing Oracle SOA Suite 11.1.1.5.0. I've extracted two downloaded zip files (ofm_osb_generic_11.1.1.5.0_disk1_1of1 and ofm_osb_generic_11.1.1.5.0_disk1_1of2). The progress continues normally until it reaches "*Copying files for: Oracle BAM 11.1.1.5.0*". It asks me to insert Disk 3 of Oracle SOA Suite. I've also changed the "disk.label" file in stage folders of second zip file, too looks like Disk 3, but the error still exists.
It seems that it's looking for data files of BAM. It's searching for "*stage/Components/oracle.integration.bam/11.1.1.5.0/1/DataFiles/filegroup3.jar*". I've checked this folder. There is no directory named "DataFiles" in this path. It seems that BAM doesn't exist in 11.1.1.5.0 distribution!
Is there anything that I've missed during installation?
Edited by: user2169403 on Jun 4, 2011 2:34 AM
Sorry!
Those files were from two different product :D. That was my mistake. The first one was from osb and the second one was from ofm.

Hey Man, I am running into exact same issue. I am getting a dialog box for inserting disk number 3 for BAM and I am also using the same version as you are. Can you please explain in little detail on how you solved this? I could not understand your updated response on you how you fixed it.
Thanks,
ora_guy

Getting BEA-170011 error in soa, osb, bam servers

Dear Friends,
i am getting below error in the soa, osb and bam servers,
<BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
please tell me how to fix this.
Thanks & Regards,
Pavan.

I am able to telnet the IP and port of this webservice from my machineThat confirms the webservice is up, to confirm you have connectivity from osb to the webservice you need to telnet from the host that's running osb to the IP and port of that webservice...
Do you have a proxy configured on start up properties of the osb? Look for things like -Dhttp.proxyHost=192.4.229.194 -Dhttp.proxyPort=80 into the setDomainEnv.sh(cmd) script...
If the server is internal, you may need to add id to the non-proxy hosts...
Cheers,
Vlad

SOA - Database Adapter push data to BAM

I would like to create an SOA application to pull data from an Oracle Database and push it Oracle BAM.
In the past I've done this by using the "Polling for new or changed records in a table" from the Database Adapter to pull new data from the database. However, I wish to know if it is possible for me to somehow configure the adapter to execute a query on the database, grab the results and push them through the Mediator and onto the BAM adapter.
The main point here is that there is no Table or View on the database to supply the data. The data is created dynamically as a query result when / if the database adapter runs the query on the database.
This needs to happen periodically (as with the polling for changes method).
Is this possible?

Hi
I believe the below option will help you.
1.Create a BPEL process and inside that use the DB adapter to execute the query and fetch the data and push the same to BAM through the BAM Adapter.
2.Schedule the BPEL process with Quartz Scheduler(default option provided by Oracle BPEL) to run periodically as per your requirement.
Regards
Albin I

Cloning BAM/SOA enviroment

Similar Messages

Maybe you are looking for