JMS Unable to resolve 'weblogic.jms.TempDestinationFactory'  error!

          We are running an application within the Weblogic 7.x EJB Framework. While trying
          to connect to the application from our GUI I get the following error. **... Unable
          to resolve 'weblogic.jms.TempDestinationFactory' Resolved: 'weblogic.jms' Unresolved:'TempDestinationFactory'
          ; We have configured our JMS server with two topics - one of which is used for
          persistent storage (i.e has the 'store' configuration attribute set to TRUE).
          Also we have configured NO stores but a JDBC Tx DataSource.
          I would appreciate any suggestions.
          **see attached picture**
          [confui2.jpg]
          

In order to use WLS JMS temporary destinations, you have to have a temporary destination template configured for
          the JMS server.
          Dongbo
          Puneet Bhatia wrote:
          > We are running an application within the Weblogic 7.x EJB Framework. While trying
          > to connect to the application from our GUI I get the following error. **... Unable
          > to resolve 'weblogic.jms.TempDestinationFactory' Resolved: 'weblogic.jms' Unresolved:'TempDestinationFactory'
          > ; We have configured our JMS server with two topics - one of which is used for
          > persistent storage (i.e has the 'store' configuration attribute set to TRUE).
          > Also we have configured NO stores but a JDBC Tx DataSource.
          > I would appreciate any suggestions.
          >
          > **see attached picture**
          >
          > ------------------------------------------------------------------------
          > Name: confui2.jpg
          > confui2.jpg Type: JPEG Image (image/pjpeg)
          > Encoding: base64
          

Similar Messages

  • Unable to resolve 'weblogic.messaging.dispatcher.S:null'

    We have a WLS 10.3 cluster with 1 admin server and 2 managed servers. Each managed server hosts JMS queues so we have a distributed queue environment. Applications periodically report an issue that prevents messages from being dropped onto the queues. The frequency of the issue is weekly and sometimes multiple times during the week. We have found that un-targeting and re-targeting the JMS Servers seems to resolve the problem (at least in the short term). The message producer applications are using the weblogic.jar and an xa connection factory. I've included the stack trace below. I'm hoping that someone can help uncover the root cause of the issue.
    Stack Trace:
    Caused by: weblogic.jms.common.JMSException: No failover destination.
    at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
    at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1275)
    at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:783)
    at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
    at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
    at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
    at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
    at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:597)
    at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:574)
    at org.springframework.jms.core.JmsTemplate$4.doInJms(JmsTemplate.java:551)
    at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:471)
    ... 8 more
    Caused by: weblogic.jms.common.JMSException: No failover destination.
    at weblogic.jms.frontend.FEProducer.pickNextDestination(FEProducer.java:750)
    at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1092)
    at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1399)
    at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1460)
    at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
    at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
    at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
    at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
    at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.messaging.dispatcher.DispatcherException: could not find Server null
    at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:176)
    at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:58)
    at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:219)
    at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreateChecked(JMSDispatcherManager.java:230)
    at weblogic.jms.frontend.FEProducer.findDispatcher(FEProducer.java:825)
    at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:995)
    ... 9 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:null'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:null'
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
    at javax.naming.InitialContext.lookup(InitialContext.java:392)
    at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:172)
    ... 14 more

    Hi,
    I would suggest you to go through these 2 links which you give all the details about UDD
    Topic:Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
    http://middlewaremagic.com/weblogic/?p=3747
    Topic:JMS Demo using WebLogic Uniform Distributed Queue (UDQ)
    http://middlewaremagic.com/weblogic/?page_id=1976
    Tips to solve UDQ issues
    - Make sure the Server Affinity Enabled parameter should be un-checked (disable) which under the [ Connection factory –> Configuration (tab) –> Load Balance (sub-tab)]
    - Disable the Server Affinity Enabled parameter for the connection factory whish is been used by your UDQ.
    - All the managed servers are in the same cluster.
    - If the managed serves are in different boxes make sure the listing address is given correctly which is under [ Machine –> Configuration (tab) –> Node Manager (sub-tab) ]
    - Test if you are able to PING the servers on different boxes and make sure that there is no network issues and you are able to communicate with the servers.
    Hope this helps you.
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Come, Join Us and Experience The Magic…

  • JNDI naming exception...unable to resolve 'weblogic.management.adminhome'

    I'm able to start admin server and access admin console (web). When I try to connect to admin server from managed server using WLST, I'm getting the error "compatibility mbean server is not initialized properly....". I tried to ping admin server from managed server using WLST ping command (java weblogic.Admin -url xxxxx -username xxxx-password xxxx PING), I'm getting error "JNDI naming exception....unable to resolve 'weblogic.management.adminhome'".

    In order to run it remotely, I need to manually export the EAR file from Eclipse, ftp to the remote server and deploy it to the managed server.
    It seems that I missed some jar files in the managed server classpath. But, I don't know which.

  • Unable to resolve location alias (1023066 error) during of BR execution

    Hi,
    I'm using 11.1.1.3 planning classic application.
    Application has been migrated from EPMA 9.3.1.
    I try to use @XREF function to get data between plans of this application.
    BR has been validated successful.
    But I get "Unable to resolve location alias (1023066 error)" during of BR execution.
    What can be a reason of this trouble?

    Hi ,
    1. The error 1023066 is "Unable to resolve location alias" happens only when location aliase is not set in essbase matching the source server
    Sandeep Reddy Enti
    HCC
    http://hyperionconsultancy.com/

  • At startup: "Unable to resolve weblogic.jdbc.connectionPool"

    WLS 6.0 SP1 on Solaris 8
    Oracle 8.1.7 using JDBC Thin driver from Oracle.
    At startup of WebLogic, just after WLS creates the pool, I get a JNDI
    NameNotFoundException, as shown below.
    However, this does not seem to cause any problems for us.
    ####<Jun 20, 2001 10:16:17 AM GMT+10:00> <Info> <JDBC Pool ora817Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Pool: 'ora817Pool'
    will be tested at: '10 minute intervals.>
    ####<Jun 20, 2001 10:16:20 AM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:21 AM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:22 AM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:23 AM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <Adapter> <pssydsun01>
    <myserver> <main> <system> <> <000000> <Exception thrown by rmi
    server(class weblogic.jndi.internal.RootNamingNode)
    [-4918694186591914732S:192.168.0.52:[7001,7001,7002,7002,7001,7002,-1]/9]:
    weblogic.jndi.internal.RootNamingNode@1fea8a>
    javax.naming.NameNotFoundException: Unable to resolve
    weblogic.jdbc.connectionPool Resolved: 'weblogic' Unresolved:'jdbc' ;
    remaining name 'connectionPool'
    at
    weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
    at
    weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
    at
    weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
    at
    weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
    at
    weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
    at
    weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(RootNamingNode_WLSkel.java:230)

    Just installed SP2 on top of WebLogic Server 6.0 SP1.
    I still get the same message in weblogic.log while it was starting up:
    ####<Jun 28, 2001 12:53:00 PM GMT+10:00> <Info> <WebLogicServer>
    <pssydsun01> <myserver> <main> <> <> <000000> <IIOP subsystem enabled.>
    ####<Jun 28, 2001 12:53:10 PM GMT+10:00> <Info> <WebLogicServer>
    <pssydsun01> <myserver> <main> <system> <> <000214> <WebLogic Server (6.0
    Service Pack 2 05/24/2001 11:55:28 #117037) "myserver"
    (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000 BEA Systems, Inc.>
    ####<Jun 28, 2001 12:53:23 PM GMT+10:00> <Info> <JDBC Pool ora817Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Pool: 'ora817Pool'
    will be tested at: '10 minute intervals.>
    ####<Jun 28, 2001 12:53:26 PM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 28, 2001 12:53:27 PM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 28, 2001 12:53:28 PM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 28, 2001 12:53:29 PM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 28, 2001 12:53:30 PM GMT+10:00> <Info> <JDBC Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
    "ora817Pool" created.>
    ####<Jun 28, 2001 12:53:30 PM GMT+10:00> <Info> <Adapter> <pssydsun01>
    <myserver> <main> <system> <> <000000> <Exception thrown by rmi
    server(class weblogic.jndi.internal.RootNamingNode)
    [7126974831161186990S:192.168.0.52:[7001,7001,7002,7002,7001,7002,-1]/9]:
    weblogic.jndi.internal.RootNamingNode@504ec1>
    javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved: ''
    Unresolved:'jdbc' ; remaining name ''
    at
    weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
    at
    weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
    at
    weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
    Daniel Hoppe wrote:
    Hi,
    it's a problem in SP1, doesn't seem to cause any harm. Afaik it's fixed
    in RP1 and in SP2
    Daniel
    -----Urspr?ngliche Nachricht-----
    Von: Jesus M. Salvo Jr. [mailto:[email protected]]
    Bereitgestellt: Mittwoch, 20. Juni 2001 02:17
    Bereitgestellt in: jndi
    Unterhaltung: At startup: "Unable to resolve
    weblogic.jdbc.connectionPool"
    Betreff: At startup: "Unable to resolve weblogic.jdbc.connectionPool"
    WLS 6.0 SP1 on Solaris 8
    Oracle 8.1.7 using JDBC Thin driver from Oracle.
    At startup of WebLogic, just after WLS creates the pool, I get a JNDI
    NameNotFoundException, as shown below.
    However, this does not seem to cause any problems for us.
    ####<Jun 20, 2001 10:16:17 AM GMT+10:00> <Info> <JDBC Pool
    ora817Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000> <Pool:
    'ora817Pool'
    will be tested at: '10 minute intervals.>
    ####<Jun 20, 2001 10:16:20 AM GMT+10:00> <Info> <JDBC
    Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000>
    <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:21 AM GMT+10:00> <Info> <JDBC
    Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000>
    <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:22 AM GMT+10:00> <Info> <JDBC
    Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000>
    <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:23 AM GMT+10:00> <Info> <JDBC
    Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000>
    <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <JDBC
    Connection Pool>
    <pssydsun01> <myserver> <main> <system> <> <000000>
    <Connection for pool
    "ora817Pool" created.>
    ####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <Adapter>
    <pssydsun01>
    <myserver> <main> <system> <> <000000> <Exception thrown by rmi
    server(class weblogic.jndi.internal.RootNamingNode)
    [-4918694186591914732S:192.168.0.52:[7001,7001,7002,7002,7001,
    7002,-1]/9]:
    weblogic.jndi.internal.RootNamingNode@1fea8a>
    javax.naming.NameNotFoundException: Unable to resolve
    weblogic.jdbc.connectionPool Resolved: 'weblogic' Unresolved:'jdbc' ;
    remaining name 'connectionPool'
    at
    weblogic.jndi.internal.BasicNamingNode.newNameNotFoundExceptio
    n(BasicNamingNode.java:803)
    at
    weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingN
    ode.java:209)
    at
    weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamin
    gNode.java:129)
    at
    weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
    at
    weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
    at
    weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(RootNaming
    Node_WLSkel.java:230)

  • Unable to resolve a ejbc Parse error

    Hi,
    I am using a session bean, which has to execute time-consuming
    business logic in transaction boundary. Everytime the transaction is
    getting timed out. To eliminate this problem, I have added
    <trans-timeout-seconds> in the weblogic-ejb-jar.xml file. Then i
    started getting ejbc parse error. I couldn't compile the file.
    The sml file and the error message are here:
    weblogic-ejb-jar.xml file:
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic
    6.0.0 EJB//EN'
    'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>APInterfaceBean</ejb-name>
    <jndi-name>JNDI_APINTERFACEMANAGER</jndi-name>
    <transaction-descriptor>
    <trans-timeout-seconds>120</trans-timeout-seconds>
    </transaction-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    Error message:
    ERROR: Error parsing 'META-INF/weblogic-ejb-jar.xml' line 17:
    The co
    ntent of element type "weblogic-enterprise-bean" must match
    "(ejb-name,(entity-d
    escriptor|stateless-session-descriptor|stateful-session-descriptor|message-drive
    n-descriptor)?,transaction-descriptor?,reference-descriptor?,enable-call-by-refe
    rence?,run-as-identity-principal?,jndi-name?,local-jndi-name?)".
    ERROR: ejbc found errors
    Request for urgent help in resolving this problem.
    Thanks in advance
    Regards
    Rajeev

    try
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic
    6.0.0 EJB//EN'
    'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>APInterfaceBean</ejb-name>
    <transaction-descriptor>
    <trans-timeout-seconds>120</trans-timeout-seconds>
    </transaction-descriptor>
    <jndi-name>JNDI_APINTERFACEMANAGER</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    William Kemp wrote:
    Hi,
    The comma separated list of elements that can appear in the
    <weblogic-enterprise-bean> element defines a strict sequence. Optional elements
    (those followed by a ?), must appear in order if they are present when part of a
    comma separated list. So, <transaction-descriptor> before <jndi-name>.
    Bill
    Rajeev S wrote:
    Hi,
    I am using a session bean, which has to execute time-consuming
    business logic in transaction boundary. Everytime the transaction is
    getting timed out. To eliminate this problem, I have added
    <trans-timeout-seconds> in the weblogic-ejb-jar.xml file. Then i
    started getting ejbc parse error. I couldn't compile the file.
    The sml file and the error message are here:
    weblogic-ejb-jar.xml file:
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic
    6.0.0 EJB//EN'
    'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>APInterfaceBean</ejb-name>
    <jndi-name>JNDI_APINTERFACEMANAGER</jndi-name>
    <transaction-descriptor>
    <trans-timeout-seconds>120</trans-timeout-seconds>
    </transaction-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    Error message:
    ERROR: Error parsing 'META-INF/weblogic-ejb-jar.xml' line 17:
    The co
    ntent of element type "weblogic-enterprise-bean" must match
    "(ejb-name,(entity-d
    escriptor|stateless-session-descriptor|stateful-session-descriptor|message-drive
    n-descriptor)?,transaction-descriptor?,reference-descriptor?,enable-call-by-refe
    rence?,run-as-identity-principal?,jndi-name?,local-jndi-name?)".
    ERROR: ejbc found errors
    Request for urgent help in resolving this problem.
    Thanks in advance
    Regards
    Rajeev
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • Unable to resolve DB adapter runtime error

    I am writing files to DB in flowN activity using merge operation and getting merge operation failed error. Then I set the following 2 properties in .jca file:
    <property name="setMaxRaiseSize" value="100"/>
    <property name="setmaxTransactionSize" value="1000"/>
    Later I found that these are inbound properties and removed from .jca file, but still I am getting the following error with reference to the property setmaxTransactionSize.
    <bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'merge' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBWriteInteractionSpec due to: Cannot set JCA WSDL Property. Error while setting JCA WSDL Property. Property setmaxTransactionSize is not defined for oracle.tip.adapter.db.DBWriteInteractionSpec Please verify the spelling of the property. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>Cannot set JCA WSDL Property. Error while setting JCA WSDL Property. Property setmaxTransactionSize is not defined for oracle.tip.adapter.db.DBWriteInteractionSpec Please verify the spelling of the property. </detail></part><part name="code"><code>null</code></part></bindingFault></bpelFault>
    I dont know from where it is still referencing the property. Please help me on how to identify and resolve this error.
    Thanks.
    Regards
    Shyam

    #include"FileSystem.h"//cannot include FileSystem.h
    The file is present in the projects folder of the working directory.
    Still couldnt resolve intellisence error. Kindly help!
    Perhaps it's getting confused because filesystem is the name of a compiler-supplied header.
    https://msdn.microsoft.com/en-us/library/hh874694.aspx
    What happens if you change the name of your header from filesystem.h to something else?
    - Wayne

  • Unable to resolve DB adapter runtime error for setMaxRaiseSize property

    I am writing files to DB in flowN activity using merge operation and getting merge operation failed error. Then I set the following 2 properties in .jca file:
    <property name="setMaxRaiseSize" value="100"/>
    <property name="setmaxTransactionSize" value="1000"/>
    Later I found that these are inbound properties and removed from .jca file, but still I am getting the following error with reference to the property setmaxTransactionSize.
    <bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'merge' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBWriteInteractionSpec due to: Cannot set JCA WSDL Property. Error while setting JCA WSDL Property. Property setMaxRaiseSize is not defined for oracle.tip.adapter.db.DBWriteInteractionSpec Please verify the spelling of the property. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>Cannot set JCA WSDL Property. Error while setting JCA WSDL Property. Property setMaxRaiseSize is not defined for oracle.tip.adapter.db.DBWriteInteractionSpec Please verify the spelling of the property. </detail></part><part name="code"><code>null</code></part></bindingFault></bpelFault>
    I dont know from where it is still referencing the property. Please help me on how to identify and resolve this error.
    Thanks.
    Regards
    Shyam
    Edited by: Shyam Patibandla on Sep 5, 2012 2:32 AM

    Hi,
    Please do following settings.
    1. Increase the consumer threads for file adapter.
    2. Increase the concurrency in receiver communication channel.
    3. Set poolWaitingTime in receiver communication channel.
    Refer SAP Note: 821267
    Regards,
    Gouri

  • Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'

    Hello,
    I hope I am posting this in the right place, if not please forgiv and point me to the right place.
    Yesterday we did a live upgrade on a system that is running WebLogic 9.2, OSM 6.3.1 and Oracle DB 10.2.0.2, those applications are on a seperate system slice, we did a complete upgrade from Solaris 10/9 (update 6) to the latest Solaris 8/11 (update 10), on SPARC. After the upgrade everything was working and applications are able to start, but weblogic server is spewing the following error message:
    <Aug 1, 2012 12:03:58 PM CEST> <Error> <oms.core> <600022> <EJB Create exception thrown while creating object=EventDispatcherEJB.>
    <01-Aug-2012 12:03:58,982 CEST PM> <ERROR> <poller.a> <Timer-4> <Failed to process events>
    java.rmi.RemoteException: Error in ejbCreate:; nested exception is:
    javax.ejb.CreateException: Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'. Resolved 'mslv.oms.oms1.internal.jms'
    at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
    at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:724)
    at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
    at weblogic.ejb.container.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:220)
    at weblogic.ejb.container.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:64)
    at com.mslv.oms.eventengine.EventDispatcher_86q3j1_EOImpl.processTimeout(EventDispatcher_86q3j1_EOImpl.java:485)
    at com.mslv.oms.poller.a.handleNotification(Unknown Source)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1652)
    at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
    at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
    at javax.management.timer.Timer.sendNotification(Timer.java:1295)
    at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
    at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)
    we went back and activated Solaris update 8, and we still got that problem. The requests that the clients that connect via OSM frontend application that communicates with WebLogic arent being processed.
    The oracle db is working and listening to port 1521, I can connect to it and can connect with the user defined in the WebLogic connection pool.
    This is the first time working on this system, the application and integration was done by someone else who are not available to help us out, I hope someone here on the forum will be able to help us out with this problem.
    Regards,
    Omar

    Often ConnectionFactory errors are caused by an inability to connect with the database hosting the OSM schema and user.
    Check the database and make sure that both it and its listener are accepting connections. If that is ok you can also check the oms_pool configuration in WebLogic. Make sure the JNDI connection is valid. In my environments I see that DHCP often screws things up. If I install OSM on a host that has a DHCP assigned address (I'm guilty of being lazy when working in VMs and not statically assigning IP addresses) I often break the JNDI when I reboot the VM and get a new IP.
    In WebLogic Admin Console:
    Domain > Services > JDBC >Connection Pool > URL
    and make sure the JDBC connection string is correct.

  • JMS communication error

    Hi,
    I have deployed JMS application on Oracle 9i Application Server. I have made the necessary configurations in jms.xml(eg., Setting the queue connection factory and the name of the queue). Now when I try to run the client application I get the following error.
    JMS communication error = Unable to connect to JMSServer (localhost/127.0.0.1:9127)
    The JMS server is running on port 9127....
    The rmi server is running on port 23791...
    Can anyone help me out as to how this problem could be resolved ?
    Sirisha

    Hi
    Did you try changing jms.xml to point to the real ip instead of host="localhost" ?
    sometimes it works.
    g'day
    nimo

  • Unable to resolve JNDI DataSource in weblogic 12c When you upgrade web application

    I create a datasource which jndi name is jdbc/allianzB2CDataSource and the target is AdminServer ,and i deploy a web application in AdminServer.In that web application,the code(base on spring framework) is:
    public static DataSource getJndiDataSource(String name) {
      JndiDataSourceLookup dsLookup = new JndiDataSourceLookup();
      Properties jndiEnvironment = new Properties();
      jndiEnvironment.put("java.naming.factory.initial",
      "weblogic.jndi.WLInitialContextFactory");
      dsLookup.setJndiEnvironment(jndiEnvironment);
      try {
      dsLookup.setResourceRef(false);
      return dsLookup.getDataSource(name);
      } catch (Exception e) {
      dsLookup.setResourceRef(true);
      return dsLookup.getDataSource(name);
    And the parameter is jdbc/allianzB2CDataSource,everything work fine,but when i restart or upgrate the web application,i got the error like this:
    javax.naming.NameNotFoundException: Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'
    Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'

    I create a datasource which jndi name is jdbc/allianzB2CDataSource and the target is AdminServer ,and i deploy a web application in AdminServer.In that web application,the code(base on spring framework) is:
    public static DataSource getJndiDataSource(String name) {
      JndiDataSourceLookup dsLookup = new JndiDataSourceLookup();
      Properties jndiEnvironment = new Properties();
      jndiEnvironment.put("java.naming.factory.initial",
      "weblogic.jndi.WLInitialContextFactory");
      dsLookup.setJndiEnvironment(jndiEnvironment);
      try {
      dsLookup.setResourceRef(false);
      return dsLookup.getDataSource(name);
      } catch (Exception e) {
      dsLookup.setResourceRef(true);
      return dsLookup.getDataSource(name);
    And the parameter is jdbc/allianzB2CDataSource,everything work fine,but when i restart or upgrate the web application,i got the error like this:
    javax.naming.NameNotFoundException: Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'
    Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'

  • Oracle.jms.AQjmsException: Error creating the db_connection( OSB PS2.)

    hi All,
    I am beginner in OSB 11g. Please excuse me if I am asking any dumb question.
    I am trying to post messages to Oracle AQ by configuring JMS Destination in OSB Alert destination
    I have configured AQ JMS in weblogic 10.3.3 ( OSB PS2) following the blog (http://jianmingli.com/wp/?p=2950)
    When i invoked my proxy OSB proxy service i am getting following exception. Can you please help if i am missing any kind of setup while configuring the JMS Module.
    Caused By: oracle.jms.AQjmsException: Error creating the db_connection
         at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:625)
         at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
         at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
         at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
         at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
         at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
         at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
         at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.getSession(JmsOutboundMessageContext.java:399)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.newMessage(JmsOutboundMessageContext.java:621)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.setRequestMetaData(JmsOutboundMessageContext.java:229)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.access$100(JmsOutboundMessageContext.java:72)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext$SendAction.run(JmsOutboundMessageContext.java:788)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.Security.runAs(Security.java:61)
         at com.bea.wli.sb.transports.jms.JmsOutboundMessageContext.send(JmsOutboundMessageContext.java:551)
         at com.bea.wli.sb.transports.jms.JmsTransportProvider.sendMessageAsync(JmsTransportProvider.java:680)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
         at $Proxy111.sendMessageAsync(Unknown Source)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageWithoutService(TransportManagerImpl.java:489)
         at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:417)
         at com.bea.wli.sb.init.FrameworkStarter$TransportServiceImpl.sendMessageAsync(FrameworkStarter.java:391)
         at com.bea.alsb.alert.action.jms.JmsActionProvider.executeAction(JmsActionProvider.java:345)
         at com.bea.alsb.alert.AlertDestinationHandlerImpl.sendAlertToDestination(AlertDestinationHandlerImpl.java:105)
         at com.bea.alsb.alert.pipeline.PipelineAlertManager.processAlert(PipelineAlertManager.java:59)
         at stages.logging.runtime.AlertRuntimeStep.processMessage(AlertRuntimeStep.java:125)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.stages.impl.SequenceRuntimeStep.processMessage(SequenceRuntimeStep.java:33)
         at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeStep.java:102)
         at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
         at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
         at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:106)
         at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
         at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
         at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
         at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
         at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
         at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
         at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
         at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
         at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
         at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
         at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
         at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
         at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
         at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
         at oracle.jms.AQjmsDBConnMgr.getConnection(AQjmsDBConnMgr.java:566)
         at oracle.jms.AQjmsDBConnMgr.<init>(AQjmsDBConnMgr.java:399)
         at oracle.jms.AQjmsXAConnection.<init>(AQjmsXAConnection.java:112)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createAllXAConnection(AQjmsXAQueueConnectionFactory.java:320)
         at oracle.jms.AQjmsXAQueueConnectionFactory.createXAQueueConnection(AQjmsXAQueueConnectionFactory.java:198)
         at weblogic.deployment.jms.JMSConnectionHelper.openConnection(JMSConnectionHelper.java:282)
         at weblogic.deployment.jms.JMSConnectionHelper.<init>(JMSConnectionHelper.java:144)
         at weblogic.deployment.jms.JMSSessionPool.getConnectionHelper(JMSSessionPool.java:517)
         at weblogic.deployment.jms.PooledConnectionFactory.createConnectionInternal(PooledConnectionFactory.java:355)
         at weblogic.deployment.jms.PooledConnectionFactory.createQueueConnection(PooledConnectionFactory.java:188)

    hi All,
    Here is the actual exception while posting message into AQ ( AQ JMS) from OSB.
    Caused By: java.lang.ClassCastException: weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1033_WLStub cannot be cast to oracle.jdbc.internal.OracleConnection
    at oracle.jms.AQjmsGeneralDBConnection.getProviderKey(AQjmsGeneralDBConnection.java:96)
    at oracle.jms.AQjmsGeneralDBConnection.<init>(AQjmsGeneralDBConnection.java:65)
    Not sure what is missing in my AQ JMS configuration. Please help.
    Regards,
    Nagi

  • Error in a page with a master-detail:Unable to resolve a Validator instance

    Hi all,
    I am using Jdeveloper 11.1.1.2
    I have a page with a master table and a detail table.
    When I try to select a row in the some tables (master or detail), I have this error:
    <AbstractValidatorTag><createValidator> Unable to resolve a Validator instance using either validatorId ' or binding #{row.bindings.IdLocazione.validator}.
    <RegistrationConfigurator><handleError> Server Exception during PPR, #1
    javax.servlet.ServletException: Unable to resolve a Validator instance using either validatorId '' or binding '#{row.bindings.IdLocazione.validator}'.
         at javax.faces.webapp.FacesServlet.service(FacesServlet.java:270)
         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:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Any suggestions?
    Thanks
    Andrea
    Edited by: Andrea9 on 17-feb-2010 00:45

    I am using ADF, I can reproduce in a testcase, but I need time.
    If you want, I can cut and paste the jspx page.
    However, I have a panelStretchLayout: on top facet I have the master table, while in the center facet I have the detail table.
    I have a query component to filtering data of the master table.
    I have this problem doing this:
    1) create a new record on master table.
    2) create some records on detail table (sons of the record of the master table just created).
    3) clicking on "find" of the query component.
    I have tried to do a master-detail with the HR connection using Departments table (master) and Employee (detail). When I try to delete a departments, it does not work, because I have to delete the employees first, while in my case I want to delete the master and the detail in cascade.
    Thanks
    Edited by: Andrea9 on 17-feb-2010 08:25

  • JMS Internal Error at Server Client Adapter!JMS Service is not started

    Hi
    Can any one tell me how to trouble shoot for following errors:
    Failed to Create Connection! Reason: Response from the server could not be reached.
    JMS Internal Error at Server Client Adapter!JMS Service is not started
    The following hosts could not be reached 143:223:221:10:50310
    We are trying to send the request from SONICMQ JMS to R/3 and trying to post the response to Sonic Queue. but we are facing some problems for JMS adapter .
    but in JMS sender and receiver adapter i gave different IP and port for listen the SONIC queue. why it is showing in different IP here? this message got from logviewer.
    regards
    Rambarki...

    Rambarki,
    What is the error displayed on the Adapter Monitoring pages?
    Generally the correct error descriptions for connectivity issues are found on adapter monitoring UI than any other.
    Other possible reasons could be :
    <i>JMS Service is not started
    The following hosts could not be reached 143:223:221:10:50310</i> This might be issue with your network settings i.e. XI server is unable to reach the specified IP on specified port.
    Regards,
    Amol

  • Javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'   - in Weblogic on starting the server

    Hi,
    I am not able to resolve the JNDI name - ATGProductionDS
    I have used CIM to create this and i am using ATG10.2 with MYSQL as my database and weblogic.
    /atg/epub/file/ConfigFileSystem journaling file system started: vfs=file:/C:
    /Stixs/ATG/ATG10.2/home/PublishingAgent/deploymentconfig/live/config/ journalDirectory=C:\Stixs\ATG\ATG10.2\home\PublishingAgent\deploymentc
    onfig\data\config
    **** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource     Failed to resolve ATGProduct
    ionDS   javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'. Resolved ''; remaining name 'ATGProductionDS'
    **** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource             at weblogic.jndi.int
    ernal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
    **** Error      Fri Dec 27 20:58:35 EST 2013    1388195915495   /atg/dynamo/service/jdbc/DirectJTDataSource             at weblogic.jndi.int
    Entries from Weblogic console -datasources
    ATGBatchDS
    Generic
    ATGBatchDS
    ATGProductionDS
    Generic
    ATGProductionDS
    atg_production_lockserver, atg_publishing_lockserver
    ATGPublishingDS
    Generic
    ATGPublishingDS
    atg_publishing_lockserver
    Please provide assistance.

    Hi,
    if you click the "Control" tab for the ATGProductionDS datasource in the Weblogic console does it show the State as running?
    Does the "Monitoring" tab for the datasource show the State as running? If you click on the "Testing" tab can you test the datasource successfully?
    If you inspect the Server using the Weblogic console there is a link "View JNDI Tree" If you click the link do you see the datasource listed in the left pane?
    Do you see any errors for the ATGProductionDS in the Weblogic server log and out log files?

Maybe you are looking for