Jbo:datasource orderbyclause never resets during application
My application uses a dynamic viewobject and I use a jbo:datasource to retrieve my information and print it in my jsp page.
now when running my application the first set of the orderbyclause in jbo:datasource for instance
String columnName = "first";
<jbo:DataSource id="_LOV" whereclause="<%=whereClause%>" orderbyclause="<%=columnName%>" forwardonly="true" appid="module" viewobject="view"/>
as you can see the orderbyclause is dynamic
then once a call the jsp again the orderbyclause does not change, even though the variable value stays the same, it acts like
String columnName = "second";
<jbo:DataSource id="_LOV" whereclause="<%=whereClause%>" orderbyclause="<%=columnName%>" forwardonly="true" appid="module" viewobject="view"/>
but the order by is still set to "first"
I am dealing with 10g version, in 11g it works no problem.
There is a setting in the app module configuration called "Disconnect Application Module Upon Release". By default it's set to false which means the AM retains database connections between http requests (you could say they're sticky). Setting it to true will release datasource connections between requests. You should also set jbo.txn.disconnect_level = 1 which will passivate AM in memory rather than DB
You will find more info in these blog posts:
http://andrejusb.blogspot.com/2011/10/adf-bc-tuning-with-do-connection.html
http://docs.oracle.com/cd/E15523_01/web.1111/b31974/bcampool.htm
http://andrejusb.blogspot.com/2010/02/optimizing-oracle-adf-application-pool.html
Similar Messages
-
Pre-loading the Cache from Database during application start-up
We are using Spring, Hibernate, Oracle Coherence 3.5.2 Weblogic Webservices
Our requirement is to pre-load the cache during the application start-up most probably during Authentication/Authorization Service is invoked.
We plan to load the data for other services from database into Coherence cache so that whenever user access that particular service he ends up hitting the Cache instead of database.
We would greatly appreciate sample code snippets on how to write CacheInitializerBean with marker to demonstrate the state of cache.Hi Rob,
Thanks for pointing to the article: Pre-Loading the Cache
In fact i already looked at that article before posting. It just mentions how to load the data from database into Cache.
What i am looking for is how to make this happen during application start-up. This is my first hurdle.
The second one is as mentioned in the article http://coherence.oracle.com/display/COH35UG/Pre-Loading+the+Cache
i wrote following code which never gets populated into cache. Not sure whats going wrong even though i see Hibernate loadAll() method loading all the objects in the console
public void populateCache() throws SQLException
Map<Long, Object> buffer = new HashMap<Long, Object>();
int count = 0;
List<Contract> contractList = this.getHibernateTemplate().loadAll(Contract.class);
log.debug("contractList size="+contractList.size());
for(Contract contract : contractList)
Long key = new Long(contract.getId());
Object value = contract;
buffer.put(key, value);
// this loads 1000 items at a time into the cache
if ((count++ % 1000) == 0)
contractCache.putAll(buffer);
buffer.clear();
if (!buffer.isEmpty())
contractCache.putAll(buffer);
}We would greatly appreciate your time in helping us resolving two hurdle blocks. -
Pre-load the Cache during Application-Start Up
Our requirement is to pre-load the cache during the application start-up most probably during Authentication/Authorization Service is invoked.
We plan to load the data for other services from database into Coherence cache so that when user access that particular service he ends up hitting the Cache instead of database.
Any pointers/suggestions on how to pre-load the cache during application start-up would be greatly appreciated. We are using Spring, Hibernate, Weblogic Web Services
Regards,
BansiHi Bansi,
I were using following approach.
First, we never use CacheFactory.getCache() in application code instead all instances of named cache were injected.
On server side, I have an CacheInitializerBean which were starting cache preloading process (in separate thread). After preloading a special marker entry were put to the cache, indicating what data in the cache are consistent.
When injecting named cache instance, we use a factory. This factory use CacheFactory.getCache() internally, but it check presence of marker object in cache an blocks until marker object will appear.
Well in practice things are little more complicated but this is basic idea.
Preload cache asynchronously and use marker to indicate completion of loading process.
Hope this will help.
Regards,
Alexey -
Message bean does not start automatically during application server startup
I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
at java.lang.Class.getConstructor0(Class.java:1930)
at java.lang.Class.newInstance0(Class.java:278)
at java.lang.Class.newInstance(Class.java:261)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:379)
at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve -
After Effects can't continue: unexpected failure during application startup
Im running 10.10, Mac OSX, it was running fine before a minor update came out, and now I can not open AE CS6. I have uninstalled, reinstalled it, installed the trial of CC 2014. No messages beside "After Effects can’t continue: unexpected failure during application startup" come up.
System log:
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 0 CarbonCore 0x00007fff82bb637d ___Gestalt_SystemVersion_block_invoke + 113
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 1 libdispatch.dylib 0x00007fff8bf70fa2 _dispatch_client_callout + 8
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 2 libdispatch.dylib 0x00007fff8bf70f00 dispatch_once_f + 79
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 3 CarbonCore 0x00007fff82b5e932 _Gestalt_SystemVersion + 987
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 4 CarbonCore 0x00007fff82b5e51f Gestalt + 144
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 5 AdobeCrashDaemon 0x0000000100002e69 -[MyDaemon GetOSVersionMajor] + 33
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 6 AdobeCrashDaemon 0x0000000100002d4a -[MyDaemon isRunningOnLeopard] + 25Well, looks like a bug in Yosemite. You might wanan read the pertinent announcements, anyway. At this point Adobe apps are not compatible with OSX 10.10.
Mylenium -
Exception during application deployment
Hi all,
I'm trying to deploy a wd application from NWDS (NW2004 sp19) and I get an error:
The application references the following jars - com.sap.security.api, com.sap.security.api.ep5, bc.rf.framework_api and bc.util.public_api. I also defined a Sharing Reference - "PORTAL:sap.com/com.sap.km.application".
Full error stacktrace:
06/10/2008 10:20:25 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[007]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7186 - 630]/>
<!NAME[D:\usr\sap\EPT\JC00\SDM\program\log\sdmcl20081006082023.log]/>
<!PATTERN[sdmcl20081006082023.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1255]/>
<!LOGHEADER[END]/>
Oct 6, 2008 10:20:23 AM Info: -
Starting deployment -
Oct 6, 2008 10:20:23 AM Info: Error handling strategy: OnErrorStop
Oct 6, 2008 10:20:23 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Oct 6, 2008 10:20:23 AM Info: Update strategy: UpdateAllVersions
Oct 6, 2008 10:20:23 AM Info: Starting deployment prerequisites:
Oct 6, 2008 10:20:23 AM Info: Loading selected archives...
Oct 6, 2008 10:20:23 AM Info: Loading archive 'D:\usr\sap\EPT\JC00\SDM\program\temp\temp86DepthVisit.ear'
Oct 6, 2008 10:20:24 AM Info: Selected archives successfully loaded.
Oct 6, 2008 10:20:24 AM Info: Actions per selected component:
Oct 6, 2008 10:20:24 AM Info: Update: Selected development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0' updates currently deployed development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.09.25.15.49.17'/'0'.
Oct 6, 2008 10:20:24 AM Info: Ending deployment prerequisites. All items are correct.
Oct 6, 2008 10:20:24 AM Info: Saved current Engine state.
Oct 6, 2008 10:20:24 AM Info: Starting: Update: Selected development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0' updates currently deployed development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.09.25.15.49.17'/'0'.
Oct 6, 2008 10:20:24 AM Info: SDA to be deployed: D:\usr\sap\EPT\JC00\SDM\root\origin\local\DepthVisit\LOKAL\0\0.2008.10.06.10.20.19\temp86DepthVisit.ear
Oct 6, 2008 10:20:24 AM Info: Software type of SDA: J2EE
Oct 6, 2008 10:20:24 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 6, 2008 10:20:24 AM Info: Begin of log messages of the target system:
08/10/06 10:20:24 - ***********************************************************
08/10/06 10:20:24 - Start updating EAR file...
08/10/06 10:20:24 - start-up mode is lazy
08/10/06 10:20:24 - EAR file updated successfully for 63ms.
08/10/06 10:20:24 - Start updating...
08/10/06 10:20:24 - EAR file uploaded to server for 79ms.
08/10/06 10:20:24 - ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application local/DepthVisit..
Reason: Exception during generation of components of application local/DepthVisit in container webdynpro.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deployApplicationDuringUpdate(DeployServiceImpl.java:701)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:666)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:612)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
... 12 more
Caused by: java.lang.NullPointerException
at com.sap.engine.services.webdynpro.util.Procedures.switchio(Procedures.java:40)
at com.sap.engine.services.webdynpro.ArchiveParser.extractEntry(ArchiveParser.java:127)
at com.sap.engine.services.webdynpro.ArchiveParser.process(ArchiveParser.java:101)
at com.sap.engine.services.webdynpro.PApplication.process(PApplication.java:170)
at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:838)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 18 more
For detailed information see the log file of the Deploy Service.
08/10/06 10:20:24 - ***********************************************************
Oct 6, 2008 10:20:24 AM Info: End of log messages of the target system.
Oct 6, 2008 10:20:24 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 6, 2008 10:20:24 AM Error: Aborted: development component 'DepthVisit'/'local'/'LOKAL'/'0.2008.10.06.10.20.19'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application local/DepthVisit..
Reason: Exception during generation of components of application local/DepthVisit in container webdynpro.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/DepthVisit in container webdynpro.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Oct 6, 2008 10:20:24 AM Info: Starting to save the repository
Oct 6, 2008 10:20:25 AM Info: Finished saving the repository
Oct 6, 2008 10:20:25 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Oct 6, 2008 10:20:25 AM Error: -
At least one of the Deployments failed -Hi,
Building the ear file is not the problem.
The deployment fails.
Seems that somehow I dont have those jars on the server.....
Aviad
Edit: I've done a search on the server and all the relevant jars are there, none is missing.
Whats next?
Edited by: Aviad Levy on Oct 6, 2008 4:41 PM -
Message sending during application processing
Hi Experts,
I want to send a message via IDOC marked as "to be processed immediate"(4) during application saving. In USEREXIT_SAVE_DOCUMENT a message is inserted into NAST. Transaction is VA11. The message should be processed during saving of document. But it is not sent. If it is marked as to be processed by job (1) and RSNAST00 is used it works. Other messages found by condition during VA11 processing are processed immediately.
Thanks in advanceHi,
It's single server installation.
I got the following suggestions from SAP from a message i sent them, i.e. "An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"
1. took /3GB switch out of boot.ini
2. Configured Analysis Services memory from:
LowMemoryLimit - 1835008000 - 1750 MB
TotalMemoryLimit - 2831155200 - 2700 MB
to
LowMemoryLimit - 1218445312 - 1162 MB
TotalMemoryLimit - 1835008000 - 1750 MB
3. Rebooted Server.
Appreciate it if you have any comments about this.
Regards,
Lip Chean -
Reg: Runtime exception occurred during application mapping
Dear SAP Gurus,
This is Amar Srinivas Eli working currently on SOAP to SOAP Scenario on PI 7.1 Server.
I Would like to inform you that I have done all steps regarding DESIGN and CONFIG and also regarding SERVICE REGISTRY part successfully.
While Testing the data in the WS Navigator by giving the input parameters I am getting an error that
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- <!-- Request Message Mapping*
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_HRS_LISTReferral_Response_MM_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns1:PI_ListRefer</SAP:P3>
<SAP:P4>ral_Response_MT. Values missing in queue context.~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_HRS_LISTReferral_Response_MM_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns1:PI_ListReferral_Response_MT. Values missing in queue context.~</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
These are the steps I did while implementing..
1. Importing the XSD's successfully
2. Developed the design and config part and also checked nearly 3-4 times regarding both REQ and
RESPONSE Mappings.
3. I already checked the link of WSDL once again...
4. Even I found REsponse Interface once again...
Still I am not getting where the error was ? Please guide me in detail in a right way in this issue.
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 7:53 AMHello,
I already checked all those queues and context fields////
Based on my Observation I found
1) As I am unable to view the SOAP BODY I increased the RUN TIME Trace Level to 3 and LOG_VAlue to 3
2) ANother most Important that I found later doing these settings are....
I found Receiver Pay LOAD and I copied that entire pay load and pasted it in
REceiver Message Mapping> Test Tab and Code->PASTED...and compared all those parameters
in the TEST TAB and DEFINITION TAB in Tree View whether all the mandatory receiver mapped
elements are coming I mean passing from source or not...
OBSERVATION::
I found that for nearly 3 fields there is a difference when I compared on Tree View in DEFINITION TAB and also parallely in the TEST TAB Tree View which I got by copied from MONI,,,,
see for example ::
CENTRE <----
> DISCHARGE DATE..
For going to CENTRE..here I found that in DEfiniition TAB...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component>PatientCareProvisionEvent->EffectiveTime-->CENTRE
But immediately I have gone to TEST TAB and TREE VIEW and I found that respective field CENTRE is posting I mean passing any value or parameter to Discharged Date or not...
But I found that...
Control Act Event-->Subject->document-->Component>Structured body> component> Section>Component-->_PatientCareProvisionEvent_
This Implies that Effective Time and Centre are missing in the XML and I mean no values are passing to receiver right..
In PI XSD 's it is there but in I think after Compiling REQUEST MAPPING and while in returning to RESPONSE MAPPING I mean whenever the Response is posting to SOAP WEBSERVICE it is unable to found those target elements and I think due to this...
Am I Correct ?
If that is the case...Let me know where the issue is whether in the data present in the WEBSERVICE created on target side or in PI Side..any issue...
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 13, 2009 10:00 AM -
Runtime exception occurred during application mapping
Hi All,
Please find the error message which we are getting:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Request Message Mapping
-->
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:ProductCateg</SAP:P3>
<SAP:P4>oryHierarchyMassReplicationRequest/ProductCategor~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_CRM_COD_ProductCategoryHierarchy_R~; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please give your expert Advice on the same.
Regards
RKDear Rableen,
As Muniyappan and peter told about the mandatory field value is missing for the target element
"/ns0:ProductCategoryHierarchyMassReplicationRequest/ProductCategor", I am able to see other fields are also not getting input data.
as below
"Cannot create target element /ns0:ProductCateg"
Request you to test with the payload in message mapping and activate the message mapping first and then edit your operation mapping and call the same message mapping in your operation mapping and activate all your objects.
Thank you!
Regards
Hanumantha Rao -
Runtime exception occurred during application mapping in SAP PI
Hi Team,
Please help me regarding this issue is very urgent:
Runtime Error in configuration part:
Here i test the XML message in Receiver Determintion:
Below i am getting error:
Runtime exception occurred during application mapping com/sap/xi/tf/_MaterialStockUpdate_Multi_AllPlant~; com.sap.aii.utilxi.misc.api.BaseRuntimeException:The processing instruction target matching "[xX][mM][lL]" is not allowed
SXMB_MONI:
I am getting below error:
Runtime exception occurred during application mappingHi,
Actually my problem is what i am getting,I am trying to test the data in runtime workbench and configuration part copied from inbound payload XML structure .
I already sent the screenshots of above errors,
Configuartion:
Runtime workbench:
This the error i am getting below in "Runtime Workbench"
Error While Sending Message: Additional error text from response: com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=MHEPL_Sandbox_100;TS=;AN=MaterialStockUpdate_Multi_AllPlants_N;ANS=http://www.manipalhospitals.com/his/mm; in the current context [Unknown]. -
Runtime exception occurred during application mapping "EXCEPTION_DURING_EX"
Hi Gurus,
I am getting following error in MONI:
SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_MDM_CMS_Backfeed_Group_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.MessageMappingExceptio</SAP:P2>
<SAP:P3>n: Runtime exception when processing target-field</SAP:P3>
<SAP:P4>mapping /ns0:BackfeedGroup/group/MasterId; root m~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_MDM_CMS_Backfeed_Group_; com.sap.aii.mappingtool.tf7.MessageMappingException: Runtime exception when processing target-fieldmapping /ns0:BackfeedGroup/group/MasterId; root m~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have tried to refresh the mapping cache and restart the message but stil this message persists.
For me it seems an issue with a wrong mapping or some wrong value in the inbound scenario.
Please suggest if any one of you had come across this error before.
With Reg,
VikashHi Vikash
Whenever you have a problem in your mapping you will get this kind of error in monitoring
According to your log the problem is in parameter /ns0:BackfeedGroup/group/MasterId
First of all check your mapping. If it is fine than check the value of this parameter from your payload.
Also try to copy your xml and test the mapping in IR. Check wether you are getting same error there .
If same error comes than try to manipulate the value of that field and try the same test again
Regards,
Shradha -
Sxmb_moni error BaseRuntimeException thrown during application mapping
Hi experts
My scenario is file to idoc. Pushing xml file from ftp . The messages are going in system error in RWB. When we see in sxmb_moni I get the following error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_SALES_CLM_SAP_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_SALES_CLM_SAP_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>Thanks in advance.
Edited by: zia Rahman on Nov 30, 2010 6:29 AMChange your UDF for reading the file name like this:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
// in test tool the value is null, so return the argument "test"
if (conf == null)
return "Filename"
else {
DynamicConfigurationKey key = DynamicConfigurationKey.create(
"http://sap.com/xi/XI/System/File",
"FileName");
return conf.get(key); -
JBO datasources: avoiding literal SQL in where clause
I understand that it is possible to set the where clause when defining a datasource with datatags:
e.g.
<jbo:DataSource id="ds" appid="wms_bc4j.Wms_bc4jModule" viewobject="WebUsersView" whereclause="USER_ID = 1"/>
However this results in literal SQL being sent to the database. Does anyone know of a method of using bind variables in this instance and thus avoid the literal SQL?Hi,
You need to "CAST" the bind variable to get the comma separated individual values.
Check this out article (Search for Using Comma-Separated String Bind for Variable IN List) on how to achieve this.
It has been developed on 10g. But, i think it will hold good for 11g as well.
-Arun -
Resetting default application to "Pages"
When I open a downloaded document (usually originally a Windows document), and click on it, somehow it is always opened in "Open Office" a slow and cumbersome word processing app that translates MS documents and spreadsheets well but is too sophisticated most of the time, so I only want to use it in rare cases when all else fails.
Instead, I want "Pages" to be my automatic default app for such things. How do I reset default applications, in this case to "Pages"?
PPSelect it in the Finder, choose Get Info from the File menu, click on Open With, and change it.
(58955) -
Cannot create target element(Runtime exception occurred during application
Hi ,
this is IDOC TO HTTP Scenario. in error description it is shoein g below error.
Runtime exception occurred during application
Cannot create target element (inbound)
please advice
thank you.Copy the payload from sxmb_moni and test it in the mapping tool using debug mode. I suspect some mandatory elements in target structure requires value but it is missing during mapping. Sometime sender data structure due to values are not getting at runtime does not create target structure element. Check all the individual fields in the mapping tool.
Maybe you are looking for
-
How can I get the iTunes app on my iPad Air 2?
I Noticed that I don't have the iTunes app on my iPad Air 2. How do I get it? Cannot find it on App Store.
-
Fonts No Longer Show Up Correctly on PC After Upgrade to iWeb '09
Since I upgraded to iLife '09, my iWeb webpage no longer renders fonts correctly when opened via a PC web browser (IE, Firefox, etc.). Specifically, when surfing my site on a PC, it displays only the boring default fonts like (Times New Roman), and n
-
Free/Busy availability and Out of Office not working after Exchange 2003 to Exchange 2010
We just migrated from Exchange 2003 to Exchange 2010 as an intermediate step before we get to Exchange 2013. I want to make sure everything is working OK before we start the migration to Exchange 2013. The users have Outlook 2010, and there are 2
-
Web Intelligence Security Best Practices
Hi All, We are in the process of starting to use web intelligence. I am puttng together a security model for it and I have some questions around best practices. We have a fairly simple two tier security model so far, end users and creators. Creators
-
I purchased the iPhone 5 and upgraded from the 4S. I backed up the 4S to iCloud before I did a full reset on the 4S. My iPhone 5 has still not restored to the backup from the 4S and it has been 2 weeks since the change. How do I get my iPhone 5 to