Cache Update XIServer

Every time if I send a File, I get this error message.
HTTP status code401 Unauthorized
An error occurred when refreshing the XI runtime cache
does anybody have an idea?
Regards,
Fth

Hi Fatih,
Please check the J2EE Port and also Roles assigned to the XIAPPLUSER
For more go through this thread,
ERR: HTTP_RESP_STATUS_CODE_NOT_OK - 401 Unauthorized
Also did you check in SM59->Http Connections to R/3 Systems->Check the HTTP Destination Used in the Receiver XI Adapter->open this and check for the service no.
I you are right on the Service No. , just check the Path Prefix is wrong I think- just check like this for the receiver -
/sap/xi/engine/?type=receiver
Also go through this link for any help on the same:
http://help.sap.com/saphelp_nw04/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/frameset.htm
Regards,
Abhy
Message was edited by: Abhy Thomas

Similar Messages

Error in Directory Cache Update

Hi,
because we changed from two SLDs (PROD & DEV) to one (DEV) we did all changes like given in note 720717.
Everything seems to run fine except the Adapter Engine - ok parts of it.
When checking the Cache-Infos in Integration Directory we get following error in Integration Server (Central Adapter Engine). What do we need to do?!
br
com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: SAP_XIIntegrationDirectory, [CreationClassName, SAP_XIIntegrationDirectory, string, Name, directory.px1.sapru03, string], target element type: SAP_XIIntegrationServer)
     at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:483)
     at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:154)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
     at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
     at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
     at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
     at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
     at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
     at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:259)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
     at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
     at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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(AccessController.java:207)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Hi,
Hereu2019s a list of common errors/problems in SAP XI and their possible resolutions. This Guide will help you troubleshoot your integration scenarios in SAP XI/PI. This is in no way an exhaustive list. You can add your points/ideas to this list. Please feel free to post your inputs using the comments form at the end of this article.
Cache Update Problems
Use transaction SXI_CACHE to update the Integration Directory cache. Alternatively, you can use the following URLs to update the CPA cache. Use XIDIRUSER to refresh the cache.
For complete cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=full
For delta cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=delta
If this does not solve the issue, check transaction SLDCHECK to ensure that connection to SLD is available. If the connection fails, check the configuration in the transaction SLDAPICUST. Make sure that the password maintained is correct and the maintained service user is not locked.
Now in the Integration Repository go to Environment u2192 Clear SLD Data Cache. Also go to Integration Directoy and clear the cache using menu Environment u2192 Clear SLD Data Cache.
Open the XI Start Page and click on Administration. On the Repository tab, choose Cache Overview. Refresh the cache using the buttons/icons on the right. Use XIDIRUSER to refresh the cache. Carry out cache refresh in the same way on the Directory and Runtime tabs.
If you are facing cache update problems in your BPM (say you have modified the BPM, but when executed old version of the BPM is picked up instead of the new one), run the transaction SWF_XI_CUSTOMIZING and press F9 carry out automatic BPM/Workflow Customizing.
Routing Errors
NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC
This means no receiver could be found. Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
TOO_MANY_RECEIVERS_CASE_BE
More than one receiver found. Check your ID configuration to ensure that there is exactly one receiver for the synchronous message. Multiple receivers for synchronous interfaces are not permitted.
Mapping Errors
JCO_COMMUNICATION_FAILURE
Check whether RFC destination AI_RUNTIME_JCOSERVER is correctly configured
NO_MAPPINGPROGRAM_FOUND
Ensure that mapping program exists and is activated. If it exists then update the cache.
EXCEPTION_DURING_EXECUTE
This error occurs due to erroneous XML formatting. Check your mapping program and ensure that you supply valid input data.
Messages stuck in queues
Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually.
Conversion Errors
Unable to convert the sender service XXXX to an ALE logical system
This error occurs in case of scenarios with IDoc adapters. Whenever you use business systems, make sure that the corresponding logical system name is maintained in the SLD.
Open your business system in the Integration Directory. Switch to Change mode. Access the menu path Service u2192 Adapter Specific Identifiers. Click the button that says u2018Compare with System Landscape Directoryu2019 and chose Apply. Save and activate your change list.
In case of business services, you can manually type a logical system name in the Adapter Specific Identifiers if required. This name should match the corresponding logical system name defined in the partner SAP systemu2019s partner profiles.
Errors on the outbound side
Sometimes the link between SAP XI and the target system (say ERP) goes down and messages fail on the outbound side. It may not be possible to restart them from using RWB or the transactions like SXI_MONITOR/SXMB_MONI. In such cases, you can follow the procedure outlined in the following article - Dealing with errors on the outbound side.
Refer this article:
http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/28e1c20a9d374cbb71875c5f89093b/content.htm
Refer this portal
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/pointers%2bfor%2btroubleshooting%2bportal%2bruntime%2berrors
Regards,
Suryanarayana

Int Server (ABAP Cache) - Cache Updated column shows "red"

...long read, appreciate your patience...
In the IB:Config, under Cache Notifications, I'm getting the red square in the Cache Updated column for all "ABAP Cache" entries (green for notification). The "Java Cache" and "Central Adapter Engine" entries are green all the way through.
I've read a bunch of other threads here, and I've read and worked through the entire "How to Handle Caches" document. I ran in to a couple issues, but I don't know how to solve them.....
1) When I run SXI_CACHE, I receive the following messages:
<green> "Cache contents are up to date"
<red> "Error during last attempt to refresh cache"
--->double-clicking shows: Error ID = BUSINESS_SYSTEM, Message = LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM
--->Running the LCR... fxn via SE37 is successful, so I don't understand why SXI_CACHE has a problem running it.
2) When I run the Cache Connectivity Test where the Yellow triangle is displayed for the IS-ABAP with message "Attempt to fetch cache data from Integration Directory not yet started or still in progress".
3) When I try to load http://<host>:<port>/CPACache/refresh?mode=delta or full, I get a "403 Forbidden - You are not authorized to view the requested resource." But I'm never prompted for a user/pw? Since I'm the only user in this XI box, I do have some of my logons saved in Internet Explorer - could it be using one of those without prompting me?
Note:
I have been experiencing on and off network issues, and the machine we have XI installed on is slow. I don't know if that could affect anything or not.
Thanks for taking the time to read this...
Brian
Message was edited by: Brian Vanderwiel

Thanks for the replies...
Prashanth,
I think SXI_CACHE is for items in the Java stack only (correct me if I'm wrong). The main problem I have is with items in the ABAP stack not making it in to the cache.
Moorthy,
I walked through the Readiness Check - everything passed except for the items I already mentioned (Cache test shows yellow). The document is a nice gathering of tests, but it doesn't offer any ideas has to how to correct problems encountered.
Integration_directory_hmi tested successfully, and I read through the other OSS Notes, but none solved the issue.

Supplier collab BP : Cache update

Hi,
In Supplier collaboration Business Package Cache update for master data
is not working.
Jco is created and configured.
Had a look in to the Backend System ECC and found from the trace that
Jco RFC user is executing the functional module but it is not updating
in the Portal.
Error in FI customization says" Could not read invoice document type
settings from database; contact the system administrator"
Please provide me some solution on this.

Would anyone have any suggestion for this problem.

Pof Serialization Error leads to partial cache updates in XA Tran

I am using coherence jca adapter to enlist in XA transactions with the database operations. The data is being stored in distributed caches with the cache member running on weblogic server with "Storage disabled". POF is being used for serialization. As a part of a single transaction, multiple caches, which are obtained from the CacheAdapter, are being updated. The application code does explicit updates to the cache and the database within the same transaction with the write to the cache happening after the write the database has been executed.
It is being observed that when an exception happens during the serialization of an object all the cache updates prior to this error are not rolled back. Namely,
I have CacheA for Object A, Cache B for Object B and Cache C for Object C.
I am updating A, B, C with the same transaction and in the same order as the objects are listed. So database for A is updated followed by cache update for A, DataBase B is updated followed by Cache update for B and similarly for C.
If there is an error while serializing C, all the database updates are rolled back, however updates to A and B are committed to the cache.
Why aren't all the cache updates being rolled back ? Has this been fixed already in coherence 3.6.
Thanks,
Shamsur
Application Server: Weblogic 10.3
jdbc driver : XA thin driver
coherence : 3.5.0
Caused by: java.lang.IllegalStateException: decimal value exceeds IEEE754r 128-bit range: 7777777788888888888899999999999900000000000000044444444444447777777777777.00
at com.tangosol.io.pof.PofHelper.calcDecimalSize(PofHelper.java:1517)
at com.tangosol.io.pof.PofBufferWriter.writeBigDecimal(PofBufferWriter.java:562)
at com.tangosol.io.pof.PofBufferWriter.writeObject(PofBufferWriter.java:1325)
at com.tangosol.io.pof.PofBufferWriter$UserTypeWriter.writeObject(PofBufferWriter.java:2092)
at com.apx.core.datalayer.data.basictypes.BigDecimalMoneyImpl.writeExternal(BigDecimalMoneyImpl.java:127)
at com.tangosol.io.pof.PortableObjectSerializer.serialize(PortableObjectSerializer.java:88)
at com.tangosol.io.pof.PofBufferWriter.writeObject(PofBufferWriter.java:1439)
at com.tangosol.io.pof.PofBufferWriter$UserTypeWriter.writeObject(PofBufferWriter.java:2092)
at com.apx.instrument.datalayer.data.domain.impl.DOtcInstrumentImpl.writeExternal(DOtcInstrumentImpl.java:200)
at com.apx.core.datalayer.data.impl.AbstractDomainObject.writeExternal(AbstractDomainObject.java:109)
... 185 more
at com.tangosol.coherence.ra.component.connector.resourceAdapter.cciAdapter.CacheAdapter$ManagedConnection$LocalTransaction.commit(CacheAdapter.CDB:37)
at weblogic.connector.security.layer.AdapterLayer.commit(AdapterLayer.java:570)
at weblogic.connector.transaction.outbound.NonXAWrapper.commit(NonXAWrapper.java:84)
at weblogic.transaction.internal.NonXAServerResourceInfo.commit(NonXAServerResourceInfo.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2251)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:270)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:283)
at $Proxy150.create(Unknown Source)
javax.resource.spi.LocalTransactionException: CoherenceRA: Commit failed:
java.lang.RuntimeException: error with the class: com.apx.instrument.datalayer.data.domain.impl.DOtcInstrumentImpl
at com.apx.core.datalayer.data.impl.AbstractDomainObject.writeExternal(AbstractDomainObject.java:111)
at com.tangosol.io.pof.PortableObjectSerializer.serialize(PortableObjectSerializer.java:88)
at com.tangosol.io.pof.PofBufferWriter.writeObject(PofBufferWriter.java:1439)
at com.tangosol.io.pof.ConfigurablePofContext.serialize(ConfigurablePofContext.java:338)
at com.tangosol.util.ExternalizableHelper.serializeInternal(ExternalizableHelper.java:2508)
at com.tangosol.util.ExternalizableHelper.toBinary(ExternalizableHelper.java:205)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ConverterValueToBinary.convert(DistributedCache.CDB:3)
at com.tangosol.util.ConverterCollections$AbstractConverterEntry.getValue(ConverterCollections.java:3333)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$BinaryMap.putAll(DistributedCache.CDB:19)
at com.tangosol.util.ConverterCollections$ConverterMap.putAll(ConverterCollections.java:1570)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ViewMap.putAll(DistributedCache.CDB:1)
at com.tangosol.coherence.component.util.SafeNamedCache.putAll(SafeNamedCache.CDB:1)
at com.tangosol.coherence.component.util.collections.WrapperMap.putAll(WrapperMap.CDB:1)
at com.tangosol.coherence.component.util.DeltaMap.resolve(DeltaMap.CDB:9)
at com.tangosol.coherence.component.util.deltaMap.TransactionMap.commit(TransactionMap.CDB:1)
at com.tangosol.coherence.component.util.TransactionCache.commit(TransactionCache.CDB:14)
at com.tangosol.coherence.component.util.transactionCache.Local.commit(Local.CDB:1)
at com.tangosol.coherence.ra.component.connector.resourceAdapter.cciAdapter.CacheAdapter$ManagedConnection$LocalTransaction.commit(CacheAdapter.CDB:25)
at weblogic.connector.security.layer.AdapterLayer.commit(AdapterLayer.java:570)
at weblogic.connector.transaction.outbound.NonXAWrapper.commit(NonXAWrapper.java:84)
at weblogic.transaction.internal.NonXAServerResourceInfo.commit(NonXAServerResourceInfo.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2251)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:270)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:230)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:283)
at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1009)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723)
at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:374)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)

Hi SR-APX
The problem is that even though you are using the JCA adaptor Coherence (pre-3.6) is not really transactional. Once you commit all that data is still being pushed out to the distributed cluster members who all work independently. An error on one member will not stop data being written successfully to others.
In Coherence 3.6 there are real transactions but you would need to see if the limitations on them fit your use-cases.
JK

Cache update not yet started In PI 7.1

Hi
Iu2019m using PI 7.1, facing the issue with Cache Update
Under Integration Builder -> Environment -> Cache Notifications
Central Adapter Engine, Mapping Runtime Cache (Central Adapter Engine) both are in gray color status (Cache update not yet started) .
Cache Connectivity Test in RWB
RWB -->Component Monitoring --> Cache Connectivity Test
For both Central Adapter Engine, Mapping Runtime Cache on Central Adapter Engine
Showing the warning
      "--Attempt to fetch cache data from Integration Directory not yet started or still in process"_
Please help me out to update the Cache successfully
Thanks
Vadde

Hi Sekher
Thank you very much for your time,
1 RFC- INTEGRATION_DIRECTORY_HMI is working fine.
2. I du2019t find the com.sap.aii.af.cpa.svc service in NWA ,
3 Under Config Tool
    template - Usage_Type_All_in_One - Services - com.sap.aii.af.cpa.svc
   "CacheType" has the value "DIRECTORYu201D only
Thanks
Vadde

ID cache update issue

Hi all :
I have a problem with ID cache update on PI 7.0. I change some configretion on ID and active them .
I check some issues on cache notification ,the update status is red (not yet start ) or yellow (strated).
I refresh status for cache ,the status is not any update .
I update the CAPcache , but the status is waiting and then no responseable .
Please give me a hand , what can i do for solve this issue .
Thanks a lot
yanbin
Best regard

Hi Rajendar K:
I just run the url :http://host:50000/CPACache/refresh?mode=full, but not response.
Please see below screenshot,
BTW ,my issue is in cache update for central adapter engine.

Cache update / Missing objects

Dear all!
Since two days we have following problem:
After activating changes in integration directory sometimes the changes are not transmitted to the Runtime Cache, sometimes they are. The Status is everytime "green". A manually (full and delta) refresh is not succesfull (means status is still green, no error message is displayed but the objects are still missing). I.e. i can see only five of eight configured communication channels.
I read the thread "Automtic Cache Update is not done !!
Any ideas?
Kind regards,
Klaus Leng

Hi Klaus,
Which parts are showing up yellow.
For me it was the Integration Engine - adapter component.
In my case I had to reset the password for the SAP XI AF CPA cache component in the visual administrator.
Also make sure you haven't changed any of the standard users in the exchangeProfile. Because they didn't have enough authorisations I once changed them over there, and that also caused similar problems.
Best regards
Alwin

Cache update problem in Integration Directory

Hi all,
We have a cache update problem in our PI development server.
If we try to edit, save and activate any of the ID objects, under Cache notifications>Central Adapter Engine> all these objects are displayed as gray items.
We have tried:
1. Clearing the SLD Data Cache.
2. Did SXI_CACHE complete refresh.
3. Did CPA cache refresh.
4. Did a complete cache refresh of the server.
5. Restarted the server.
But still the problem has not bee resolved. Could you pls provide your inputs and resolution points.
Thank you very much.
regards,
Jack Nuson

HI Jack ,
first try to manually update the cache from ID select on your cache notifiaction and click on delta cache refresh button and refresh button .IF it does not yied any result then
Perform a full cache refresh using the URL
http://<host>:<port>/CPACache/refresh?mode=full . If the cache refresh happens properly then your problem will get resolved other wise you have to see the cache log to view why it failed there it will show you the exact reason . You might need to restart your java server also if the problem persist .
Regards,
Saurabh

Issues with cache updates

Hi ,
I have some issues with runtime xi cache update.
i tested the RFC dest for connection RFC Dest - INTEGRATION_DIRECTORY_HMI.
that failed with HTTP 500 internal server error .
I even tried to update the cache from TCode - sxi_cache
the error i got there was
Prefix number: entry missing for system XI1 client 200
If anyone has any idea as to why is such an error occuring
Thanks
Nikhil

Hi
<i>that failed with HTTP 500 internal server error .</i>
is not an error
Please can you check on this thread:
XI Runtime cache error: Cache contents are obsolete
Regards
Vijaya

Runtime cache updating

Hi
I have installed XI server (installation,post installation,configuration)accrording to the guide given by SAP. I have done a simple file to file to scenario.
Sender comm channel and Sender agrmnt is not updated in Runtime cache , all other ID objects are updated.
Here our SP No: 9 . Can anybody give any clue?
thanks in advance
N.Prasad Babu

Hi Prasad,
Take a look at these threads..
/people/sravya.talanki2/blog/2005/12/21/convert-any-r3-structure-to-xsd-made-easy-was-60
http://help.sap.com/saphelp_nw04/helpdata/en/97/89bb3f23823c17e10000000a114084/frameset.htm
Cache update / Missing objects
Hope these help you!
cheers,
Prashanth

Photo Cache Update??

Does the iPod Photo Cache update automatically from My Pictures (assuming of course that's where the photos from the camera are stored to begin with.)
If not, is the Photo Cache needed at all? It seems a waste of space to have the same photos in 2 locations. . .

So no one else updates photos?
The acceptable solution to this is to go around and delete everyone's photo cache?

Cache updated date/time is shown as 1970/01/01

When we checked the cache notification for central adapter engine in the cache monitoring , the cache updated date/time is shown as 1970/01/01.
We have tried to do delta cache refresh and complete cache refresh, but we have not got the intended result. Please look in to the problem and let me know if you have any ideas regarding the same.
regards,
KRUSHI

Hi
Check for these SM59 in XI ->http connections -><INTEGRATION_DIRECTORY_HMI > ->test the connection. check is it successful or not.
Also you can do the cache refresh from SLD->Administration->Cache Overview

Cache Update Policy: apply result to the cache

Hello everyone!
I can not run the cache update policy in the object. It does not work!
The test is as follows:
- A sap rfc GETLIST, which returns a recordset. Each record is of type X
- A sap rfc OPERATION that modifies a record of type X and that takes as input the id (primary key) of the line to change, and that returns the entire record X changed (including the id).
- GETLIST is used as definition of mbo Y, while OPERATION is used as definition for an update operation of Y with apply result to the cache set.
- Y is in a cache group set to "scheduled, 1h".
Now, if I run the operation, the line on my bb after synchronization remain the same as before (in the CDB it is not changed), while the SAP system has changed the row.
What's wrong? Please help!
Thanks!

http://infocenter.sybase.com/help/topic/com.sybase.infocenter.dc01283.0155/doc/html/fre1239918764246.html
Have you verified that there are no warnings in eclipse after you choose this particular "cache policy".
If you call the GetList immediately after the operation has been executed from SAPGui, Does it show the new value?
I've heard of situation where the commit of operation in SAP takes time and in case caching is not enabled,
synchronization may cause SUP to call GetList again and if that doesn't return new data, BB is getting
the old data although there is an interim state where the CDB had results of operation applied.
What is the cache validity period for this Cachegroup?
Edited by: Himagiri Mukkamala on Feb 10, 2011 8:57 AM

JMS Cache updates in existing transactions

We have two application instances running, with synchronization over JMS. In the following scenario what will be the outome?
- AppInstance1 does changes to Object1 and commits. These changes are sent to the JMS queue.
- AppInstance2 is in the middle of one transaction when it recieves the cache updates. The current transaction include Object1 (which updates are received for).
Does the transaction in Instance2 get aborted upon receiving the cache sync or are the mechanisms at work in TopLink smart enough to merge the non conflicting fields?
Thanks,
Anders,

This depends on your locking mechanism and has little to do with cache-synch. Cache synchronization does not replace the requirement for a locking mechanism.
If you are using no locking, then no matter if you have a single server, multiple servers with or without cache synch, then there is the potential that concurrent transactions can overwrite each others data.
If you are using optimistic locking, then no matter if you have a single server, multiple servers with or without cache synch, your second transaction will get an optimistic lock error and its transaction will be rolled-back.
If you are using pessimistic locking, then there is not much point in using cache synch as you will be accessing the database anyway. The second transaction will block on its read of the object until the first transaction completes, or throw an error on read if using no_wait.
The benefit that cache synchronization provides it that because changes are synchronized between servers the likely-hood of getting an optimistic lock exception is greatly reduced. It can also be used with infrequently updated objects that do not use any locking, or object to which locking is not an issue.

Cache Update XIServer

Similar Messages

Maybe you are looking for