xodus

问题 When caching https://github.com/JetBrains/xodus/blob/master/openAPI/src/main/java/jetbrains/exodus/env/Environment.java with EHCache it throws: Caused by: org.ehcache.spi.serialization.UnsupportedTypeException: No serializer found for type 'jetbrains.exodus.env.Environment' at org.ehcache.impl.internal.spi.serialization.DefaultSerializationProvider.getSerializerClassFor(DefaultSerializationProvider.java:136) at org.ehcache.impl.internal.spi.serialization.DefaultSerializationProvider

问题 Since it possible for one JVM process to write to Xodus and other JVM to read to the same environment, what is the correct way for a JVM process or method to remove the lock of the environment at end of every transaction as such other JVM processes would be able to write to the same environment at their own respective transactions? 回答1: The xd.lck file is never being removed, it is being locked by an Environment which is allowed to write. For implementation details, look at LockingManager. If

问题 Since it possible for one JVM process to write to Xodus and other JVM to read to the same environment, what is the correct way for a JVM process or method to remove the lock of the environment at end of every transaction as such other JVM processes would be able to write to the same environment at their own respective transactions? 回答1: The xd.lck file is never being removed, it is being locked by an Environment which is allowed to write. For implementation details, look at LockingManager. If

问题 Since it possible for one JVM process to write to Xodus and other JVM to read to the same environment, what is the correct way for a JVM process or method to remove the lock of the environment at end of every transaction as such other JVM processes would be able to write to the same environment at their own respective transactions? 回答1: The xd.lck file is never being removed, it is being locked by an Environment which is allowed to write. For implementation details, look at LockingManager. If

问题 Since it possible for one JVM process to write to Xodus and other JVM to read to the same environment, what is the correct way for a JVM process or method to remove the lock of the environment at end of every transaction as such other JVM processes would be able to write to the same environment at their own respective transactions? 回答1: The xd.lck file is never being removed, it is being locked by an Environment which is allowed to write. For implementation details, look at LockingManager. If

问题 What would cause this exception to be thrown? Caused by: javax.management.InstanceAlreadyExistsException: jetbrains.exodus.entitystore: type=EntityStoreConfig, location=/var/xodus/master, name=persistentEntityStore at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean

来源： https://stackoverflow.com/questions/63211112/how-does-jetbrains-youtrack-server-scales-over-load

来源： https://stackoverflow.com/questions/63786000/removing-lock-on-non-graceful-application-shutdown

问题 When trying to upload a file using VFS my app throws this error, what could be wrong in my code: jetbrains.exodus.ExodusException: Unexpected root page type: -99 at jetbrains.exodus.tree.patricia.PatriciaTree.<init>(PatriciaTree.java:37) at jetbrains.exodus.env.StoreImpl.openImmutableTree(StoreImpl.java:220) at jetbrains.exodus.env.TransactionBase.getTree(TransactionBase.java:125) at jetbrains.exodus.env.ReadWriteTransaction.getTree(ReadWriteTransaction.java:186) at jetbrains.exodus.env

问题 My app is throwing this error, what could be the main problem?: jetbrains.exodus.log.BlockNotFoundException: Address is out of log space, overflow, address = 6225920, file = 00000000000.xd at jetbrains.exodus.log.BlockNotFoundException.raise(BlockNotFoundException.java:28) at jetbrains.exodus.log.Log.readBytes(Log.kt:776) at jetbrains.exodus.log.LogCache.readBytes(LogCache.java:134) at jetbrains.exodus.log.LogCache.readFullPage(LogCache.java:111) at jetbrains.exodus.log.SharedLogCache.getPage