This question is locked. New answers and comments are not allowed.
Hi,
I am attempting to move a legacy application
The visual studio plugin has been upgraded.
The references/assemblies for the specific ORM project have been upgraded
The project uses "forward mapping" with the mappings defined in the app.config of the ORM project.
The App.Config/Web.Config configuration remains as is - I have not upgrade from "Classic" to the newer ORM configuration(rlinq?)
The application now runs and is capable of using the existing model classes. It is using ObjectScope to get the database.
However the project uses MSMQ for caching.
I am seeing the following error logged by telerik through the tracewriter
Unable to use one of the configured queues. LocalPath setting is 'CacheEvict-Q'. Original Exceptions:
System.Messaging.MessageQueueException: Sharing violation resulted from queue being open already for exclusive receive.
at System.Messaging.MessageQueue.MQCacheableInfo.get_ReadHandle()
at System.Messaging.MessageQueue.StaleSafePurgeQueue()
at System.Messaging.MessageQueue.Purge()
at OpenAccessRuntime.MSMQClusterImpl.CheckAndCreateReceiveQueues(String path)
Here are the web.config settings being used
<l2CacheEnabled>true</l2CacheEnabled>
<l2CacheClusterTransport>MSMQ</l2CacheClusterTransport>
<l2CacheClusterTransport.multicastaddr>224.2.1.145:8000</l2CacheClusterTransport.multicastaddr>
<l2CacheClusterTransport.localpath>CacheEvict-Q</l2CacheClusterTransport.localpath>
<l2QueryCacheEnabled>false</l2QueryCacheEnabled>
<l2QueryCacheMaxObjectsPerQuery>5000</l2QueryCacheMaxObjectsPerQuery>
<l2CacheMaxObjects>20000</l2CacheMaxObjects>
<l2QueryCacheMaxQueries>2000</l2QueryCacheMaxQueries>
The error seems to go away if I manually delete the queue through "Computer Management->Services and Applications->Message Queuing->Private Queues"
After deleting the queue, I do a page refresh and the ORM recreates the private queue and does not throw the exception.
But the problem returns after an IISreset and page refresh.
thanks
fraser
I am attempting to move a legacy application
FROM: 'Telerik.OpenAccess, Version=2011.1.316.10, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342'
TO: 'Telerik.OpenAccess, Version=2013.3.1014.1, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342'
The visual studio plugin has been upgraded.
The references/assemblies for the specific ORM project have been upgraded
The project uses "forward mapping" with the mappings defined in the app.config of the ORM project.
The App.Config/Web.Config configuration remains as is - I have not upgrade from "Classic" to the newer ORM configuration(rlinq?)
The application now runs and is capable of using the existing model classes. It is using ObjectScope to get the database.
However the project uses MSMQ for caching.
I am seeing the following error logged by telerik through the tracewriter
Unable to use one of the configured queues. LocalPath setting is 'CacheEvict-Q'. Original Exceptions:
System.Messaging.MessageQueueException: Sharing violation resulted from queue being open already for exclusive receive.
at System.Messaging.MessageQueue.MQCacheableInfo.get_ReadHandle()
at System.Messaging.MessageQueue.StaleSafePurgeQueue()
at System.Messaging.MessageQueue.Purge()
at OpenAccessRuntime.MSMQClusterImpl.CheckAndCreateReceiveQueues(String path)
Here are the web.config settings being used
<l2CacheEnabled>true</l2CacheEnabled>
<l2CacheClusterTransport>MSMQ</l2CacheClusterTransport>
<l2CacheClusterTransport.multicastaddr>224.2.1.145:8000</l2CacheClusterTransport.multicastaddr>
<l2CacheClusterTransport.localpath>CacheEvict-Q</l2CacheClusterTransport.localpath>
<l2QueryCacheEnabled>false</l2QueryCacheEnabled>
<l2QueryCacheMaxObjectsPerQuery>5000</l2QueryCacheMaxObjectsPerQuery>
<l2CacheMaxObjects>20000</l2CacheMaxObjects>
<l2QueryCacheMaxQueries>2000</l2QueryCacheMaxQueries>
The error seems to go away if I manually delete the queue through "Computer Management->Services and Applications->Message Queuing->Private Queues"
After deleting the queue, I do a page refresh and the ORM recreates the private queue and does not throw the exception.
But the problem returns after an IISreset and page refresh.
thanks
fraser