Message Bridge  error:Connection Factory

Hi
          I am trying to build a Message Bridge accross two domains which are using the same version of Weblogic Server(8.1).
          I am running into this error..
          <Warning> <Connector> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = , user name =) on createManagedConnection.>
          Please could anybody help me with this.

Hi,
          This exception indicates a failure to establish a JNDI context for either the source or target destination host. Check if the the bridge's configured URLs for both are correct. I'm not 100% sure, but it is likely that no URL need be configured for destination's that are in the same cluster as the bridge.
          For more information, I suggest looking at the Messaging Bridge FAQ, which contains some troubleshooting tips. You can find a link to it here:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          Tom Barnes, BEA

Similar Messages

  • MQ 6 WLS 9.2 JMS Message Bridge Error

    I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2 collocated on the same server following the BEA example:
              1.Create local queue on MQ
              2.Bind queue using JMSAdmin
              3.Create JMS bridge betwen a source destination using JNDI name in #2 and a local WLS queue.
              Here is the WLS config:
              <messaging-bridge>
              <name>MQ-WLSBridge</name>
              <target>adminServer</target>
              <source-destination>MQ-WLSSource</source-destination>
              <target-destination>MQ-WLSTarget</target-destination>
              <selector></selector>
              <quality-of-service>Exactly-once</quality-of-service>
              <qos-degradation-allowed>true</qos-degradation-allowed>
              <durability-enabled>true</durability-enabled>
              <idle-time-maximum>60</idle-time-maximum>
              <async-enabled>true</async-enabled>
              <started>true</started>
              <preserve-msg-property>false</preserve-msg-property>
              </messaging-bridge>
              <jms-bridge-destination>
              <name>MQ-WLSTarget</name>
              <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
              <classpath></classpath>
              <connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
              <connection-url>t3://localhost:7005</connection-url>
                   <destination-jndi-name>WLSMessageQueue</destination-jndi-name>
              </jms-bridge-destination>
              <jms-bridge-destination>
              <name>MQ-WLSSource</name>
              <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
              <classpath></classpath>
              <connection-factory-jndi-name>QCF</connection-factory-jndi-name>
              <initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
              <connection-url>file:///usr/mqm/java/jndi</connection-url>
              <destination-jndi-name>MQMessageQueus</destination-jndi-name>
              </jms-bridge-destination>
              I used a standalone JMS client and was able to connect to the MQ queue using the above JNDI name, factory so the MQ side was set up properly.
              When I start up WLS, I saw that
              <The messaging bridge "MQ-WLSBridge" has been successfully deployed.>
              and the exception:
              <MessagingBridge> <BEA-200042> <Bridge MQ-WLSBridge failed to connect to the source destination and will try again in 20 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: javax.resource.ResourceException: Failed to start the connection
                   at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1458)
                   at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1438)
                   at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:403)
                   at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:242)
                   at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
                   at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
                   at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
                   at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1057)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:346)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:294)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:277)
                   at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:606)
                   at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:271)
                   at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
                   at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
                   at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
                   at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseConnectionFactory.java:92)
                   at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:809)
                   at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1042)
                   at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
                   at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
                   at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
              )>
              There is no error in the MQ logs. What is the problem?
              CS

    C S <> wrote:
              > I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2
              > collocated on the same server following the BEA example: 1.Create local
              > queue on MQ 2.Bind queue using JMSAdmin
              > 3.Create JMS bridge betwen a source destination using JNDI name in #2 and
              > a local WLS queue.
              >
              > Here is the WLS config:
              > <messaging-bridge>
              > <name>MQ-WLSBridge</name>
              > <target>adminServer</target>
              > <source-destination>MQ-WLSSource</source-destination>
              > <target-destination>MQ-WLSTarget</target-destination>
              > <selector></selector>
              > <quality-of-service>Exactly-once</quality-of-service>
              > <qos-degradation-allowed>true</qos-degradation-allowed>
              > <durability-enabled>true</durability-enabled>
              > <idle-time-maximum>60</idle-time-maximum>
              > <async-enabled>true</async-enabled>
              > <started>true</started>
              > <preserve-msg-property>false</preserve-msg-property>
              > </messaging-bridge>
              >
              > <jms-bridge-destination>
              > <name>MQ-WLSTarget</name>
              >
              <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
              > <classpath></classpath>
              >
              <connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
              > <connection-url>t3://localhost:7005</connection-url>
              > <destination-jndi-name>WLSMessageQueue</destination-jndi-name>
              > </jms-bridge-destination>
              > <jms-bridge-destination>
              > <name>MQ-WLSSource</name>
              >
              Hello,
              First of all, your classpath doesn't seem to be correct. You need to add the
              MQ jars in the bridge classpath. (DONT use the server classpath for
              this!!!)
              Secondly, enable debugging in Weblogic, which will give you some
              information: -Dweblogic.Debug.DebugMessagingBridgeStartup=true -Dweblogic.Debug.DebugMessagingBridgeRuntime=true -Dweblogic.Debug.DebugMessagingBridgeRuntimeVerbose=true
              IF you have more questions, pls reply also be mail.
              Bart
              Schelstraete Bart
              [email protected]
              http://www.schelstraete.org
              http://www.linkedin.com/in/bschelst

  • Error : Connection factory has been stopped

    Hi ,
    i Have a JPA/Toplink application to be depolyed on OAS 10.1.3.3 , i defined a DataSource on the Application Server , but iam getting this error when iam trying to run my application :
    Caused by: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection
    factory has been stopped.
    at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:259)
    at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:142)
    at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:127)
    at oracle.toplink.essentials.jndi.JNDIConnector.connect(JNDIConnector.java:130)
    Thanks
    Message was edited by:
    mr_jaber

    well as always...nothing works like restart of the server. Issue resolved.

  • Data import from EBS failed via FDMEE in fdm . Getting error message as "Error connecting to AIF URL.

    FDM Data import from EBS failed via FDMEE after roll back the 11.1.2.3.500 patch . Getting below error message in ERPI Adapter log.
    *** clsGetFinData.fExecuteDataRule @ 2/18/2015 5:36:17 AM ***
    PeriodKey = 5/31/2013 12:00:00 AM
    PriorPeriodKey = 4/30/2013 12:00:00 AM
    Rule Name = 6001
    Execution Mode = FULLREFRESH
    System.Runtime.InteropServices.COMException (0x80040209): Error connecting to AIF URL.
    at Oracle.Erpi.ErpiFdmCommon.ExecuteRule(String userName, String ssoToken, String ruleName, String executionMode, String priorPeriodKey, String periodKey, String& loadId)
    at fdmERPIfinE1.clsGetFinData.fExecuteDataRule(String strERPIUserID, String strDataRuleName, String strExecutionMode, String strPeriodKey, String strPriorPeriodKey)
    Any help Please?
    Thanks

    Hi
    Getting this error in ErpiIntergrator0.log . ODI session ID were not generated in ODI / FDMEE. If I import from FDMEE its importing data from EBS.
    <[ServletContext@809342788[app:AIF module:aif path:/aif spec-version:2.5 version:11.1.2.0]] Servlet failed with Exception
    java.lang.RuntimeException
    at com.hyperion.aif.servlet.FDMRuleServlet.doPost(FDMRuleServlet.java:76)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

  • Message Bridge error "Received message with no URI property"

    I have created a message bridge between two weblogic JMS servers on different domains.
              Message bridge has source and destinations.
              I have tested each ques seperately with MDB deployed on each server.
              When i am putting message on source que then i am getting this error "Received message with no URI property"
              It would be grat help if some could tell me what might be going wrong.
              Thanks
              Akash

    Hi,
              This exception indicates a failure to establish a JNDI context for either the source or target destination host. Check if the the bridge's configured URLs for both are correct. I'm not 100% sure, but it is likely that no URL need be configured for destination's that are in the same cluster as the bridge.
              For more information, I suggest looking at the Messaging Bridge FAQ, which contains some troubleshooting tips. You can find a link to it here:
              http://dev2dev.bea.com/technologies/jms/index.jsp
              Tom Barnes, BEA

  • Message Bridge Error

    Hi,
    I am getting this Warning for every 2 mins. i was using this for 4 yrs on HP-UX . few months back i moved this to Linux and working good. today i did reboot start getting this Warning
    <Jan 12, 2010 6:29:53 PM GMT> <Warning> <MessagingBridge> <BEA-200026> <Bridge "TestInboundQueue" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was javax.jms.IllegalStateException: MQJMS3033: QueueReceiver is closed.)>
    Thanks
    Subba
    Edited by: Subba R Kancharla on Jan 12, 2010 4:33 PM

    Have you consulted the bridge troubleshooting guide in the bridge documentation?
    Also check to see if there was a change to the MQ version and/or configuration...
    Tom

  • JMS Messaging Bridge Problems with WLS 8.1 sp2

              Thank you in advance for your help.
              I am trying to configure a JSM Messaging Bridge to connect an MQ Q to a Weblogic
              Q. I have this working wonderfully in an environment without clustering but once
              I try to deploy to a cluster, I am having two major problems.
              1) When the managed servers are restarted, the messaging bridges immediately complain
              about not being able to find the resource adaptor. After I manually un-target
              the messaging bridge from the cluster and re-target them, they find the resource
              adaptor but cannot connect to the source... which leads to my next problem.
              2) The messaging bridges cannot connect to the source destination whether it is
              an MQ Q or a Weblogic JMS Q does not matter. Here are the log entries that I
              see relative:
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Got Notification:weblogic.management.AttributeAddNotification:
              Deployments from <null> to [Caching Stub]Proxy for eBusDev02:Location=secaServer01,Name=seca_OES_ADV_REPLY
              Messaging Bridge,Type=MessagingBridgeConfig - weblogic.management.AttributeAddNotification[source=eBusDev02:Location=secaServer01,Name=secaServer01,Type=ServerConfig].>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! creating bridge seca_OES_ADV_REPLY Messaging
              Bridge.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
              is deployed as a migratable.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Initializging bridge seca_OES_ADV_REPLY Messaging
              Bridge as a migratable.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
              source configurations are:
              AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              Classpath=null
              ConnectionURL = file:/e:/private/JNDI/eBusDev02
              DestinationType = Queue
              DestinationJNDIName = jms.oes.MQ-ADV-REPLYQ
              InitialContextFactory = com.sun.jndi.fscontext.RefFSContextFactory
              ConnectionFactoryJNDIName = jms.oes.MQ-QCF
              .>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
              target configurations are:
              AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              Classpath=null
              ConnectionURL = t3://30.135.10.63:8103,30.135.10.63:8104
              DestinationType = Queue
              DestinationJNDIName = jms/oes/ADV-REPLYQ
              InitialContextFactory = weblogic.jndi.WLInitialContextFactory
              ConnectionFactoryJNDIName = jms/oes/QCF
              .>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
              is successfully initialized.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
              has been successfully initialized as a migratable.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Activating bridge seca_OES_ADV_REPLY Messaging
              Bridge.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
              has been successfully activated..>
              ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200033>
              <Bridge "seca_OES_ADV_REPLY Messaging Bridge" is obtaining connections to the
              two adapters.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006>
              <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
              Getting source connection.>
              ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
              <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200042>
              <Bridge seca_OES_ADV_REPLY Messaging Bridge failed to connect to the source destination
              and will try again in 15 seconds. (java.lang.NullPointerException)>
              I know the queues are up and I am pretty sure my MQ client configuration is correct.
              Is there anyway to get more information about the NullPointerException or the
              error being encountered?
              

    Given that you have ruled out message backlogs, my first suspicion is that the leak has something to do with connection allocation. Does JMS stats reveal an application generated connection leak? Check to see if the current number of connections/sessions stays steady.
              If this doesn't help, you can use a third party tool like OptimizeIt to get periodic snap-shots of memory usage and identify the leaked object (or create a reproducer and have customer support do it). A possible work-around is to modify your app to pool JMS connections/sessions for re-use - greatly reducing the number of connections created per day.
              Tom

  • Error connecting using JCO.Client: null

    Hi,
    I created a WD app which uses  the RFC FM.  I followed How-To-build-webdynpro.pdf document to create the WD and trying to deploy and run, I see the view page but when I trigger the action via button UI element I get following error as exception in the try catch block of execute method
    In the NWA I see
    Could not create JCOClientConnection for logical System: 'WD_MODELDATA_DEST' - Model
    An exception has occurred: Erorr accessing cache [region]='XCM_SESSION_SCOPE'.
    [EXCEPTION]
    com.sap.isa.core.cache.Cache$Exception: Cannot return access for region 'XCM_SESSION_SCOPE'. Cache is not ready
    I'm using following existing JCO definition by configuring them with correct parameters.  Tested them successfully
    WD_RFC_METADATA_DEST
    WD_MODELDATA_DEST
    What am I missing?  In SM04 tcode I see 2 connections are opened with 2 Megabyte not released for a long time.  I think if connections are released correctly it should drop to 1 megabyte.  Is there anything that I need to do just after execute method as shown below (I have replaced function module with <FM> in below code)
    try {
             wdContext.node<FM>_Input().current<FM>_Get_InputElement().modelObject().execute();
         } catch(Exception exception) {
              msgMgr.reportException(exception.getLocalizedMessage(), false);
          wdContext.nodeOutput().invalidate();
          msgMgr.reportSuccess("Success");
    The error is in the catch block which is displayed on the view page.
    Thanks
    Praveen
    I modified the above code and put in finally block to close the connections as follows, please let me know if this is OK.  I still get error message as "Error connecting using JCO.Client: null" but no additional connections in the SM04 after adding finally block.
    try {
             wdContext.node<FM>_Input().current<FM>_Get_InputElement().modelObject().execute();
         } catch(Exception exception) {
              msgMgr.reportException(exception.getLocalizedMessage(), false);
         }finally {
              // disconnect the connection
              wdContext.<FM>_Get_InputElement().modelObject().modelInstance().disconnectIfAlive();     
    Edited by: Praveen11 on Oct 5, 2009 9:06 AM

    Thanks Satish.
    The issue is resolved.  I think it was to do with permission, as I was running directly from NWDS deploy and run the session didn't have proper authorisation or something that was causing this error.
    When I copy pasted the URL in the correct browser session window I got no error and function module was successfully executed.   However the issue now is that values are not showing up in the view may be to do with mapping context or model  I'll review and post back as different thread.
    Thanks
    Praveen

  • Foreign JMS Server vs Messaging bridge

    Could any body tell me which one is the best Whether Foreign JMS Server or Messaging bridge for connecting Weblogic to IBM MQ Series.I am trying to use foreign jms server but i dont know how to post the message to that queue i created in foreign jms server..

    Hi,
              For sending messages non-transactionally, foreign JMS server is sufficient. For sending messages transactionally using standard JTA transactions, the simplest way is to send them on the server and reference the foreign JMS through an EJB resource reference. See the the following FAQ for a walk-through of the various options, including guidance on when to use a bridge:
              http://e-docs.bea.com/wls/docs81/faq/interop.html
              Tom

  • Using Bridge CS5 exporting to flickr get error message "Unable to connect to Flickr, please check your internet connection and try again."?

    using Bridge CS5 to exporting to flickr, but get error message "Unable to connect to Flickr, please check your internet connection and try again."  please help?

    I'm experiencing the same problem. Don't think I can help, but maybe I can offer an explanation. It looks as if Flickr has changed their API and Adobe will need to update the export plugin to comply to get it working again. I found this announcement on Flickr:
    Flickr: The Help Forum: [Official Thread] Flickr API switching to https-only on June 27th, 2014!

  • HT3728 When I reconnect my Time Capsule after a factory reset, the Airport Utility shows ther message"Unexpected error. Try again." I also get this if I redo the factory reset.

    The Time Capsule is not providing a wireless connection.
    When I reconnect my Time Capsule after a factory reset, the Airport Utility shows ther message"Unexpected error. Try again." I also get this if  I cancel the Airport Utility app and restart it. I performed the factory reset again, restarted the Airport Utility and received the same error. What are the steps to debug and fix the wireless problem?
    My Time Capsule is connected to my FIOS router and to my Mac Mini. I am still able to connect to the Internet from the Mini via ethernet. It seems that the Time Capsule acts as a bridge for the ethernet connections between Internet to FIOS, FIOS to Time Capsule, and Time Capsule to Mac Mini.

    Which model TC is this? The A1xxx number from the base please.
    Try the setup in full isolation from the network.. so unplug the TC from the network.. and turn off wireless in the mini.. so you have mini--ethernet--lan port TC.. and nothing else.
    Do the factory reset.
    Now check if TC comes up in airport utility..
    If it fails, turn on ipv6 local link.. if you are using 6.3 utility this could be necessary.
    Still fails, try loading the v5 utility.. you will need to plug the computer back into the FIOS to get internet. Then depending on OS.. Lion according to your profile.. you can just down the utility.. ML takes more steps.
    See below.
    Do you have an iphone or ipad.. download the airport utility app and use those for the setup.. that can sometimes work better.
    How to load 5.6 into ML.
    1. Download 5.6 for Lion.
    http://support.apple.com/kb/DL1482
    Click to open the dmg but do not attempt to install the pkg.. it won't work anyway.
    2. Download and install unpkg.
    http://www.timdoug.com/unpkg/
    Run unpkg on the desktop.. it is very simple.. drag the AirPortUtility56.pkg file over to unpkg.. and it will create a new directory of the same name on the desktop.. drill down.. applications utilities .. there lo and behold is Airport utility 5.6 .. drag it to your main utilities directory or just run it from current location.
    You cannot uninstall 6.1 (now 6.2 if you updated) so don't try.. and you cannot or should not run them both at the same time.. so just ignore the toyland version.. the plastic hammer.. and start using 5.6.. a real tool.
    For screen shots see this post.
    https://discussions.apple.com/thread/4668746?tstart=0

  • Error when creating a new JMS connection factory in GlassFish V3 b57

    When I use the admin console and try to create a new JMS connection factory in GlassFish V3 b57, the operation fails with the error message
    An error has occurred: Can't find ConfigModel.Property for attr -connection-validation-required on interface com.sun.enterprise.config.serverbeans.ConnectorConnectionPool
    Should I better report this in the GlassFish news forum (http://forums.java.net/jive/forum.jspa?forumID=56&start=0)?
    p.s. I launch the admin console from within NetBeans 6.7.1 (the server started before the IDE). WIth version b 56, creating a JMS connection factory worked fine.
    Best regards,
    Michael Justin

    This bug does not apear in the nightly build (b58) now so everything looks fine again.
    Greetings,
    Michael

  • Error occured in Messaging bridge in weblogic to MQ Series

    Hi,
    I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
    <Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
    ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
    locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
    --Please give me the suggestion to fix this.
    Thanks in Advance,
    Sureshkannan Nagarajan

    Hi,
    I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
    <Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
    ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
    locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
    --Please give me the suggestion to fix this.
    Thanks in Advance,
    Sureshkannan Nagarajan

  • Error occured in Message Bridging in Weblogic to MQ Server

    Hi,
    I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
    <Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
    ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
    locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
    --Please give me the suggestion to fix this.
    Thanks in Advance,
    Sureshkannan Nagarajan

    Hello Priya
    If u r loading thru flat file
    1. Check the correct path in infopackage
    2. Check if it is opened,if it is then close it and run package again
    If loading thru R/3
    1. Check DS is not opened in change mode
    2. Check if RSA3 is able to extract data...if it is then check in RSA7 and chk IDOC status...
    3. Are you running init..then make sure no document is posted in R/3 side...
    Thanks
    Tripple k

  • Error saving JCA Connection factory in PI NWA

    Hi All,
    I am facing an  issue in SAP PI NWA for creating a JCA connection factory so that I can use the user module to convert IDOCs to flat file. we are on SAP PI 7.11 sp06....
    error details : CF_XD1_180 failed due to: Can not add connection factory '', Reason: . See the log file for more details.
    The logs details : com.sap.engine.services.connector.exceptions.ConnectorException: Connector remote administration failed, reason: "Can not set authentication user store "null" in security context "CF_XD1_180" for connector "CF_XD1_180" in application "sap.com/tc~sapjra".".
    at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.addComponent(ConnectorContainerImpl.java:1005
    i posted this  in SAP PI forum also...
    Error saving connection factory
    Regards
    ashutosh r

    Hello Carme,
    From the error , I can see that the name of the JCA Connection Factory that you are trying to create in NWA is: "MRD_300".
    This beautiful blog by William will surely help you rectify the problem.
    /people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
    Kindly check if you have done the following in your configuration:
    1. Copy and create new dependent JCA Connection Factory from the JCA resource: "SAPJavaResourceAdapter15" 
    2. You have to go to the "Configuration Properties" tab (and not Security tab) of your JCA connection Factory (MRD_300) to enter the credentials that will be used by this CF. Make sure that you enter the details properly. Eg. In your case, just check if the password is entered.
    3. Also, check if the JCA resource "SAPJavaResourceAdapter15" is up and running (green traffic light). Else, restart the corresponding Java Service from NWA -> Operations Management -> Start & Stop -> Java Services
    I hope this should solve your problem.
    Regards, Gaurav.

Maybe you are looking for

  • How can I insert large text captions in photos?

    How can I add viewable captions to photos? I often send reports with a number of photos attached in a PDF file in Adobe Acrobat Standard. I would like the text comments in the photos to be viewable as soon as someone opens the adobe pdf file and look

  • Java classes not Found in Webdynpro

    hi, I have this problem. Suppose i have a value node "Emp". If i am creating a supply function for it, I cannot get the 'IEmpNode' or 'IEmpElement' . Even if i type it, it gives error. However, if i create a method, these classes are present in the "

  • How to contact mac air to iPad

    I bought an Ipad yesterday, does someoneknow how to connect ipad the mac air

  • Monitor displaying bright white message when it is about to enter power saving.

    Is there a way to disable the bright white "monitor is about to sleep" on the Paviliion 23x1? It's blinding at night. If there's no way to do this the screen is going to be given away or put in the bin given that it was only £100 or so. The iritation

  • Why does InDesign keep freezing?

    InDesign is being impossible. I can't place a simple logo in an eBook because the program freezes. I am using CS6 on a Mac which is running Mavericks. My guess is that fonts are the culprit. This is what Console shows during the freez ups: 12/10/13 3