BAM Server Connection

Hi
I have installed BAM on Windows xp and all the services are running and i am able to open BAM start up page.
Through BPEL i need to access BAM.
For that i tried creating BAM server connection,but i couldnot succeed
for hostname i used the Machine name where my BAM services are running.
Port is 80
and user name is domain\username(which i used during the installation of BAM)
PWD : installation PWD
domain :Domain.
i tried with above ,but the connection failed.
Can you pls let me know where i went wrong.
Do i have to install BAM client on all the machines from where i access BAM server ????
Thanks and Regards
Ashwini

Hello Ashwini. You donot need to install "anything" on clients. BAM is completely browser driven and needs only server install. For BPEL connection, you have to be sure about the BPEL server and JDev UI versions. All components (BPEL, JDev,BAM) have to be 10.1.3
Alternate -debug- try DomainName in CAPS only and also try username 'without' domain name

Similar Messages

  • Unable to setup BAM server connections from JDeveloper

    Hi
    I have installed BAM on XP .I'm able to access BAM from frontend and all services are up and running. When i tried to set up a BAM server connection from Jdeveloper , it failed.
    How do i get the values for the following parameters..
    Host Name:
    Port Number: 80
    User Name:
    Password:
    Domain Name:
    Your help in this regard is highly appreciated.
    Thanks
    Laj Abraham

    Host name will be the host where BAM is installed
    User name will be the user name of a user granted access to BAM
    Domain name will be that user's domain
    Password will be the user's password
    By default the user you used to install BAM is automatically granted acces, you can use the administrator page in BAM to add additional users

  • How to Create an Oracle BAM Server Connection?

    I m following the steps at the end of this post to create the connection but at the end I m getting this message from JDev:
    {Unable to write to
    /C:/JDeveloper/mywork/Application1/.adf/META-INF/connections.xml
    because it is a read-only. Either make it writable or allow it to be made writable through source control.}
    it creates the directory C:/JDeveloper/mywork/Application1/.adf/META-INF/ with only a adf-config.xml file but NOT the connections.xml any one knows what is wrong?
    Bellow is the stpes I m following. Its exactly what is written at the Oracle Fusion Middleware Developer´s guide for Oracle SOA Suite 11g Release 1(11.1.1) E10224-01
    To create an Oracle BAM connection:
    1. Select New from the File main menu in Oracle JDeveloper.
    The New Gallery dialog opens.
    2. Choose Connections from the General category.
    3. Select BAM Connection in the Items list, and click OK.
    The BAM Connection wizard opens.
    4. Provide a name for the connection. Leave the Create Connection In selection as
    Application Resources.
    5. Click Next.
    6. Enter the following connection information about the Oracle BAM instance.
    7. Click Next.
    8. Test the connection by clicking Test Connection. If the connection was successful,
    the following message appears:
    Passed.
    9. Click Finish.
    Note: You can create connections to Oracle BAM in the Oracle
    JDeveloper Resource Palette as well as the Application Resources
    panel of a specific application. It is recommended that you create these
    connections in the Application Resources pane rather than the
    Resource Palette.
    Field Description
    BAM Web Host Enter the name of the host on which the BAM report server and
    Web server are installed. In most cases, the BAM Web host and
    Oracle BAM Server host are the same.
    BAM Server Host Enter the name of the host on which the Oracle BAM Server is
    installed.
    User Name Enter the Oracle BAM Server user name (typically bamadmin).
    Password Enter the password of the user name.
    HTTP Port Enter the port number or accept the default value of 8888. This is
    the HTTP port for the BAM Web host.
    RMI Port Enter the port number or accept the default value of 9085. The
    RMI port is for the BAM report cache, which is part of the Oracle
    BAM Server.
    Use HTTPS Select this check box if you want to use secure HTTP (HTTPS) to
    connect to the Oracle BAM Server during design time.
    Otherwise, HTTP is used.
    Message was edited by:
    Mario.Mesquita

    Ok that will be nice, but is not the case I dont want to read the tutorial, the problem is I already start to read and execute the tutorial you told me the problem is this tutorial it doesnt show how to do everything from scratch because you already have inside the zip file everything like xmls etc etc, and I want to get my DO and create the process myself, I dont want to get something that it is already done, this tutorial does not show for example how to create this composite.xml, this file it is already inside the zip file, so this way I just follow half of the process and dont learn how to make the whole process.
    tks

  • BAM Server Connection FAILED

    I'm working with BAM 10.1.2 and BPEL 10.1.2.0.2. Well, I'm trying connect to the BAM server and I can't do it!!!
    Maybe I need something..... but i dont know what?
    I red that is posible fix this issue installing the BPEL PM 10.1.3 but I dont to find that download!
    help me!

    Hello - typo from my previous response - pl read last word as "access". Contact Oracle rep for quick BAM 10.1.3 access. (if this is possible for you).
    http://www.oracle.com/technology/tech/java/oc4j/10131/index.html
    http://www.oracle.com/technology/software/products/ias/soapreview.html
    BPEL 10.1.2 has BAM -sensor- connection as [preview] mode.
    Alternates - in BPEL_BAM server dialog box
    (a) donot use localhost, (b) provide domain name in CAPS (donot leave empty). (c) Provide server name in CAPS.

  • Hardcoded BAM server parameters when using BAM sensors

    The problem we're having is that when a BPEL process has BAM sensors, the BAM server configuration parameters are hardcoded in bpel.xml and sensorAction.xml.
    This causes problems when the process is being deployed to a different instance than the development instance.
    I solved the problem for the bpel.xml file with the <customize> ant task, but haven't found a solution yet for sensorAction.xml.
    Any suggestions?
    Thanks,
    Arnold van Koppen

    See..when the BAM Server is down the corresponding data objects wont be available to you..During the design time wat u do is create a variable which contains the elements dat u wanna monitor in the BAM...IN BAM u create data objects ..then u map the schema from the BPEL to the BAM Data Objects ...U need a BAM Server connection which pulls up the metadata from the server ..If the BAM Server is down u wont get the BAM DOs...to keep a back up u can use DB as the sensor action so that the data from the sensor action is written to the DB..Using a DB Adapter i think the data from the Reports schema can be written to the OracleBAM schema ...so that even if the BAM Server is down the data is written to the OracleBAM schema

  • BAM Server stopped working - Cannot connect to the Oracle BAM services

    Hi,
    On logging into the OracleBAM page, I get Error 500 - Internal Server Error.
    Caused by: java.lang.reflect.InvocationTargetException
    Caused by: oracle.bam.common.remoting.ServiceUnavailableException: BAM-00223: Service "interface oracle.bam.adc.common.core.IDataStore" is unavailable.
    Caused by: oracle.bam.adc.api.exceptions.ServerUnavailableException: BAM-01261: Cannot connect to the Oracle BAM services.
    In the server startup log I find the following error before the server state changed to RUNNING
    BAM-01324: Unable to establish BAM administrator account.
    java.lang.Exception: BAM administrator account OracleSystemUser does not have administrator privileges.
    How do I fix this? Help Please!
    Also, is there a way to bring my BAM installation back to its vanilla state? Maybe run the Repository Creation Utility once more? Are there any files on the server that has to be cleaned?
    Thanks
    Alosh

    Hello SOA gurus,
    We're getting the same error as well. Our's a Linux environment and we've configured 2 managed servers (soa_server and bam_server)
    Log file for the bam_server throws up this error message periodically. Looks like the other server doesn't. Does this message pertain to only BAM server ? (I'm new to SOA suite).
    Also, is this a show stopper ? I've seen the managed server going down at times and wasn't sure if it was due to this error. Don't know if this error can be ignored or need to fix.
    Can someone help on how to fix this really soon please ?
    Thanks
    Muthu

  • BAM Connection in 12C -  Failed to establish a connection to localhost at port 7004.Please verify the Bam server host and JNDI port.

    Hi,
    BAM server is running on 7004 in our local system.
    We need o connect to BAM server from OSB service.
    We tried to use the BAM adapter in the pipeline in 12c, We received Failed to establish a connection to localhost at port 7004.Please verify the Bam server host and JNDI port.
    Please let us know the resolution to this issue.
    Also please provide some links/steps to connect from OSB service to BAM server in 12c.
    Thanks,

    In BAM 12c, you can send data via JMS by configuring an EMS in BAM using the "self-described" payload. Make sure the date formats match correctly. You can configure an error queue which will show you any data parsing problems.
    For example,
    <msgRoot dataObjectName="Student" operationType="insert" keys="RequestId">
       <RequestId>R1000</RequestId>
       <StudentId>S12345</StudentId>
       <RequestType>Admission</RequestType>
       <RequestStatus>Open</RequestStatus>
       <RequestMessage>Please Admin</RequestMessage>
       <RequestCode>3</RequestCode>
       <SubmitTime>2015-03-17 18:23:07</SubmitTime>
       <ApprovalTime>2015-02-18 18:23:07</ApprovalTime>
    </msgRoot>

  • BAM server does not start after cluster install

    Hi All,
    BAM server is not starting properly with the below exception. It happens in cluster environment linux 5.5, single node linux 5.5 enviroment. I am using jrockit JDK.
    Its Urgent. Please let me know if some one has come across this issue.
    <Feb 21, 2012 10:43:54 PM EST> <Error> <oracle.bam.adc.kernel.viewsets.satellite.GenericSatellite> <BEA-000000> <BAM-00553: Resources start operation for destination topic/oracle.bam.messaging.systemobjectnotification failed.. [Ljava.lang.StackTraceElement;@2ab016f>
    <Feb 21, 2012 10:43:54 PM EST> <Error> <HTTP> <BEA-101216> <Servlet: "BamServer" failed to preload on startup in Web application: "/oracle/bam".
    java.lang.ExceptionInInitializerError
         at oracle.bam.adc.kernel.viewsets.satellite.GenericSatellite.start(GenericSatellite.java:285)
         at oracle.bam.adc.kernel.server.ADCService.startService(ADCService.java:88)
         at oracle.bam.server.BamServer$ServiceEntry$1.run(BamServer.java:1717)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.bam.common.messaging.api.exception.StartFailedException: BAM-00553: Resources start operation for destination topic/oracle.bam.messaging.systemobjectnotification failed.
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.onStartFailedException(MessageOperationBase.java:1616)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1521)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1476)
         at oracle.bam.adc.kernel.viewsets.satellite.GenericSatellite.start(GenericSatellite.java:274)
         at oracle.bam.adc.kernel.server.ADCService.startService(ADCService.java:85)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.bam.common.messaging.api.MessageFrameworkException: BAM-00500: exception in messaging framework: BAM-00533: Resource open for destination topic/oracle.bam.messaging.systemobjectnotification failed.
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.onStartException(MessageOperationBase.java:1600)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.performStart(MessageOperationBase.java:1572)
         at oracle.bam.common.messaging.api.jms.JMSMessageProducer.performStart(JMSMessageProducer.java:513)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1512)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1477)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.bam.common.messaging.api.exception.OpenFailedException: BAM-00533: Resource open for destination topic/oracle.bam.messaging.systemobjectnotification failed.
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.waitForOpen(MessageOperationBase.java:1355)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.waitForOpen(MessageOperationBase.java:1290)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.performStart(MessageOperationBase.java:1560)
         at oracle.bam.common.messaging.api.jms.JMSMessageProducer.performStart(JMSMessageProducer.java:513)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1512)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.bam.common.messaging.api.exception.OpenFailedException: BAM-00533: Resource open for destination topic/oracle.bam.messaging.systemobjectnotification failed.
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.onOpenFailedException(MessageOperationBase.java:1272)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.open(MessageOperationBase.java:1172)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.access$000(MessageOperationBase.java:72)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase$1.performOperation(MessageOperationBase.java:1152)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase$UtilityThread.run(MessageOperationBase.java:2545)
    Caused By: oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination topic/oracle.bam.messaging.systemobjectnotification failed.
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.onRecoveryFailedException(MessageOperationBase.java:2027)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.recover(MessageOperationBase.java:1865)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.onOpenException(MessageOperationBase.java:1251)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.performOpen(MessageOperationBase.java:1222)
         at oracle.bam.common.messaging.api.invmjms.INVMJMSMessageProducer.performOpen(INVMJMSMessageProducer.java:222)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination topic/oracle.bam.messaging.systemobjectnotification failed.
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.performRecovery(MessageOperationBase.java:1979)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.recover(MessageOperationBase.java:1856)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.onOpenException(MessageOperationBase.java:1252)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.performOpen(MessageOperationBase.java:1222)
         at oracle.bam.common.messaging.api.invmjms.INVMJMSMessageProducer.performOpen(INVMJMSMessageProducer.java:223)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.bam.common.messaging.api.MessageFrameworkException: BAM-00500: exception in messaging framework: BAM-00500: exception in messaging framework: null
         at oracle.bam.common.messaging.api.jms.JMSMessageProducer.acquireResources(JMSMessageProducer.java:698)
         at oracle.bam.common.messaging.api.invmjms.INVMJMSMessageProducer.acquireResources(INVMJMSMessageProducer.java:282)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.performOpen(MessageOperationBase.java:1211)
         at oracle.bam.common.messaging.api.invmjms.INVMJMSMessageProducer.performOpen(INVMJMSMessageProducer.java:223)
         at oracle.bam.common.messaging.base.operation.MessageOperationBase.open(MessageOperationBase.java:1163)
         Truncated. see log file for complete stacktrace
    Caused By: oracle.bam.common.messaging.api.MessageFrameworkException: BAM-00500: exception in messaging framework: null
         at oracle.bam.common.messaging.base.connection.jms.JMSConnectionFactory.newInstance(JMSConnectionFactory.java:336)
         at oracle.bam.common.messaging.base.connection.jms.JMSSharedConnectionFactory.newInstance(JMSSharedConnectionFactory.java:279)
         at oracle.bam.common.messaging.base.connection.jms.JMSSharedConnectionFactory.newInstance(JMSSharedConnectionFactory.java:55)
         at oracle.bam.common.messaging.base.connection.ConnectionFactoryBase.getInstance(ConnectionFactoryBase.java:84)
         at oracle.bam.common.messaging.base.connection.jms.JMSSharedConnectionFactory.getInstance(JMSSharedConnectionFactory.java:149)
         Truncated. see log file for complete stacktrace
    Caused By: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://CHAITU-HP:9001: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:788)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         Truncated. see log file for complete stacktrace
    Caused By: java.net.ConnectException: t3://CHAITU-HP:9001: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination
         at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         Truncated. see log file for complete stacktrace
    Caused By: java.rmi.ConnectException: Destination unreachable; nested exception is:
         java.net.ConnectException: Connection refused: connect; No available router to destination
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
         at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
         at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
         at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
         Truncated. see log file for complete stacktrace
    -Chaitu

    The issue was with JMS modules. I missed to identify the subdeployments tab for UMSJMSSystemResource where we had two sub deployments as UMSJMSSubDMSOA and UMSJMSSubDMSOA_auto..
    I've removed the second subdeployment and all resources listed against is by following this below path in Admin Console
    click JMS Modules -> Click UMSJMSSystemResource -> Click the Subdeployments tab.
    Ensure that UMSJMSSubDMSOA is the only subdeployment available. Remove others if listed and all dependant resources as applicable to your environment.
    Go back to UMSJMSSystemResource and click Targets.
    Deselect BAM_Cluster as target.
    Click Save and Activate.
    Upon subsequent restart, the Server came up nice and fine.
    Regards!
    Sarat

  • After configuring  LDAP Oracle BAM Server is not starting

    Configured LDAP on SOA Suite PS3 (11.1.1.4.0) environment. As per the requirement create OracleSystemUser and OracleSystemGroup in external LDAP and made the user as memner to OracleSystemGroup. Followed the guide @ http://www.oracle.com/technetwork/middleware/bam/technote-bam-multiplesecurityprovid-130532.pdf
    As per the BAM requirement,
    1) Created user "OracleSystemUser" in the external LDAP
    2) Created group "OracleSystemGroup" in the external ldap
    3) Made "OracleSystemUser" as member to "OracleSystemGroup"
    Post configuration, restarted SOA Admin Server and Oracle BAM Server but BAM Server failed to start and its goving following error in the logs :
    [2011-08-17T13:34:38.563+00:00] [bam_server1] [NOTIFICATION] [] [oracle.bam.adc.kernel.server.DataStoreServer] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: OracleSystemUser ] [ecid: 679489bd4ac3a480:-4b8798f0:131d7f26dd0:-8000-0000000000000002,0] [APP: oracle-bam#11.1.1] BAM schema version is 2025
    [2011-08-17T13:35:28.530+00:00] [bam_server1] [ERROR] [] [oracle.bam.adc.security] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: OracleSystemUser ] [ecid: 679489bd4ac3a480:-4b8798f0:131d7f26dd0:-8000-0000000000000002,0] [APP: oracle-bam#11.1.1] [15] Authenticator.createAdminContext: Exception occurred attempting to create administrator context.[[
    java.lang.Exception: BAM administrator account OracleSystemUser does not m_connection-jpss null
    at oracle.bam.adc.security.authentication.Authenticator.createAdminContext(Authenticator<Aug 22, 2011 2:20:00 PM GMT+00:00> <Warning> <org.apache.myfaces.trinidad.webapp.ResourceServlet> <BEA-000000> <ResourceServlet._setHeaders(): Content type for /bi/jsLibs/engine_20101227.swf is NULL! at oracle.bam.adc.kernel.server.ADCService.startService(ADCService.java:91)
    Cause: Unknown file extension> erver$ServiceEntry$1.run(BamServer.java:1717)
    Verified the synchronization of OracleSystemUser as I was able to login using this user to other SOA Application urls.
    Any pointers to resolve this issue would be highly appreciated.

    Hi Raj,
    Couple of points. Please check,
    1. if the listener is up
    2. the tnsnames.ora to check the right HOST
    3. related services are up
    The following thread may be of use :
    Re: Not able to connect to Oracle B2B database after restart of my system
    Regards,
    Dheeraj

  • Opening BAM Server Port and Integrating BPEL Server over Internet

    Hi Friends,
    I have a BPEL Process which has Sensor Actions to insert data to a BAM Data Object. BPEL & BAM Servers are on different boxes and have to be accessed over the internet. I want to know whether anyone can give me any pointers to manually open BAM Server's Port from a Windows XP machine to be accessed by a BPEL Server Process over Internet. Pl. provide detailed steps in case possible.
    Appreciate your help in advance.
    Thanks
    Ram

    When you create the BPEL process (or after you deploy it) you can modify the bam server settings. In your case, I think all you need to do is supply the correct port -- 445 instead of 80
    If you are doing this post-deployment you can go to the BPEL console, select the BPEL service and modify the connection settings by modifying the process' descriptor. You should modify the bamserver.port property. If you are not using 10.1.3.3, then there is a bug with the descriptor page that requires that you make sure you re-type in the bamserver.password field PRIOR to clicking update desciptor.
    If you are doing it pre-deployment, you can modify the bpel.xml file in JDeveloper of your BPEL process. You will see the bamserver.port property defined in that file.

  • Dispatcher Running But no Server Connected---- Fluctuate

    Hi All,
       I found a strange problem in my QA system.
    My QA system fluctuates most of the time. It Runs ok but just between 5-10 min after running successfully it suddenly goes down and the connection to the server is lost.
    The ABAP stack runs absolutely ok even during that time. But the JAVA stack throws an error like u201CDispatcher is running but no server connected u201C.
    Do anyone have any idea on this. The same installation is applied to Dev also and it is working perfectly but the QA is giving me the problem.
    Thanks ,
    JAY.

    Yes i got ,,
      and here it is...
    ============================================================================
    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7186 - 630]/>
    <!NAME[./log/system/server.log]/>
    <!PATTERN[server.log]/>
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    <!ENCODING[ASCII]/>
    <!FILESET[0, 5, 10485760]/>
    <!PREVIOUSFILE[server.4.log]/>
    <!NEXTFILE[server.1.log]/>
    <!LOGHEADER[END]/>
    #1.5#0003BADBE09F002400000052000059E4000455F2596502B9#1220399277081#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000053000059E4000455F259655E98#1220399277104#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.aii.af finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000054000059E4000455F259655F83#1220399277105#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.aii.af finished on current cluster node for 30 ms.#
    #1.5#0003BADBE09F002400000055000059E4000455F25965A193#1220399277121#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.security.ws] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000056000059E4000455F259667B9A#1220399277177#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Warning#1#com.sap.engine.services.deploy#Plain###
    Warning occurred on server 39925850 during stopApp sap.com/com.sap.aii.security.ws : Application sap.com/com.sap.xi.pck has a weak reference to application sap.com/com.sap.aii.security.ws which is being stopped and it may not work correctly.#
    #1.5#0003BADBE09F002400000057000059E4000455F259667CC5#1220399277178#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.aii.security.ws finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000058000059E4000455F259667D58#1220399277178#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.aii.security.ws finished on current cluster node for 71 ms.#
    #1.5#0003BADBE09F002400000059000059E4000455F25966BE50#1220399277194#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.pmi.adm] finished successfully on Web Container.#
    #1.5#0003BADBE09F00240000005A000059E4000455F25966C522#1220399277196#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.pmi.adm finished successfully on server 39925850#
    #1.5#0003BADBE09F00240000005B000059E4000455F25966C5C3#1220399277196#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.pmi.adm finished on current cluster node for 15 ms.#
    #1.5#0003BADBE09F00240000005C000059E4000455F25966FE56#1220399277211#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.engine.docs.examples] finished successfully on Web Container.#
    #1.5#0003BADBE09F00240000005D000059E4000455F25967059D#1220399277213#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.engine.docs.examples finished successfully on server 39925850#
    #1.5#0003BADBE09F00240000005E000059E4000455F259670641#1220399277213#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.engine.docs.examples finished on current cluster node for 14 ms.#
    #1.5#0003BADBE09F00240000005F000059E4000455F259672D2B#1220399277223#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af.adapter.caller] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000060000059E4000455F2596732D6#1220399277224#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.aii.af.adapter.caller finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000061000059E4000455F259673370#1220399277224#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.aii.af.adapter.caller finished on current cluster node for 8 ms.#
    #1.5#0003BADBE09F002400000062000059E4000455F2596783E9#1220399277245#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.xi.repository] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000063000059E4000455F259692FAB#1220399277354#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sap.xi.repository' application stopped successfully.#
    #1.5#0003BADBE09F002400000064000059E4000455F259693D52#1220399277358#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.xi.repository finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000065000059E4000455F259693DF7#1220399277358#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.xi.repository finished on current cluster node for 131 ms.#
    #1.5#0003BADBE09F002400000066000059E4000455F259697F45#1220399277375#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.security.core.admin] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000067000059E4000455F25969852C#1220399277376#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.security.core.admin finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000068000059E4000455F2596985C6#1220399277376#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.security.core.admin finished on current cluster node for 14 ms.#
    #1.5#0003BADBE09F002400000069000059E4000455F25969A7A4#1220399277385#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af.ispeak.eventlistener] finished successfully on Web Container.#
    #1.5#0003BADBE09F00240000006A000059E4000455F25969ACBF#1220399277386#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.aii.af.ispeak.eventlistener finished successfully on server 39925850#
    #1.5#0003BADBE09F00240000006B000059E4000455F25969AD5B#1220399277387#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.aii.af.ispeak.eventlistener finished on current cluster node for 8 ms.#
    #1.5#0003BADBE09F00240000006C000059E4000455F25969B9DB#1220399277390#/System/Server##com.sap.bcb.support.DeployEventListener.processApplicationEvent######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.bcb.support.DeployEventListener#Plain###BCB application will be stopped now...#
    #1.5#0003BADBE09F00240000006D000059E4000455F2596AFCC1#1220399277472#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/tcbcbici] finished successfully on Web Container.#
    #1.5#0003BADBE09F00240000006E000059E4000455F25975D1C9#1220399278182#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/tcbcbici finished successfully on server 39925850#
    #1.5#0003BADBE09F00240000006F000059E4000455F25975D288#1220399278183#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/tcbcbici finished on current cluster node for 794 ms.#
    #1.5#0003BADBE09F002400000070000059E4000455F2597620B9#1220399278203#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.xi.directory] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000071000059E4000455F259776E5E#1220399278288#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sap.xi.directory' application stopped successfully.#
    #1.5#0003BADBE09F002400000072000059E4000455F2597779D7#1220399278291#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.xi.directory finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000073000059E4000455F259777A78#1220399278291#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.xi.directory finished on current cluster node for 105 ms.#
    #1.5#0003BADBE09F002400000074000059E4000455F259779C04#1220399278300#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/tcwdpdfsvrchal] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000075000059E4000455F25977A12F#1220399278301#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/tcwdpdfsvrchal finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000076000059E4000455F25977A1CB#1220399278301#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/tcwdpdfsvrchal finished on current cluster node for 7 ms.#
    #1.5#0003BADBE09F002400000077000059E4000455F25977DF6D#1220399278317#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.engine.heartbeat] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000078000059E4000455F259785B52#1220399278349#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.engine.heartbeat finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000079000059E4000455F259785C06#1220399278349#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.engine.heartbeat finished on current cluster node for 46 ms.#
    #1.5#0003BADBE09F00240000007A000059E4000455F25978A79B#1220399278368#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.xi.mdt] finished successfully on Web Container.#
    #1.5#0003BADBE09F00240000007B000059E4000455F25979FC58#1220399278455#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.xi.mdt finished successfully on server 39925850#
    #1.5#0003BADBE09F00240000007C000059E4000455F25979FD0E#1220399278456#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.xi.mdt finished on current cluster node for 105 ms.#
    #1.5#0003BADBE09F00240000007D000059E4000455F2597A1E57#1220399278464#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af.rfc.app] finished successfully on Web Container.#
    #1.5#0003BADBE09F00240000007E000059E4000455F2597A2396#1220399278465#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.aii.af.rfc.app finished successfully on server 39925850#
    #1.5#0003BADBE09F00240000007F000059E4000455F2597A2431#1220399278466#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.aii.af.rfc.app finished on current cluster node for 8 ms.#
    #1.5#0003BADBE09F002400000080000059E4000455F2597A426D#1220399278473#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.engine.class.download] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000081000059E4000455F2597A475A#1220399278475#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.engine.class.download finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000082000059E4000455F2597A47F3#1220399278475#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.engine.class.download finished on current cluster node for 7 ms.#
    #1.5#0003BADBE09F002400000083000059E4000455F2597A6C56#1220399278484#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.xi.pck] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000084000059E4000455F2597AA4ED#1220399278499#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sap.xi.pck' application stopped successfully.#
    #1.5#0003BADBE09F002400000085000059E4000455F2597AAFAB#1220399278501#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.xi.pck finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000086000059E4000455F2597AB05B#1220399278501#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.xi.pck finished on current cluster node for 24 ms.#
    #1.5#0003BADBE09F002400000087000059E4000455F2597ACFA9#1220399278509#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/com.sap.aii.af.jmsadapter] finished successfully on Web Container.#
    #1.5#0003BADBE09F002400000088000059E4000455F2597AD48F#1220399278511#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.aii.af.jmsadapter finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000089000059E4000455F2597AD53B#1220399278511#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.aii.af.jmsadapter finished on current cluster node for 7 ms.#
    #1.5#0003BADBE09F00240000008A000059E4000455F2597AF7C9#1220399278520#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/tcTechSrvXML_DAS] finished successfully on Web Container.#
    #1.5#0003BADBE09F00240000008B000059E4000455F2597B4D7C#1220399278542#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/tcTechSrvXML_DAS' application stopped successfully.#
    #1.5#0003BADBE09F00240000008C000059E4000455F2597B5550#1220399278544#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/tcTechSrvXML_DAS finished successfully on server 39925850#
    #1.5#0003BADBE09F00240000008D000059E4000455F2597B55EA#1220399278544#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/tcTechSrvXML_DAS finished on current cluster node for 31 ms.#
    #1.5#0003BADBE09F00240000008E000059E4000455F2597B7AE9#1220399278553#/System/Server##com.sap.engine.services.servlets_jsp.server.container.WebContainer######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.container.WebContainer#Plain###Stop of application [sap.com/tcmonitoringsysteminfo] finished successfully on Web Container.#
    #1.5#0003BADBE09F00240000008F000059E4000455F2597B7FBE#1220399278555#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/tcmonitoringsysteminfo' application stopped successfully.#
    #1.5#0003BADBE09F002400000090000059E4000455F2597B8562#1220399278556#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/tcmonitoringsysteminfo finished successfully on server 39925850#
    #1.5#0003BADBE09F002400000091000059E4000455F2597B860F#1220399278556#/System/Server##com.sap.engine.services.deploy######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/tcmonitoringsysteminfo finished on current cluster node for 10 ms.#
    #1.5#0003BADBE09F002400000093000059E4000455F2597BBA47#1220399278570#/System/Server##com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame######8d4dc2c0794911ddb7d70003badbe09f#SAPEngine_System_Thread[impl:5]_19##0#0#Error#1#com.sap.engine.services.servlets_jsp.server.ServletsAndJspServerFrame#Plain###Cannot lookup Deploy service.
    The error is: java.lang.ClassCastException: null
    Exception id: [0003BADBE09F002400000092000059E4000455F2597BB924]#
    #1.5#0003BADBE09F004400000015000059E4000455F2597BDE91#1220399278579#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service servlet_jsp stopped.#
    #1.5#0003BADBE09F004400000016000059E4000455F2597BE858#1220399278581#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service adminadapter stopped.#
    #1.5#0003BADBE09F004400000017000059E4000455F2597F9A9D#1220399278824#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service monitor stopped.#
    #1.5#0003BADBE09F004400000018000059E4000455F2598006D9#1220399278851#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service basicadmin stopped.#
    #1.5#0003BADBE09F004400000019000059E4000455F259810CCC#1220399278918#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service apptracing stopped.#
    #1.5#0003BADBE09F00440000001A000059E4000455F259821AAC#1220399278987#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service jms_provider stopped.#
    #1.5#0003BADBE09F0032000000B5000059E4000455F259826C15#1220399279008#/System/Server##com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer######5c5547a0794511dd855e0003badbe09f#Thread[SAPEngine_CCMSCommandConsumer_0,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Info#1#com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer#Plain###CCMSGeneration thread was interrupted#
    #1.5#0003BADBE09F00440000001B000059E4000455F259826E13#1220399279009#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service tc.monitoring.logviewer stopped.#
    #1.5#0003BADBE09F00440000001C000059E4000455F2598277B3#1220399279011#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service jmx stopped.#
    #1.5#0003BADBE09F00440000001D000059E4000455F25982BD65#1220399279029#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service webdynpro stopped.#
    #1.5#0003BADBE09F00440000001E000059E4000455F25982C474#1220399279031#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service telnet stopped.#
    #1.5#0003BADBE09F00440000001F000059E4000455F259832F9D#1220399279058#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service shell stopped.#
    #1.5#0003BADBE09F004000000009000059E4000455F2598332E1#1220399279059#/System/Server##com.sap.engine.services.deploy######8d1eea90794911ddb8490003badbe09f#SAPEngine_System_Thread[impl:5]_73##0#0#Warning#1#com.sap.engine.services.deploy#Plain###Stopping application sap.com/com.sap.jdo which is in started mode, because the resource applocking with type service is not available.#
    #1.5#0003BADBE09F00400000000A000059E4000455F2598357B8#1220399279069#/System/Server##com.sap.engine.services.dbpool.deploy.ContainerImpl######8d1eea90794911ddb8490003badbe09f#SAPEngine_System_Thread[impl:5]_73##0#0#Info#1#com.sap.engine.services.dbpool.deploy.ContainerImpl#Plain###DataSources or DataSource aliases of 'sap.com/com.sap.jdo' application stopped successfully.#
    #1.5#0003BADBE09F00400000000B000059E4000455F259835E58#1220399279070#/System/Server##com.sap.engine.services.deploy######8d1eea90794911ddb8490003badbe09f#SAPEngine_System_Thread[impl:5]_73##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp over application sap.com/com.sap.jdo finished successfully on server 39925850#
    #1.5#0003BADBE09F00400000000C000059E4000455F259835EF6#1220399279070#/System/Server##com.sap.engine.services.deploy######8d1eea90794911ddb8490003badbe09f#SAPEngine_System_Thread[impl:5]_73##0#0#Info#1#com.sap.engine.services.deploy#Plain###
    Operation stopApp on application sap.com/com.sap.jdo finished on current cluster node for 9 ms.#
    #1.5#0003BADBE09F002D00000036000059E4000455F25983691D#1220399279073#/System/Server##com.sap.engine.services.applocking.AppLockingApplicationFrame.unbindFromNaming(expectNamingAvailable)######8d473310794911ddc2a40003badbe09f#SAPEngine_System_Thread[impl:5]_63##0#0#Info#1#com.sap.engine.services.applocking.AppLockingApplicationFrame#Java###Successfully unbound from JNDI#1#applocking-service#
    #1.5#0003BADBE09F002D00000037000059E4000455F259836A3C#1220399279073#/System/Server##com.sap.engine.services.applocking.AppLockingApplicationFrame.stop()######8d473310794911ddc2a40003badbe09f#SAPEngine_System_Thread[impl:5]_63##0#0#Info#1#com.sap.engine.services.applocking.AppLockingApplicationFrame#Java### stopped successfully#1#applocking-service#
    #1.5#0003BADBE09F004400000020000059E4000455F259836CED#1220399279074#/System/Server##com.sap.engine.core.service630.container.MemoryContainer######57d5b2f0794511ddbfb00003badbe09f#Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service applocking stopped.#
    #1.5#0003BADBE09F004400000021000059E4000455F25983DD86#1220399279103#/System/Server##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-35,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service dsr stopped.#
    #1.5#0003BADBE09F004900000043000059E4000455F2599103AF#1220399279965#/System/Server##com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_23##0#0#Info#1#com.sapmarkets.bam.jmxadapter.CCMSCommandConsumer#Plain###New thread spawned for generating the ccmstemplates.#
    #1.5#0003BADBE09F004900000044000059E4000455F2599141AA#1220399279980#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###com.sapmarkets.bam.util.BAMRuntimeException: Error occured while trying to register     a new log#
    #1.5#0003BADBE09F006900000008000059E4000455F2599141F8#1220399279981#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###com.sapmarkets.bam.util.BAMRuntimeException: Error occured while trying to register     a new log#
    #1.5#0003BADBE09F00690000000A000059E4000455F2599148D9#1220399279982#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###com.sap.engine.services.jmx.exception.JmxIllegalStateException: JmxFrame not completely initialized, innerMBeanServer is null#
    #1.5#0003BADBE09F004900000046000059E4000455F25991495F#1220399279982#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###com.sap.engine.services.jmx.exception.JmxIllegalStateException: JmxFrame not completely initialized, innerMBeanServer is null#
    #1.5#0003BADBE09F004900000048000059E4000455F25991587A#1220399279986#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###Originated from: com.sap.engine.services.jmx.exception.JmxIllegalStateException: JmxFrame not completely initialized, innerMBeanServer is null
         at com.sap.engine.services.jmx.JmxFrame.getInnerMBeanServer(JmxFrame.java:467)
         at com.sap.engine.services.jmx.ClusterInterceptor.getInnerMBS(ClusterInterceptor.java:119)
         at com.sap.engine.services.jmx.ClusterInterceptor.getMBSC(ClusterInterceptor.java:190)
         at com.sap.engine.services.jmx.ClusterInterceptor.isRegistered(ClusterInterceptor.java:868)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.isRegistered(MBeanServerInterceptorChain.java:290)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogAsMBean(AbstractFileLogHandler.java:229)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:151)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:85)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:402)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.handleEvent(AbstractFileLogHandler.java:469)
         at com.sap.tc.logging.LoggingManager.notifyAddLog(LoggingManager.java:342)
         at com.sap.tc.logging.LogController.addLog(LogController.java:1328)
         at com.sap.tc.logging.PropertiesConfigurator.configure(PropertiesConfigurator.java:1119)
         at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:314)
         at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:257)
         at com.sap.jms.client.connection.QueueConnectionFactory.createQueueConnection(QueueConnectionFactory.java:70)
         at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.createQueueConnection(QueueConnectionFactoryImpl.java:162)
         at com.sap.engine.services.ejb.message.JMSBridge.createConnection(JMSBridge.java:194)
         at com.sap.engine.services.ejb.message.JMSBridge.registerQueueListener(JMSBridge.java:142)
         at com.sap.engine.services.ejb.message.JMSBridge.recreateJMSConnection(JMSBridge.java:278)
         at com.sap.engine.services.ejb.message.MDBExceptionListener.onException(MDBExceptionListener.java:38)
         at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.onException(ConnectionImpl.java:118)
         at com.sap.jms.client.connection.Connection.onException(Connection.java:824)
         at com.sap.jms.server.ServerClientAdapter$ExceptionListenerCaller.run(ServerClientAdapter.java:366)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    #1.5#0003BADBE09F00690000000C000059E4000455F259915885#1220399279986#/System/Server##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#Plain###Originated from: com.sap.engine.services.jmx.exception.JmxIllegalStateException: JmxFrame not completely initialized, innerMBeanServer is null
         at com.sap.engine.services.jmx.JmxFrame.getInnerMBeanServer(JmxFrame.java:467)
         at com.sap.engine.services.jmx.ClusterInterceptor.getInnerMBS(ClusterInterceptor.java:119)
         at com.sap.engine.services.jmx.ClusterInterceptor.getMBSC(ClusterInterceptor.java:190)
         at com.sap.engine.services.jmx.ClusterInterceptor.isRegistered(ClusterInterceptor.java:868)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.isRegistered(MBeanServerInterceptorChain.java:290)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogAsMBean(AbstractFileLogHandler.java:229)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:151)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:85)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:402)
         at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.handleEvent(AbstractFileLogHandler.java:469)
         at com.sap.tc.logging.LoggingManager.notifyAddLog(LoggingManager.java:342)
         at com.sap.tc.logging.LogController.addLog(LogController.java:1328)
         at com.sap.tc.logging.PropertiesConfigurator.configure(PropertiesConfigurator.java:1119)
         at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:314)
         at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:257)
         at com.sap.jms.client.connection.QueueConnectionFactory.createQueueConnection(QueueConnectionFactory.java:70)
         at com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl.createQueueConnection(QueueConnectionFactoryImpl.java:162)
         at com.sap.engine.services.ejb.message.JMSBridge.createConnection(JMSBridge.java:194)
         at com.sap.engine.services.ejb.message.JMSBridge.registerQueueListener(JMSBridge.java:142)
         at com.sap.engine.services.ejb.message.JMSBridge.recreateJMSConnection(JMSBridge.java:278)
         at com.sap.engine.services.ejb.message.MDBExceptionListener.onException(MDBExceptionListener.java:38)
         at com.sap.engine.services.jmsconnector.cci.ConnectionImpl.onException(ConnectionImpl.java:118)
         at com.sap.jms.client.connection.Connection.onException(Connection.java:824)
         at com.sap.jms.server.ServerClientAdapter$ExceptionListenerCaller.run(ServerClientAdapter.java:366)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    ==================================================================================

  • BAM cannot connect to WEBLOGIC

    I have this setup in my EMS :
    WeblogicJMS
    View|Edit|Copy|Delete|Create|Start|Stop|Test|Refresh
    Name: WeblogicJMS
    Owner: fmwadmin
    Created: 7/29/08 3:00:57 PM
    Last modified: 7/30/08 6:34:52 PM
    Status: Stopped
    Initial Context Factory: weblogic.jni.WLInitialContextFactory.
    JNDI Service Provider URL: t3://10.20.162.16:7001.
    Topic/Queue ConnectionFactory Name: jms/confactory.
    Topic/Queue Name: jms/topic.
    JNDI Username: weblogic.
    JNDI Password: ********.
    JMS Message Type: TextMessage.
    Durable Subscriber Name (Optional): OracleBam.
    Message Selector (Optional): OracleBam.
    DataObject Name: /WeblogicJMS/TextJMS.
    Operation: Insert.
    Batching: No.
    Transaction: No.
    Start when BAM Server starts: No.
    JMS Username (Optional): .
    JMS Password (Optional): .
    XML Formatting
    Pre-Processing
    Message Specification
    Message Element Name: textdata
    Column Value
    Element Tag
    Attribute
    Source to Data Object Field Mapping
    Key Tag name Data Object Field
    . textdata. textdata. String
    When I try to start the connection I get this error:
    An error occurred while processing your request
    Details...
    Exception Message BAM-00533: Resource open for destination "jms/topic" failed.
    Stack Trace at oracle.bam.common.messaging.base.operation.MessageOperationBase.onStartFailedException(MessageOperationBase.java:1582) at oracle.bam.common.messaging.api.MessageConsumerRegistry.onStartFailedException(MessageConsumerRegistry.java:822) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1487) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1442) at oracle.bam.ems.engine.JMSListener.<init>(JMSListener.java:143) at oracle.bam.ems.engine.EMSHandler.initMessageHandler(EMSHandler.java:392) at oracle.bam.ems.engine.EMSHandler.start(EMSHandler.java:422) at oracle.bam.ems.server.EMSServer.start(EMSServer.java:103) at oracle.bam.web.architect.Sources.startEMS(Sources.java:930) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at oracle.bam.web.shared.WebPage.invokeWebMethod(WebPage.java:480) at oracle.bam.web.shared.WebPage.processRequest(WebPage.java:414) at oracle.bam.web.shared.WebPage.processRequest(WebPage.java:298) at _2609._architect._default._jspService(_default.java:46) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:60) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:406) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:706) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:627) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65) at oracle.bam.web.cache.ClientSideCache.doFilter(ClientSideCache.java:79) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15) at oracle.bam.web.filters.GZIPFilter.doFilter(GZIPFilter.java:86) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.redirect.Redirect.doFilter(Redirect.java:66) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.filters.ValidateBrowserSupport.doFilter(ValidateBrowserSupport.java:93) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.filters.CharsetFixupFilter.doFilter(CharsetFixupFilter.java:65) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:583) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:334) at com.evermind.server.http.HttpRequestHandler.doDispatchRequest(HttpRequestHandler.java:942) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:843) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:658) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:626) at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:417) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:189) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:163) at oracle.oc4j.network.ServerSocketReadHandler$ClientRunnable.run(ServerSocketReadHandler.java:275) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) ...
    Debugging Information BAM-00553: Resources start for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Start.Failed"] BAM-00500: Exception in messaging framework "BAM-00533: Resource open for destination "jms/topic" failed.". [ErrorSource="Messaging", ErrorID="MessageFramework.Exception"] BAM-00533: Resource open for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Open.Failed"] BAM-00533: Resource open for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Open.Failed"] BAM-00523: Resource recovery for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Recovery.Failed"] BAM-00523: Resource recovery for destination "jms/topic" failed. [ErrorSource="Messaging", ErrorID="MessageFramework.Recovery.Failed"] BAM-00500: Exception in messaging framework "BAM-00500: Exception in messaging framework "Cannot instantiate class: weblogic.jni.WLInitialContextFactory".". [ErrorSource="Messaging", ErrorID="MessageFramework.Exception"] BAM-00500: Exception in messaging framework "Cannot instantiate class: weblogic.jni.WLInitialContextFactory". [ErrorSource="Messaging", ErrorID="MessageFramework.Exception"] Cannot instantiate class: weblogic.jni.WLInitialContextFactory [ErrorSource="javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jni.WLInitialContextFactory [Root exception is oracle.classloader.util.AnnotatedClassNotFoundException: Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system.]"] Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system. [ErrorSource="oracle.classloader.util.AnnotatedClassNotFoundException: Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system."] Debugging information: oracle.bam.common.messaging.api.exception.StartFailedException: BAM-00553: Resources start for destination "jms/topic" failed.oracle.bam.common.messaging.api.exception.StartFailedException: BAM-00553: Resources start for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.onStartFailedException(MessageOperationBase.java:1582) at oracle.bam.common.messaging.api.MessageConsumerRegistry.onStartFailedException(MessageConsumerRegistry.java:822) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1487) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1442) at oracle.bam.ems.engine.JMSListener.<init>(JMSListener.java:143) at oracle.bam.ems.engine.EMSHandler.initMessageHandler(EMSHandler.java:392) at oracle.bam.ems.engine.EMSHandler.start(EMSHandler.java:422) at oracle.bam.ems.server.EMSServer.start(EMSServer.java:103) at oracle.bam.web.architect.Sources.startEMS(Sources.java:930) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at oracle.bam.web.shared.WebPage.invokeWebMethod(WebPage.java:480) at oracle.bam.web.shared.WebPage.processRequest(WebPage.java:414) at oracle.bam.web.shared.WebPage.processRequest(WebPage.java:298) at _2609._architect._default._jspService(_default.java:46) at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:60) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:406) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:706) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:627) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65) at oracle.bam.web.cache.ClientSideCache.doFilter(ClientSideCache.java:79) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15) at oracle.bam.web.filters.GZIPFilter.doFilter(GZIPFilter.java:86) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.redirect.Redirect.doFilter(Redirect.java:66) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.filters.ValidateBrowserSupport.doFilter(ValidateBrowserSupport.java:93) at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17) at oracle.bam.web.filters.CharsetFixupFilter.doFilter(CharsetFixupFilter.java:65) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:583) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:334) at com.evermind.server.http.HttpRequestHandler.doDispatchRequest(HttpRequestHandler.java:942) at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:843) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:658) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:626) at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:417) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:189) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:163) at oracle.oc4j.network.ServerSocketReadHandler$ClientRunnable.run(ServerSocketReadHandler.java:275) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.bam.common.messaging.api.MessageFrameworkException: BAM-00500: Exception in messaging framework "BAM-00533: Resource open for destination "jms/topic" failed.". at oracle.bam.common.messaging.base.operation.MessageOperationBase.onStartException(MessageOperationBase.java:1566) at oracle.bam.common.messaging.base.operation.MessageOperationBase.performStart(MessageOperationBase.java:1538) at oracle.bam.common.messaging.api.jms.JMSMessageConsumerRegistry.performStart(JMSMessageConsumerRegistry.java:444) at oracle.bam.common.messaging.base.operation.MessageOperationBase.start(MessageOperationBase.java:1478) ... 42 more Caused by: oracle.bam.common.messaging.api.exception.OpenFailedException: BAM-00533: Resource open for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.waitForOpen(MessageOperationBase.java:1321) at oracle.bam.common.messaging.base.operation.MessageOperationBase.waitForOpen(MessageOperationBase.java:1255) at oracle.bam.common.messaging.base.operation.MessageOperationBase.performStart(MessageOperationBase.java:1526) ... 44 more Caused by: oracle.bam.common.messaging.api.exception.OpenFailedException: BAM-00533: Resource open for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.onOpenFailedException(MessageOperationBase.java:1238) at oracle.bam.common.messaging.api.MessageConsumerRegistry.onOpenFailedException(MessageConsumerRegistry.java:785) at oracle.bam.common.messaging.base.operation.MessageOperationBase.open(MessageOperationBase.java:1138) at oracle.bam.common.messaging.base.operation.MessageOperationBase.access$000(MessageOperationBase.java:71) at oracle.bam.common.messaging.base.operation.MessageOperationBase$1.performOperation(MessageOperationBase.java:1118) at oracle.bam.common.messaging.base.operation.MessageOperationBase$UtilityThread.run(MessageOperationBase.java:2512) Caused by: oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.onRecoveryFailedException(MessageOperationBase.java:1993) at oracle.bam.common.messaging.api.MessageConsumerRegistry.onRecoveryFailedException(MessageConsumerRegistry.java:804) at oracle.bam.common.messaging.base.operation.MessageOperationBase.recover(MessageOperationBase.java:1831) at oracle.bam.common.messaging.base.operation.MessageOperationBase.onOpenException(MessageOperationBase.java:1217) at oracle.bam.common.messaging.base.operation.MessageOperationBase.performOpen(MessageOperationBase.java:1188) at oracle.bam.common.messaging.base.operation.MessageOperationBase.open(MessageOperationBase.java:1129) ... 3 more Caused by: oracle.bam.common.messaging.api.exception.RecoveryFailedException: BAM-00523: Resource recovery for destination "jms/topic" failed. at oracle.bam.common.messaging.base.operation.MessageOperationBase.performRecovery(MessageOperationBase.java:1945) at oracle.bam.common.messaging.base.operation.MessageOperationBase.recover(MessageOperationBase.java:1822) ... 6 more Caused by: oracle.bam.common.messaging.api.MessageFrameworkException: BAM-00500: Exception in messaging framework "BAM-00500: Exception in messaging framework "Cannot instantiate class: weblogic.jni.WLInitialContextFactory".". at oracle.bam.common.messaging.api.jms.JMSMessageConsumerRegistry.acquireResources(JMSMessageConsumerRegistry.java:730) at oracle.bam.common.messaging.base.operation.MessageOperationBase.performOpen(MessageOperationBase.java:1177) ... 4 more Caused by: oracle.bam.common.messaging.api.MessageFrameworkException: BAM-00500: Exception in messaging framework "Cannot instantiate class: weblogic.jni.WLInitialContextFactory". at oracle.bam.common.messaging.base.connection.jms.JMSConnectionFactory.newInstance(JMSConnectionFactory.java:317) at oracle.bam.common.messaging.base.connection.jms.JMSConnectionFactory.newInstance(JMSConnectionFactory.java:47) at oracle.bam.common.messaging.base.connection.ConnectionFactoryBase.getInstance(ConnectionFactoryBase.java:82) at oracle.bam.common.messaging.api.jms.JMSMessageConsumerRegistry.acquireResources(JMSMessageConsumerRegistry.java:677) ... 5 more Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jni.WLInitialContextFactory [Root exception is oracle.classloader.util.AnnotatedClassNotFoundException: Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system.] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at oracle.bam.common.messaging.base.connection.jms.JMSConnectionFactory.newInstance(JMSConnectionFactory.java:300) ... 8 more Caused by: oracle.classloader.util.AnnotatedClassNotFoundException: Missing class: weblogic.jni.WLInitialContextFactory Dependent class: com.sun.naming.internal.VersionHelper12 Loader: jre.bootstrap:1.5.0_11 Code-Source: unknown Configuration: jre bootstrap This load was initiated at OracleBamWeb.web.oracle-bam-web:0.0.0 using the Class.forName() method. The missing class is not available from any code-source or loader in the system. at oracle.classloader.PolicyClassLoader.handleClassNotFound(PolicyClassLoader.java:2169) at oracle.classloader.PolicyClassLoader.internalLoadClass(PolicyClassLoader.java:1716) at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1672) at oracle.classloader.PolicyClassLoader.loadClass(PolicyClassLoader.java:1657) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654) ... 12 more ...
    EventParam 1 ...
    State oracle.bam.web.architect.Sources ...
    Event startEMS ...
    Assembly Architect
    Anybody knows what to do?

    Is this problem solved ?
    I too face similar problem . . .
    It says 'Test failed - BAM-00553: Resources start for destination "jms/mytestqueue" failed'
    However this queue exists and I can produce and consume from this queue through stand alone java programs.
    In my case, BAM runs on a seperate Weblogic domain and the JMS queue is on another weblogic domain, however both on the same machine.
    Initial Context Factory: weblogic.jndi.WLInitialContextFactory.
    JNDI Service Provider URL: t3://localhost:7001. ( this is the weblogic domain, where my jms queue resides )
    Topic/Queue Connection Factory Name: weblogic/jms/ConnectionFactory.
    Topic/Queue Name: jms/mytestqueue.
    JNDI Username: .
    JNDI Password: .
    JMS Message Type: MapMessage.

  • Oracle BAM Server don't start

    Oracle BAM Server don't start.
    Below is the log file.
    Any suggestion?
    Thank you!

    Hi,
    The problem is database connection to almost all schemas:
    MDS-00929: unable to look up name "jdbc/mds/owsm" in JNDI context
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "BamServerSingletonServlet" failed to preload on startup in Web application: "/oracle/bam".
    java.lang.RuntimeException: java.sql.SQLException: The Network Adapter could not establish the connection
    You should ensure you can connect from middleware server to database, and data source information is right (<domain_location>/config/jdbc/<datasource files>)
    Hope this helps.
    Regards,
    Jorge

  • Error while creating a application server connection in jdeveloper 10.1.3.2

    When I am trying to create a connection using the wizard with the following inputs
    hostname as :- localhost
    RMI Por as 22667
    When I use the test conection receive the following error
    racle.oc4j.admin.jmx.shared.exceptions.JMXRuntimeException: Error while getting remote MBeanServer for url: ormi://localhost:22667/default
         at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:502)
         at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:161)
         at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
         at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
         at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
         at oracle.oc4j.admin.jmx.remote.rmi.RMIJMXConnectorImpl.getConnector(RMIJMXConnectorImpl.java:190)
         at oracle.oc4j.admin.jmx.remote.JMXConnectorImpl.connect(JMXConnectorImpl.java:400)
         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
         at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper._getJMXConnector(J2EEConnectionWrapper.java:269)
         at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper.getPresentation(J2EEConnectionWrapper.java:76)
         at oracle.jdevimpl.cm.dt.browser.j2ee.J2EEBrowser.openConnectionBrowser(J2EEBrowser.java:75)
         at oracle.jdeveloper.cm.dt.ConnectionNode$NodeOpen.doWork(ConnectionNode.java:423)
         at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
         at java.lang.Thread.run(Thread.java:613)
    Caused by: javax.naming.NamingException: Error reading application-client descriptor: Error communicating with server: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused] [Root exception is java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]]
         at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:127)
         at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:468)
         ... 14 more
    Caused by: java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
         at com.oracle.naming.J2EEContext.create(J2EEContext.java:104)
         at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:124)
         ... 20 more
    Caused by: oracle.oc4j.rmi.OracleRemoteException: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:110)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:123)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:75)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
         at com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:515)
         at com.oracle.naming.J2EEContext.create(J2EEContext.java:97)
         ... 21 more
    Caused by: javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
         at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:292)
         at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:101)
         ... 26 more
    Caused by: java.net.ConnectException: Connection refused
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:428)
         at java.net.Socket.connect(Socket.java:507)
         at java.net.Socket.connect(Socket.java:457)
         at java.net.Socket.<init>(Socket.java:365)
         at java.net.Socket.<init>(Socket.java:207)
         at com.evermind.server.rmi.RMIClientConnection.createSocket(RMIClientConnection.java:682)
         at oracle.oc4j.rmi.ClientSocketRmiTransport.createNetworkConnection(ClientSocketRmiTransport.java:58)
         at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:78)
         at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
         at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:646)
         at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:190)
         at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:174)
         at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
         ... 28 more
    ---- Embedded exception
    javax.naming.NamingException: Error reading application-client descriptor: Error communicating with server: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused] [Root exception is java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]]
         at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:127)
         at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:468)
         at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:161)
         at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
         at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
         at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
         at oracle.oc4j.admin.jmx.remote.rmi.RMIJMXConnectorImpl.getConnector(RMIJMXConnectorImpl.java:190)
         at oracle.oc4j.admin.jmx.remote.JMXConnectorImpl.connect(JMXConnectorImpl.java:400)
         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
         at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper._getJMXConnector(J2EEConnectionWrapper.java:269)
         at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper.getPresentation(J2EEConnectionWrapper.java:76)
         at oracle.jdevimpl.cm.dt.browser.j2ee.J2EEBrowser.openConnectionBrowser(J2EEBrowser.java:75)
         at oracle.jdeveloper.cm.dt.ConnectionNode$NodeOpen.doWork(ConnectionNode.java:423)
         at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
         at java.lang.Thread.run(Thread.java:613)
    Caused by: java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
         at com.oracle.naming.J2EEContext.create(J2EEContext.java:104)
         at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:124)
         ... 20 more
    Caused by: oracle.oc4j.rmi.OracleRemoteException: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:110)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:123)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:75)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
         at com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:515)
         at com.oracle.naming.J2EEContext.create(J2EEContext.java:97)
         ... 21 more
    Caused by: javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
         at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:292)
         at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:101)
         ... 26 more
    Caused by: java.net.ConnectException: Connection refused
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:428)
         at java.net.Socket.connect(Socket.java:507)
         at java.net.Socket.connect(Socket.java:457)
         at java.net.Socket.<init>(Socket.java:365)
         at java.net.Socket.<init>(Socket.java:207)
         at com.evermind.server.rmi.RMIClientConnection.createSocket(RMIClientConnection.java:682)
         at oracle.oc4j.rmi.ClientSocketRmiTransport.createNetworkConnection(ClientSocketRmiTransport.java:58)
         at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:78)
         at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
         at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:646)
         at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:190)
         at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:174)
         at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
         ... 28 more
    ---- Embedded exception
    java.lang.InstantiationException: Error communicating with server: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
         at com.oracle.naming.J2EEContext.create(J2EEContext.java:104)
         at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getApplicationContext(ApplicationClientInitialContextFactory.java:124)
         at oracle.j2ee.naming.ApplicationClientInitialContextFactory.getInitialContext(ApplicationClientInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.fetchMBeanServerEjbRemote(CoreRemoteMBeanServer.java:468)
         at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.<init>(CoreRemoteMBeanServer.java:161)
         at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.<init>(RemoteMBeanServer.java:128)
         at oracle.oc4j.admin.jmx.client.RemoteMBeanServer.getMBeanServer(RemoteMBeanServer.java:158)
         at oracle.oc4j.admin.jmx.client.ClientMBeanServerProxyFactory.getMBeanServer(ClientMBeanServerProxyFactory.java:68)
         at oracle.oc4j.admin.jmx.remote.rmi.RMIJMXConnectorImpl.getConnector(RMIJMXConnectorImpl.java:190)
         at oracle.oc4j.admin.jmx.remote.JMXConnectorImpl.connect(JMXConnectorImpl.java:400)
         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
         at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper._getJMXConnector(J2EEConnectionWrapper.java:269)
         at oracle.jdevimpl.cm.dt.J2EEConnectionWrapper.getPresentation(J2EEConnectionWrapper.java:76)
         at oracle.jdevimpl.cm.dt.browser.j2ee.J2EEBrowser.openConnectionBrowser(J2EEBrowser.java:75)
         at oracle.jdeveloper.cm.dt.ConnectionNode$NodeOpen.doWork(ConnectionNode.java:423)
         at oracle.ide.dialogs.ProgressRunnable.run(ProgressRunnable.java:159)
         at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
         at java.lang.Thread.run(Thread.java:613)
    Caused by: oracle.oc4j.rmi.OracleRemoteException: Connection refused; nested exception is:
         javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:110)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.getFinder(ApplicationClientResourceFinder.java:123)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.getLocation(ApplicationClientResourceFinder.java:75)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.getEjbBinding(ApplicationClientResourceFinder.java:38)
         at com.oracle.naming.J2EEContext.addEJBReferenceEntries(J2EEContext.java:515)
         at com.oracle.naming.J2EEContext.create(J2EEContext.java:97)
         ... 21 more
    Caused by: javax.naming.CommunicationException: Connection refused [Root exception is java.net.ConnectException: Connection refused]
         at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:292)
         at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
         at oracle.oc4j.deployment.ApplicationClientResourceFinder.lookupResourceFinder(ApplicationClientResourceFinder.java:101)
         ... 26 more
    Caused by: java.net.ConnectException: Connection refused
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:428)
         at java.net.Socket.connect(Socket.java:507)
         at java.net.Socket.connect(Socket.java:457)
         at java.net.Socket.<init>(Socket.java:365)
         at java.net.Socket.<init>(Socket.java:207)
         at com.evermind.server.rmi.RMIClientConnection.createSocket(RMIClientConnection.java:682)
         at oracle.oc4j.rmi.ClientSocketRmiTransport.createNetworkConnection(ClientSocketRmiTransport.java:58)
         at oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java:78)
         at oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTransport.java:68)
         at com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.java:646)
         at com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientConnection.java:190)
         at com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.java:174)
         at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
         ... 28 more

    Caused by: java.net.ConnectException: Connection refused
    Is the Oracle application server running?

  • Hi, i am having trouble with my mac mail account, i cannot send or receive any emails because of the server connection problems. Message says it could not be connected to SMTP server. Thanks in advance for your help.

    Hi, i am having trouble with my mac mail account, i cannot send or receive any emails because of the server connection problems. Message says it could not be connected to SMTP server. Thanks in advance for your help.

    Hello Sue,
    I have an iPad 3, iPad Mini and iPhone 5S and they are all sluggish on capitalisation using shift keys. I hope that Apple will solve the problem because it is driving me crazy.
    I find using a Microsoft Surface and Windows 8 phone, which I also have, work as well as all the ios devices before the ios 7 upgrade.
    It has something to do with the length of time that you need to hold the shift key down. The shift key needs to be held longer than the letter key for the capitalisation to work. For some reason, this is a major change in the way we have learnt to touch type on computers. I am having to relearn how to type!
    Michael

Maybe you are looking for