BAM-00553: Resources start operation for destination jms/BAMTopic failed

Hi ,
im trying to subscribe to a JMS topic created in a different machine(OSB+weblogic) from BAM Enterprise Message sources .Bam is intalled in a different machine along with soa suite.
when i try to subscribe to that topic im facing this issue BAM-00553: Resources start operation for destination jms/BAMTopic failed.
Please suggest me on how to solve this problem.
please share me any notes on how to subscribe to JMS Topic from Bam Enterprise message sources( Note: JMS topic and BAM are availabe in different machines)
Any Suggestions are appreciated!
Thanks,
Karthik

Similar Messages

Error in EMS - Test failed - BAM-00553: Resources start operation

All:
I am setting up a JMS Module with Foreign Server. I have created 2 Modules....the 2nd one is exactly similar as the first one.
I get an error: Test failed - BAM-00553: Resources start operation for destination jms/BAM01Topic failed when I do the Test for the EMS in BAM Architect.
I have restarted BAM Managed Server and also the WLS server...doesn't help.
Here are the config files:
This works:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
<foreign-server name="BAM_EBIZ_FOREIGN">
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name="BAM_OM_EBIZ">
<local-jndi-name>jms/BAMEBIZTopic</local-jndi-name>
<remote-jndi-name>Topics/XX_OM_MONITOR_Q</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="BAM_EBIZ_CF">
<local-jndi-name>jms/BAMEBIZTopicCF</local-jndi-name>
<remote-jndi-name>TopicConnectionFactory</remote-jndi-name>
</foreign-connection-factory>
<initial-context-factory>oracle.jms.AQjmsInitialContextFactory</initial-context-factory>
<jndi-property>
<key>datasource</key>
<value>jdbc/db/EBSAM</value>
</jndi-property>
</foreign-server>
</weblogic-jms>
This doesn't:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://xmlns.oracle.com/weblogic/weblogic-jms" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
<foreign-server name="BAM001_FOREIGN">
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name="BAM001_EBIZ">
<local-jndi-name>jms/BAM01Topic</local-jndi-name>
<remote-jndi-name>Topics/XX_OM_BAM01_Q</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="BAM001_EBIZ_CF">
<local-jndi-name>jms/BAM01TopicCF</local-jndi-name>
<remote-jndi-name>TopicConnectionFactory</remote-jndi-name>
</foreign-connection-factory>
<initial-context-factory>oracle.jms.AQjmsInitialContextFactory</initial-context-factory>
<jndi-property>
<key>datasource</key>
<value>jdbc/db/EBSAM</value>
</jndi-property>
</foreign-server>
</weblogic-jms>
Any help will be greatly appreciated.
Santanu

Deepan,
Here are the exports for EMS
<?xml version="1.0"?>
<OracleBAMExport Version="2025">
<EMS Version="2" Name="FINISH_PAY_HIST" ID="8"^M
<EnterpriseMessageSource version="6"><Description><EMSType>EMST.ORACLE</EMSType><Location><Part1>weblogic.jndi.WLInitialContextFactory</Part1>
<Part2>t3://uslx46c.intranet.local:9001</Part2>
<Part3>jms/BAMEBIZTopicCF</Part3>
<Part4>jms/BAMEBIZTopic</Part4>
<Part5>aiujd16</Part5>
<Part6>###3aYwb6Ww68LmirhFwkn5I8wn7OxTPrkzUqM34Y6s1tI=</Part6>
<Part7>8</Part7>
<Part8>TEMP1</Part8>
<Part9/>
<Part10>/Test DO/FINISH_PAY_HIST</Part10>
<Part11>1</Part11>
<Part12>1</Part12>
<Part13>1</Part13>
<Part14>Yes</Part14>
<Part15/>
<Part16/>
</Location><Fields><Field System="0"><ID>DummyName</ID><Key>off</Key><ProvidersName>DummyName</ProvidersName><DisplayName>DummyName</DisplayName><Type>String</Type><MaxSize>0</MaxSize><PackingSpec Type="XML"><BatchNamespaceURI/><MsgNamespaceURI/><BatchNode/><RootNode>ORDER</RootNode><Path/><DTPattern/><DTLanguage/><DTCountry/><DTVariant/><Fields Type="Tags"><Field Key="true" Type="String"><Name>EXTRACT_WEEK</Name><DisplayName>EXTRACT_WEEK</DisplayName></Field><Field Key="true" Type="String"><Name>EXTRACT_TYPE</Name><DisplayName>EXTRACT_TYPE</DisplayName></Field><Field Key="true" Type="String"><Name>ORG_ID</Name><DisplayName>ORG_ID</DisplayName></Field><Field Key="true" Type="String"><Name>ORDER_NUMBER</Name><DisplayName>ORDER_NUMBER</DisplayName></Field><Field Key="false" Type="String"><Name>RECEIPT_TYPE</Name><DisplayName>RECEIPT_TYPE</DisplayName></Field><Field Key="false" Type="String"><Name>PAYMENT_TYPE</Name><DisplayName>PAYMENT_TYPE</DisplayName></Field><Field Key="false" Type="String"><Name>BUCKET_HIGH</Name><DisplayName>BUCKET_HIGH</DisplayName></Field><Field Key="false" Type="String"><Name>BUCKET</Name><DisplayName>BUCKET</DisplayName></Field><Field Key="false" Type="String"><Name>ELAPSED_TIME</Name><DisplayName>ELAPSED_TIME</DisplayName></Field></Fields></PackingSpec></Field></Fields></Description></EnterpriseMessageSource>^M
</EMS>
</OracleBAMExport>
<?xml version="1.0"?>
<OracleBAMExport Version="2025">
<EMS Version="2" Name="FINISH_PAY_HIST1" ID="9"^M
<EnterpriseMessageSource version="6"><Description><EMSType>EMST.ORACLE</EMSType><Location><Part1>weblogic.jndi.WLInitialContextFactory</Part1>
<Part2>t3://uslx46c.intranet.local:9001</Part2>
<Part3>jms/BAM01TopicCF</Part3>
<Part4>jms/BAM01Topic</Part4>
<Part5>aiujd16</Part5>
<Part6>###ojE/zWMN2kMfDgtjuKomSBqC7TiPgDCGT5rrmlH4yXs=</Part6>
<Part7>8</Part7>
<Part8>TEMP1</Part8>
<Part9/>
<Part10>/Test DO/FINISH_PAY_HIST1</Part10>
<Part11>1</Part11>
<Part12>1</Part12>
<Part13>1</Part13>
<Part14>Yes</Part14>
<Part15/>
<Part16/>
</Location><Fields><Field System="0"><ID>DummyName</ID><Key>off</Key><ProvidersName>DummyName</ProvidersName><DisplayName>DummyName</DisplayName><Type>String</Type><MaxSize>0</MaxSize><PackingSpec Type="XML"><BatchNamespaceURI/><MsgNamespaceURI/><BatchNode/><RootNode>ORDER</RootNode><Path/><DTPattern/><DTLanguage/><DTCountry/><DTVariant/><Fields Type="Tags"><Field Key="true" Type="String"><Name>EXTRACT_WEEK</Name><DisplayName>EXTRACT_WEEK</DisplayName></Field><Field Key="true" Type="String"><Name>EXTRACT_TYPE</Name><DisplayName>EXTRACT_TYPE</DisplayName></Field><Field Key="true" Type="String"><Name>ORG_ID</Name><DisplayName>ORG_ID</DisplayName></Field><Field Key="true" Type="String"><Name>ORDER_NUMBER</Name><DisplayName>ORDER_NUMBER</DisplayName></Field><Field Key="false" Type="String"><Name>RECEIPT_TYPE</Name><DisplayName>RECEIPT_TYPE</DisplayName></Field><Field Key="false" Type="String"><Name>PAYMENT_TYPE</Name><DisplayName>PAYMENT_TYPE</DisplayName></Field><Field Key="false" Type="String"><Name>BUCKET_HIGH</Name><DisplayName>BUCKET_HIGH</DisplayName></Field><Field Key="false" Type="String"><Name>BUCKET</Name><DisplayName>BUCKET</DisplayName></Field><Field Key="false" Type="String"><Name>ELAPSED_TIME</Name><DisplayName>ELAPSED_TIME</DisplayName></Field></Fields></PackingSpec></Field></Fields></Description></EnterpriseMessageSource>^M
</EMS>
</OracleBAMExport>

BAM-00533: Resource open for destination jms/demoQueue failed

I have some BPM processes (11.1.1.5). I need to connect BAM 11.1.1.5.
However, I get BAM-00533 error.
How to fill in
Topic/Queue Connection Factory Name:
Topic/Queue Name.
JNDI Username:
JNDI Password:
The official doc is about how to add BAM to BPEL.
How to configure EMS? Please paste detail steps.
Name: EMS
Owner: weblogic
Created: 6/20/2011 4:30:27 PM
Last modified: 6/20/2011 5:16:11 PM
Status: Test failed - oracle.bam.common.messaging.api.exception.OpenFailedException: BAM-00533: Resource open for destination jms/demoQueue failed.
Initial Context Factory: weblogic.jndi.WLInitialContextFactory.
JNDI Service Provider URL: t3://192.168.1.190:9001.
Topic/Queue Connection Factory Name: weblogic/jms/ConnectionFactory.
Topic/Queue Name: jms/demoQueue.
JNDI Username: weblogic.
JNDI Password: ***************************************************************.
JMS Message Type: TextMessage.
Durable Subscriber Name (Optional): .
Message Selector (Optional): .
Data Object Name: /Samples/myDataObject3.
Operation: Insert.
Batching: No.
Transaction: No.
Start when BAM Server starts: Yes.
JMS Username (Optional): .
JMS Password (Optional): .

Seems like the same issue is still there, that WebLogic does not allow a connection consumer
to be created if it is not running from modules in WebLogic. (see http://dlc.sun.com/pdf//816-5904-10/816-5904-10.pdf section 8.2.4)
Maybe you can try, as a workaround, the synchronous delivery mode of the generic resource adapter,
which is not dependent on the interfaces described in section 8.2.4 of the JMS specification.
deliverytype=synchronousYou can also try posting this in the JMS forum - maybe TomB can put a light on the issue.

Atempt to start OMS for Grid Control 11g fails with - Unexpected error occu

Hello,
I am running Grid Control 11g.
Repository DB is 11.2.0.1
Both the Grid Control and DB server are running in same machine - redhat 5.
When trying to start the oms, this fails with the below error:
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Starting WebTier...
WebTier Successfully Started
Starting Oracle Management Server...
Oracle Management Server is not functioning because of the following reason:
Unexpected error occurred. Check error and log files.
The emctl.log shows the following error which I am unable to debug:
2011-09-13 11:20:05,619 [main] DEBUG oms.StatusOMSCmd processStatusOMS.138 - HTTP port in emgc property file: 7202
2011-09-13 11:20:05,620 [main] DEBUG oms.StatusOMSCmd processStatusOMS.139 - HTTPS port in emgc property file: 7301
2011-09-13 11:20:05,620 [main] DEBUG oms.StatusOMSCmd processStatusOMS.155 - Using http port.
2011-09-13 11:20:05,620 [main] DEBUG oms.StatusOMSCmd processStatusOMS.195 - Attempting to connect to http://<host>.<domain>:7202/em/console/logon/logon
2011-09-13 11:23:05,596 [main] ERROR oms.StatusOMSCmd processStatusOMS.239 - Read timed out
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at HTTPClient.BufferedInputStream.fillBuff(BufferedInputStream.java:206)
at HTTPClient.BufferedInputStream.read(BufferedInputStream.java:126)
at HTTPClient.StreamDemultiplexor.read(StreamDemultiplexor.java:348)
at HTTPClient.RespInputStream.read(RespInputStream.java:147)
at HTTPClient.RespInputStream.read(RespInputStream.java:108)
at HTTPClient.Response.readResponseHeaders(Response.java:1107)
at HTTPClient.Response.getHeaders(Response.java:832)
at HTTPClient.Response.getStatusCode(Response.java:331)
at HTTPClient.RetryModule.responsePhase1Handler(RetryModule.java:92)
at HTTPClient.HTTPResponse.handleResponseImpl(HTTPResponse.java:872)
at HTTPClient.HTTPResponse.access$000(HTTPResponse.java:62)
at HTTPClient.HTTPResponse$2.run(HTTPResponse.java:839)
at HTTPClient.HTTPResponse$2.run(HTTPResponse.java:837)
at HTTPClient.HttpClientConfiguration.doAction(HttpClientConfiguration.java:666)
at HTTPClient.HTTPResponse.handleResponse(HTTPResponse.java:837)
at HTTPClient.HTTPResponse.getStatusCode(HTTPResponse.java:242)
at oracle.sysman.emctl.oms.StatusOMSCmd.processStatusOMS(StatusOMSCmd.java:199)
at oracle.sysman.emctl.wls.OMSController.statusOMS(OMSController.java:867)
at oracle.sysman.emctl.wls.OMSController.startOMS(OMSController.java:606)
at oracle.sysman.emctl.wls.OMSController.main(OMSController.java:213)
2011-09-13 11:23:05,597 [main] INFO wls.OMSController statusOMS.950 - statusOMS finished with result: 9
In emgc.properties, I have MSPORT=7202.
I have used the notes in Metalink 1287904.1, but without resolution.
I am able to connect with sqlplus, with user sysman, without issues. There are no invalid objects under sysman.
emoms.trc shows the following:
2011-09-11 15:51:53,160 [JobWorker 22356:Thread-108] WARN jdbc.ConnectionCache _getConnection.353 - Invalid or Stale Connection found in the Connection Cache
java.sql.SQLException: Invalid or Stale Connection found in the Connection Cache
Thank you for support.
Regards,
Horia
Edited by: horia.berca on Sep 13, 2011 5:29 AM
Edited by: horia.berca on Sep 13, 2011 5:32 AM
Edited by: horia.berca on Sep 13, 2011 5:35 AM
Edited by: horia.berca on Sep 13, 2011 5:45 AM

Hello again;
Check the solution in this: ( and note the multiple versions of oracle it covers )
UNABLE TO FIND GRID INFRASTRUCTURE LISTENER (Doc ID 1483234.1)
Best Regards
mseberg

BAM 11g Not starting properly

Hi,
I installed fmw 11.1.1.4 on 64 bit windows system.Everyting is working fine but while starting BAM managed server its not starting properly,
In em and WL the bam server is showing up state, but in deployed application oracle-bam is showing down state.
Any suggestion...
*I created the domain selecting all dev mode.
*I've one admin server where soa+osb running and one bam managed server.

Here is the excerpts from logs,
bam_server1 log
weblogic.application.ModuleException: [HTTP: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)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.security.Security.runAs(Security.java:61)
     at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
     at oracle.bam.common.security.authentication.BamPrivilegedExceptionAction.execute(BamPrivilegedExceptionAction.java:153)
     at oracle.bam.common.security.authentication.BamPrivilegedExceptionAction.execute(BamPrivilegedExceptionAction.java:121)
     at oracle.bam.server.BamServer$ServiceEntry.start(BamServer.java:1722)
     at oracle.bam.server.BamServer.init(BamServer.java:272)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3154)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:485)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:637)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:246)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
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)
     at oracle.bam.server.BamServer$ServiceEntry$1.run(BamServer.java:1716)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.security.Security.runAs(Security.java:61)
     at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
     at oracle.bam.common.security.authentication.BamPrivilegedExceptionAction.execute(BamPrivilegedExceptionAction.java:153)
     at oracle.bam.common.security.authentication.BamPrivilegedExceptionAction.execute(BamPrivilegedExceptionAction.java:121)
     at oracle.bam.server.BamServer$ServiceEntry.start(BamServer.java:1722)
     at oracle.bam.server.BamServer.init(BamServer.java:272)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:246)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
bam_diagnostic
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.api.MessageConsumerRegistry.onOpenFailedException(MessageConsumerRegistry.java:934)
     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.api.MessageConsumerRegistry.onRecoveryFailedException(MessageConsumerRegistry.java:953)
     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.INVMJMSMessageConsumerRegistry.performOpen(INVMJMSMessageConsumerRegistry.java:132)
     at oracle.bam.common.messaging.base.operation.MessageOperationBase.open(MessageOperationBase.java:1163)
     ... 3 more
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.INVMJMSMessageConsumerRegistry.performOpen(INVMJMSMessageConsumerRegistry.java:133)
     at oracle.bam.common.messaging.base.operation.MessageOperationBase.open(MessageOperationBase.java:1163)
     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:1153)
     ... 1 more
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.JMSMessageConsumerRegistry.acquireResources(JMSMessageConsumerRegistry.java:769)
     at oracle.bam.common.messaging.base.operation.MessageOperationBase.performOpen(MessageOperationBase.java:1211)
     ... 5 more
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)
     at oracle.bam.common.messaging.base.connection.jms.JMSSharedConnectionFactory.getInstance(JMSSharedConnectionFactory.java:55)
     at oracle.bam.common.messaging.api.jms.JMSMessageConsumerRegistry.acquireResources(JMSMessageConsumerRegistry.java:705)

Test failed BAM-00553 Error when integrating B2B with BAM

Hi,
We used the following link to integrate B2B with BAM.
Oracle Fusion Middleware User’s Guide for Oracle B2B 11g.
Monitoring Instance Message Data With Oracle BAM
http://docs.oracle.com/cd/E15586_01/integration.1111/e10229/b2b_bam.htm#CFHJIBHC
server is running on linux machine..
we got the following error when we create Enterprise Message Sources and try to start it.
Name: B2B_EMS
Owner: weblogic
Created: 1/23/2012 9:02:17 AM
Last modified: 1/25/2012 8:37:43 AM
Status: Test failed - BAM-00553: Resources start operation for destination jndi/jms/bamqueue failed.
Initial Context Factory: weblogic.jndi.WLInitialContextFactory.
JNDI Service Provider URL: t3://soahost:9001.
Topic/Queue Connection Factory Name: jms/BAMAQQueueCF.
Topic/Queue Name: jndi/jms/bamqueue.
JNDI Username: .
JNDI Password: .
JMS Message Type: TextMessage.
Durable Subscriber Name (Optional): .
Message Selector (Optional): .
Data Object Name: /Samples/B2B/B2BDO.
Operation: Insert.
Batching: No.
Transaction: No.
Start when BAM Server starts: Yes.
JMS Username (Optional): .
JMS Password (Optional): .
Please suggest with the solution, also provide with any of other sample which defines B2B and BAM Integration.
Regards
Shankar

Hi,
We used the following link to integrate B2B with BAM.
Oracle Fusion Middleware User’s Guide for Oracle B2B 11g.
Monitoring Instance Message Data With Oracle BAM
http://docs.oracle.com/cd/E15586_01/integration.1111/e10229/b2b_bam.htm#CFHJIBHC
server is running on linux machine..
we got the following error when we create Enterprise Message Sources and try to start it.
Name: B2B_EMS
Owner: weblogic
Created: 1/23/2012 9:02:17 AM
Last modified: 1/25/2012 8:37:43 AM
Status: Test failed - BAM-00553: Resources start operation for destination jndi/jms/bamqueue failed.
Initial Context Factory: weblogic.jndi.WLInitialContextFactory.
JNDI Service Provider URL: t3://soahost:9001.
Topic/Queue Connection Factory Name: jms/BAMAQQueueCF.
Topic/Queue Name: jndi/jms/bamqueue.
JNDI Username: .
JNDI Password: .
JMS Message Type: TextMessage.
Durable Subscriber Name (Optional): .
Message Selector (Optional): .
Data Object Name: /Samples/B2B/B2BDO.
Operation: Insert.
Batching: No.
Transaction: No.
Start when BAM Server starts: Yes.
JMS Username (Optional): .
JMS Password (Optional): .
Please suggest with the solution, also provide with any of other sample which defines B2B and BAM Integration.
Regards
Shankar

Need the JNDI name for Destinations present in JMS Modules

Hi all,
I need JNDI`s of all the Destinations present in JMS Modules. With this code i am able to get all info about the JMS Modules, Destinations and as well as information about messages, but still not able to extract JNDI of Destination. Can some one give me pointer on this ?
try {
JMXServiceURL serviceUrl =
new JMXServiceURL(
"service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.runtime");
System.out.println("Connecting to: " + serviceUrl);
Hashtable env = new Hashtable();
env.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES,
"weblogic.management.remote");
env.put(javax.naming.Context.SECURITY_PRINCIPAL, "weblogic");
env.put(javax.naming.Context.SECURITY_CREDENTIALS, "welcome1");
jmxCon = JMXConnectorFactory.newJMXConnector(serviceUrl, env);
jmxCon.connect();
MBeanServerConnection con = jmxCon.getMBeanServerConnection();
Set<ObjectName> mbeans = con.queryNames(queryObjectName, null);
for (ObjectName mbeanName : mbeans) {
String temp = mbeanName.toString();
System.out.println(temp);
String[] mBeanAttributes = {"Name", "DestinationType", "MessagesCurrentCount",
"MessagesPendingCount", "MessagesReceivedCount", "MessagesHighCount" };
queryObjectName = new ObjectName("*:*,Type=JMSDestinationRuntime");
mbeans = con.queryNames(queryObjectName, null);
for (ObjectName mbeanName : mbeans) {
AttributeList attributes = con.getAttributes(mbeanName, mBeanAttributes);
System.out.println((Attribute) attributes.get(0)+ "" +
(Attribute) attributes.get(1)+
(Attribute) attributes.get(2)+
(Attribute) attributes.get(3)+
(Attribute) attributes.get(4)+
(Attribute) attributes.get(5));
String temp = mbeanName.toString();
ObjectInstance inst = con.getObjectInstance(mbeanName);
System.out.println(temp);
finally {
if (jmxCon != null)
jmxCon.close();
But Nowhere i am getting the JNDI of destination Queues or Topics.
Edited by: mdev on Feb 21, 2012 5:21 PM

You are accessing the runtime mbean of a JMS destination. The JNID name of a destination is not available on the runtime destination MBean.
If you are using jms-system-resource to deploy your JMS module, you should be able to access the deployment mbean of the destination. The starting MBean for JMS is JMSSystemResourceMBean in this case.

How to create business operation for starting workflows

How to create business operation for starting workflows from worklist?
When I call methods that implements business operation from java class everything
works fine(wlpi-ejb.jar is required), but when I call business operation from
Studio I can't use classes from wlpi-ejb.jar.

Business operation is called by WLIS. So, I include wlpi-ejb.jar into WLIS classpath.
Studio uses deployed EJB from wlpi-*.jar, I don't know why Studio doesn't see
methods from deployed EJBs when WLIS classpath contains wlpi-ejb.jar.
"Andrew Pitonyak" <[email protected]> wrote:
>
When studio starts, what is your classpath? If you use the included batch
file to start it, then your class path may not include this :-)
Andrew
"Raul" <[email protected]> wrote in message
news:[email protected]..
How to create business operation for starting workflows from worklist?
When I call methods that implements business operation from java classeverything
works fine(wlpi-ejb.jar is required), but when I call business operationfrom
Studio I can't use classes from wlpi-ejb.jar.

[EJB:010112] - error with WLI8.1 Event Generator for foreign JMS/MQ provider

I'm getting following error in weblogic server log when starting a JMS Event generator
to a foreign JMS(MQ5.3) Queue.
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect
every 10 seconds. This log message will repeat every 600 seconds until the condi
tion clears.>
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. The Error was:
[EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted, but the pro
vider defined in the EJB is not transacted. Provider should be transacted if onM
essage method in MDB is transacted.>
My WLI8.1.2 is patched with CR131686_812.zip to support event generator for foreign
JMS destinations. The foreign JMS/MQ provider is configured properly. QueueSend/Receive
were tested fine with JMS java code using local JNDI names of foreign JMS objects.
So we know that foreign Queue is active and accessiable from webLogic.
Anyone run into this? Solution?
Thanks,
Scott

Hi Scott,
I need a transaction from the MDB since I am not using an EJb to pursue the action.
Hence I need to retain the <trans-attribute>Required</trans-attribute> at the
MDB.
Have any answers?
Pradip
"Scott Yen" <[email protected]> wrote:
>
It's resolved.
The MDB automatically created by JMS Event Generator defaults to be deployed
with
“transacted”. That requires the foreign JMS provider to be “XA”.
The deployment descriptor is created as <domain-directory>/WLIJmsEG_<event_gen_name>.jar
e.g. C:\bea812\user_projects\domains\jmsInterop\WLIJmsEG_mqQueueEventGen.jar
Since MQ in the localhost and remote SLUDV18 are not XA-enabled, we had
to manually
change the <container-transaction> section in ejb-jar.xml:
From :
<trans-attribute>Required</trans-attribute>
To:
<trans-attribute>NotSupported</trans-attribute>
"Scott Yen" <[email protected]> wrote:
I'm getting following error in weblogic server log when starting a JMS
Event generator
to a foreign JMS(MQ5.3) Queue.
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. Connection failed after 2 attempts. The MDB will attempt to
reconnect
every 10 seconds. This log message will repeat every 600 seconds until
the condi
tion clears.>
<May 4, 2004 4:44:35 PM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJ
B: mqQueueEventGen is unable to connect to the JMS destination: WAL1021852D_Test
JMSQueue. The Error was:
[EJB:010112]The Message Driven Bean 'mqQueueEventGen' is transacted,
but the pro
vider defined in the EJB is not transacted. Provider should be transacted
if onM
essage method in MDB is transacted.>
My WLI8.1.2 is patched with CR131686_812.zip to support event generator
for foreign
JMS destinations. The foreign JMS/MQ provider is configured properly.
QueueSend/Receive
were tested fine with JMS java code using local JNDI names of foreign
JMS objects.
So we know that foreign Queue is active and accessiable from webLogic.
Anyone run into this? Solution?
Thanks,
Scott

Using JNDI Provider for Oracle JMS Queue

Hello,
I created a JMS Queue in Oracle 9.2.0.1 and would like
a Java client to receive events from the Queue. I am
not running Oracle9iAS. I have access to WebLogic server
7.0 which is also a JNDI provider. Is there a sample code
that shows the steps on how to go about this.
thanks very much for any pointers.

To define an Enterprise Message Source for AS JMS and OJMS in BAM, see Chapter 3 in the BAM Architect's User Guide.
Specifying Settings for Oracle (AS JMS and OJMS)
Settings for Oracle (AS JMS and OJMS) include:
■ Initial Context Factory.
For 10.1.3: oracle.j2ee.rmi.RMIInitialContextFactory
For 10.1.2: com.evermind.server.rmi.RMIInitialContextFactory
■ JNDI Service Provider URL. For standalone use oc4j: ormi://machine_name/
where machine_name is the OC4J installed host, and for production use Application Server: opmn:ormi://<machine_name>:<opmn request port>:home where machine_name is the application server installed host, opmn request port could be found from looking at opmn.xml in <App server install location>/opmn/conf
■ TopicConnectionFactory Name.
java:comp/resource/BAMTTT/TopicConnectionFactories/bam_ttq_tab
■ Topic Name. java:comp/resource/BAMTTT/Topics/bam_ttq
■ JMS Message Type. TextMessage.
■ Durable Subscriber Name. BAMFilteredSubscription
■ Message Selector. Message selector, for example, BAMFilter='true'
■ Client ID. ClientID
You can also refer to:
http://www.oracle.com/technology/products/integration/bam/10.1.3/TechNotes/TechNote_BAM_AQ_Configuration.pdf
Regards, Stephen

Dead message queue - DLQ for foreign JMS providers

Is there a way to configure Error-queue or 'Dead message/letter queue' in MDB listening to foreign JMS provider like JBoss? (Automatic routing of failed messages to error-queue after specified retries to preserve JMS messages)
          I did all the docs from BEA and it doesn't cover this DLQ for foreign JMS providers :). For Weblogic JMS service, DLQ can be configured in the config.xml. But for <ForeignJMSServer> there is no way to configure dead-queue.
          Could some please validate this before I start coding this piece in the application instead of appserver configuration.
          JMS provider is Tibco and JMS destinations are pre-defined and can't/doesn't need to be created
          Thanks in advance.

Interesting idea! But no, there's no facility for redirecting failed foreign provider messages to a DLQ. This is a feature normally supplied by the foreign provider itself.
          Some foreign providers, in addition to WebLogic 9.0 JMS, provide a "redelivery count" property in the message. If the foreign provider provides no automatic DLQ capability, you might be able to leverage this property to have your MDB application code automatically forward messages with high redelivery counts to the DLQ.
          Tom

Injecting JMS Queue / Destination into MDB fails

I am trying to inject a Destination into an EJB3 MDB using
    @Resource(name = "queue/abc/Responses")
    private Destination m_responseQueue;In the ejb-jar.xml file I declare the following
      <message-driven>
            <ejb-name>JobRequestListener</ejb-name>
            <ejb-class>com.abc.backend.jobs.JobRequestListener</ejb-class>
            <message-destination-link>JobRequests</message-destination-link>
            
            <resource-ref>
                <res-ref-name>jms/ConnectionFactory</res-ref-name>
                <res-type>javax.jms.ConnectionFactory</res-type>
                <res-auth>Container</res-auth>
            </resource-ref>
            
            <message-destination-ref>
                <message-destination-ref-name>queue/abc/Responses</message-destination-ref-name>
                <message-destination-type>javax.jms.Queue</message-destination-type>
                <message-destination-usage>Produces</message-destination-usage>
                <message-destination-link>Responses</message-destination-link>
            </message-destination-ref>
        </message-driven>and in weblogic-ejb-jar.xml I add
    <weblogic-enterprise-bean>
        <ejb-name>JobRequestListener</ejb-name>
        <message-driven-descriptor>
            <pool>
                <max-beans-in-free-pool>20</max-beans-in-free-pool>
                <initial-beans-in-free-pool>10</initial-beans-in-free-pool>
            </pool>
            <destination-jndi-name>queue/abc/JobRequests</destination-jndi-name>
        </message-driven-descriptor>
        <transaction-descriptor>
            <trans-timeout-seconds>315</trans-timeout-seconds>
        </transaction-descriptor>
        
        <resource-description>
            <res-ref-name>jms/ConnectionFactory</res-ref-name>
            <jndi-name>jms/ABCConnectionFactory</jndi-name>
        </resource-description>
        
        <resource-description>
            <res-ref-name>queue/abc/Responses</res-ref-name>
            <jndi-name>queue/abc/Responses</jndi-name>
        </resource-description>
    </weblogic-enterprise-bean>Initially I didn't have the resource-description in the weblogic-ejb-jar.xml file, but even after adding it I am still getting the following exception during deployment
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for
this EJB deployment. weblogic.deployment.EnvironmentException:
[EJB:010176]The resource-env-ref 'queue/abc/Responses' declared in the ejb-jar.xml
descriptor or annotation has no JNDI name mapped to it. The resource-ref must
be mapped to a JNDI name using the resource-description element of the
weblogic-ejb-jar.xml descriptor or corresponding annotation.
     at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:639)
     at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:247)
     at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1014)
     at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:908)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1188)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425)By injecting a Queue rather then a destination I can work around this issue, however I would prefer to use a Destination as this allows me to change the behavior of my application without making code changes. It seems like a bug in 10.3 to me.
Edited by: ejb3workshop on Sep 1, 2009 1:44 PM
Edited by: ejb3workshop on Sep 1, 2009 1:59 PM
Edited by: ejb3workshop on Sep 2, 2009 3:11 PM

Because JMS resources by the very nature are "undependable", I think it is usually not advisable to inject JMS resources into an EJB except for MDB source destinations. The problem with injection of JMS resources is that if the JMS resource is not available at the point the EJB is originally deployed/initialized, the EJB deployment/initializaition will fail (except for MDBs, which will still deploy if the source is down, and will automatically retry internally). This is goodness for many types of resources, but since JMS resources are not necessarily always available by their very nature (down for maintenance, in the middle of a migration, initializing later in the boot, etc), most messaging applications should be specifically designed to be robustly handle the failure case during runtime.
Anyhow, EJB3 does not require descriptors.
I haven't fully vetted the following samples, but I think they should be pretty close to correct.
Sample MDB code:
// MDB will still deploy even if the source destination is down (the container will keep retrying internally).
@MessageDriven(mappedName = "Server1Q1",
                        activationConfig = {@ActivationConfigProperty(
                                                      propertyName = "connectionFactoryJndiName",
                                                      propertyValue = "Server1CF")})
public class MyMDB implements MessageListener {
@EJB
private MyStateless myStateless;
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public void onMessage(Message message) {
    System.out.println("Got the message, version 5: "+message);
    myStateless.completeWorkOrder();
Sample injected JMS resources - no resource descriptors needed:
@Stateless(mappedName="StatelessBean")
public class MyStatelessBean implements MyStateless {
int ctr;
@Resource(mappedName="mdbq2")
private Queue queue1;
@Resource(mappedName="cfadmin2")
private QueueConnectionFactory connectionFactory2;
Sample pseudo-code for non-injected JMS resources, no resource descriptors needed:
Eg, instead of
@Resource(mappedName="cfadmin")
private QueueConnectionFactory cf;
Do this:
// note the semi-colon! turns off injection, note the type field -- required
// I'm not sure of exact syntax
//cfadmin is assumed to be the JNDI name if the
// JNDI name isn't specified in another parameter...
@Resource(mappedName="cfadmin", type="javax.jms.QueueConnectionFactory");
// this is not injected now
// cache cf for re-use (performance)
private QueueConnectionFactory cf;
@Resource
private SessionContext sctx; // inject the session ctx
And in the source code itself, do this:
   int tryCount == 3;
   while (cf != null) {
     try {
       // not quite sure if this is the righ syntax, but I think "java:/comp/env" prefix
       // isn't needed for the new EJB3.0 session context
       cf = sctx.lookup("cfadmin"); //cfadmin is mappedname for resource above
     } catch (NNN n) { // don't know the exact exception
       if (--tryCount == 0) throw n;
       sleep 3 seconds // don't want to retry in a tight loop
Tom

17076 : Invalid operation for read only resultset

Hi,
I am trying to update database table through java jdbc application.
But while running the program i am getting the error message " Invalid operation for read only resultset: updateString " with error code 17076.
My program is given below :
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
public class Misc2 {
public static void main(String[] args) {
Connection con = null;
Statement stmt = null;
ResultSet rs = null;
try {
con = JDBCUtil.getOracleConnection();
stmt = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
String query = "select * from employees";
rs = stmt.executeQuery(query);
while (rs.next()) {
String fname = rs.getString(3);
if (fname.equalsIgnoreCase("Elmer")) {
rs.updateString(3, "Mark");
rs.updateString(2, "Robert");
break;
} catch (SQLException ex) {
System.out.println("error code : " + ex.getErrorCode());
System.out.println("error message : " + ex.getMessage());
} finally {
JDBCUtil.cleanUp(con, stmt);
****JDBCUtil Class****
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.Statement;
public class JDBCUtil {
public static Connection getOracleConnection(){
Connection con = null;
try{
// Load the driver
Class.forName("oracle.jdbc.driver.OracleDriver");
//Establish Connection
con = DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:XE","ex","ex");
}catch(Exception ex){
ex.printStackTrace();
return con;
public static void cleanUp (Connection con , Statement stmt){
// Release the resource
try{
if(con != null){
con.close();
if(stmt != null){
stmt.close();
}catch(Exception ex){
ex.printStackTrace();
Please help me to fix this issue.

>
But while running the program i am getting the error message " Invalid operation for read only resultset: updateString " with error code 17076.
>
Your result using 'SELECT *' is not updateable. Gimbal2 was pointing you in the right direction. You have to specify the columns in the select list to get an updateable result set.
You also need to use 'updateRow()' to update the database and have a commit somewhere to keep the results.
This code works for me. Note that I added an explicit SELECT list, the 'updateRow()' method and an explicit COMMIT.
    try {
        con = getOracleConnection();
        stmt = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
//        String query = "select * from employees";
        String query = "select first_name from employees"; -- added explicit SELECT list
        rs = stmt.executeQuery(query);
        while (rs.next()) {
            String fname = rs.getString(1);
            if (fname.equalsIgnoreCase("Adam")) {
                rs.updateString(1, "Mark");
                rs.updateRow();                                    -- need this statement to actually update the database
//                rs.updateString(2, "Robert");
                break;
        con.commit(); -- added explicit commit for testing
    } catch (SQLException ex) {See Performing an UPDATE Operation in a Result Set in the 'Updating Result Sets' section of the JDBC Developer's Guide and Reference
http://docs.oracle.com/cd/B28359_01/java.111/b31224/resltset.htm#i1024720
As gimbal2 also alluded it is considered poor practice to use column numbers to perform result set operations when you don't know for certain what column a given number refers to. Before people start jumping all over that statement let me clarify it. The key part is KNOWING what column you are referencing. It is more performant to access result column columns by column number rather than by column name since the methods that take a column name call the integer method under the covers anyway but have to search the array of column names in order to get the column number.
With your query (SELECT *) there is no way to be sure the column order is the same since the table could be redefined with the columns in a different order or certain columns having been deleted. So for performance LOOP processing column numbers are used inside the loop but those column numbers are determined by using the metadata BEFORE the loop to convert column names to column numbers.
That way you code (BEFORE the loop) can use column names but you use a set of integer variables (one for each column) for the actual access inside the loop.

Failures were detected while initiating start task for application 'em'

Hello there,
I'm facing a problem here that I'm not able to resolve it.
This is the third time I reinstalled the WebLogic Sever (WebLogic Server Version: 10.3.5.0) and I'm getting the same error.
After installing the WebLogic Server, everything goes fine, I can access /em, /console, /analytics.
The problem is when I create a WebService (with JDeveloper Studio 11.1.2.3.0). After deploying the WebService and restart WebLogic Server, the /em deployment can't start.
I get this error while accessing to localhost:7001/em:
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
When I try to start it from the console I get this error (it doesn't matter if I start it Servicing all requests or Servicing only administration requests):
java.lang.NoClassDefFoundError: javax/faces/application/ProjectStage
Errors were encountered while performing this operation.
Here is the log file:
<Mar 27, 2013 12:24:43 PM GMT-03:00> <Warning> <Deployer> <BEA-149004> <Failures
were detected while initiating start task for application 'em'.>
<Mar 27, 2013 12:24:43 PM GMT-03:00> <Warning> <Deployer> <BEA-149078> <Stack tr
ace for message 149004
java.lang.NoClassDefFoundError: javax/faces/application/ProjectStage
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.getDeclaredFields(Class.java:1743)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:1024)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:1017)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoClassDefFoundError: javax/faces/application/ProjectStage
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.getDeclaredFields(Class.java:1743)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:1024)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:1017)
Truncated. see log file for complete stacktrace
>
I really don't know why /em can't start after deploying a WebService.
Thanks in advance, Max.

Hello there,
I'm facing a problem here that I'm not able to resolve it.
This is the third time I reinstalled the WebLogic Sever (WebLogic Server Version: 10.3.5.0) and I'm getting the same error.
After installing the WebLogic Server, everything goes fine, I can access /em, /console, /analytics.
The problem is when I create a WebService (with JDeveloper Studio 11.1.2.3.0). After deploying the WebService and restart WebLogic Server, the /em deployment can't start.
I get this error while accessing to localhost:7001/em:
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
When I try to start it from the console I get this error (it doesn't matter if I start it Servicing all requests or Servicing only administration requests):
java.lang.NoClassDefFoundError: javax/faces/application/ProjectStage
Errors were encountered while performing this operation.
Here is the log file:
<Mar 27, 2013 12:24:43 PM GMT-03:00> <Warning> <Deployer> <BEA-149004> <Failures
were detected while initiating start task for application 'em'.>
<Mar 27, 2013 12:24:43 PM GMT-03:00> <Warning> <Deployer> <BEA-149078> <Stack tr
ace for message 149004
java.lang.NoClassDefFoundError: javax/faces/application/ProjectStage
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.getDeclaredFields(Class.java:1743)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:1024)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:1017)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NoClassDefFoundError: javax/faces/application/ProjectStage
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
at java.lang.Class.getDeclaredFields(Class.java:1743)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:1024)
at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAn
notationProcessor.java:1017)
Truncated. see log file for complete stacktrace
>
I really don't know why /em can't start after deploying a WebService.
Thanks in advance, Max.

Daily operations for BW?

Hi ~
I'm learning BW 3.5 now and I would like to know what are the daily operations for a BW person. Also, could you provide me with a list of T-Codes and maybe a brief description of what each of them do?
Thanks in advance,
Denny.
P.S. Since I'm learning version 3.5, is there a big difference with BI 7?

List of tcodes:
Again search forum before you post....
BALE Area Menu for Administration
CMOD Enhancements
DB02 Tables and Indexes Monitor
DB12 DBA Backup Logs
DB13 DBA Planning Calendar
DB16 Display DB Check Results
FILE Cross-Client File Names/Paths
LISTCUBE List viewer for InfoCubes
LISTSCHEMA Show InfoCube schema
PFCG Role Maintenance
RRMX Start the Business Explorer Analyzer
RS12 Overview of master data locks
RSA1 BW Administrator Workbench
RSA3 Extractor Checker
RSA5 Install Business Content
RSA7 BW Delta Queue Monitor
RSB1 Display authorization object
RSBBS Maintaining BW Sender-Receiver
RSBMO2 Open Hub Monitor
RSBO Open Hub Maintenance
RSBROWSER BW Browser
RSD1 Characteristic maintenance
RSD2 Maintenance of key figures
RSD3 Maintenance of units
RSD4 Maintenance of time characteristics
RSD5 Internal: Maint. of Tech. Chars
RSDCUBE Start: InfoCube editing
RSDCUBEM Start: InfoCube editing
RSDDV Maintaining Aggregates
RSDIOBCM Start: InfoObject catalog editing
RSDODS Initial Screen: ODS Object Processing
RSFH Test Transaction Data Extractors
RSIMG BW IMG
RSKC Maintaining the Permitted Extra Chars
RSMD Extractor Checker
RSMON BW Administrator Workbench
RSO2 Oltp Metadata Repository
RSPC Process Chain Maintenance
RSPCM Monitor daily process chains
RSQ02 Maintain InfoSets
RSQ10 SAP Query: Role Administration
RSQ11 InfoSet Query: Web reporting
RSRQ Data Load Monitor for a Request
RSRT Start of the report monitor
RSRTRACE Set trace configuration
RSRV Analysis and Repair of BW Objects
RSSM Authorizations for Reporting
RSU1 Create update rules
RSU2 Change update rules
RSU3 Display update rules
RSZC Copying Queries between InfoCubes
RSZDELETE Deletion of query objects
RSZV Call up of view V_RSZGLOBV
RZ10 Maintain Profile Parameters
RZ11 Profile Parameter Maintenance
RZ20 CCMS Monitoring
SALE Display ALE Customizing
SAPBWNEWS PRINT SAP BW NEWS
SBIW BIW in IMG for OLTP
SCC4 Client Administration
SCCL Local Client Copy
SE01 Transport Organizer (Extended)
SE09 Transport Organizer
SE10 Transport Organizer
SE11 ABAP Dictionary
SE14 Utilities for Dictionary Tables
SE16 Data Browser
SE36 Logical Database Builder
SE37 ABAP Function Modules
SE38 ABAP Editor
SE84 R/3 Repository Information System
SE91 Message Maintenance
SGEN SAP Load Generator
SM04 User List
SM12 Display and Delete Locks
SM13 Administrate Update Records
SM30 Call View Maintenance
SM31 Call View Maintenance Like SM30
SM36 Schedule Background Job
SM37 Overview of job selection
SM38 Queue Maintenance Transaction
SM50 Work Process Overview
SM51 List of SAP Systems
SM59 RFC Destinations (Display/Maintain)
SM62 Display/Edit Events
SM64 Trigger Event
SM66 System wide Work Process Overview
SNUM Number Range Driver
SPAD Spool Administration
SPAM Support Package Manager
SPRO Customizing - Edit Project
ST02 Setups/Tune Buffers
ST03 Performance, SAP Statistics, Workload
ST04 DB Performance Monitor
ST22 ABAP dump analysis
STMS Transport Management System
SU01 User Maintenance
SU1 Maintain Own User Address
SWU3 Automatic Workflow Customizing
WE07 IDoc statistics
WE20 Partner Profiles
WE21 Port definition
By no means, above is a complete list of transaction. SAP BW system contains many more standard
transactions. In addition to which, there would be some useful custom transactions as well in any
ongoing production system.
Complete list of transactions in your system can be found in SAP table
TSTC and TSTCT (Descriptions).
Also, one can find them, Using SE84 -> Other Objects -> Transactions.

BAM-00553: Resources start operation for destination jms/BAMTopic failed

Similar Messages

Maybe you are looking for