Contact Us

Home > Error The > Error The Specified Log Seems To Be In Use Already

Error The Specified Log Seems To Be In Use Already

like, are those running in an app server, where it is pointed to a single CARBON_HOME? .. Enterprise . I'm sure we will see forum & support queries about this. current community chat Stack Overflow Meta Stack Overflow your communities Sign up or log in to customize your list.

No further replies will be accepted. This error comes when more that one instance is trying to access the same transaction log file of Atomikos, or there's also a chance that the earlier JVM shutdown was not Can we get rid of this log check? > > > On Wed, May 25, 2011 at 6:41 PM, Sumedha Rubasinghe wrote: > > > I just killed running instance of at com.atomikos.icatch.standalone.UserTransactionServiceImp.createDefault(UserTransactionServiceImp.java:246) at com.atomikos.icatch.standalone.UserTransactionServiceImp.init(UserTransactionServiceImp.java:306) at com.atomikos.icatch.config.UserTransactionServiceImp.init(UserTransactionServiceImp.java:413) at com.atomikos.icatch.jta.UserTransactionManager.checkSetup(UserTransactionManager.java:90) at com.atomikos.icatch.jta.UserTransactionManager.init(UserTransactionManager.java:140) at org.wso2.carbon.atomikos.TransactionFactory.initTxManager(TransactionFactory.java:37) This is due to the lock file (tm.out.lck) created by atomikos in repository/log folder & deleting it makes the http://stackoverflow.com/questions/12305700/solve-error-log-already-in-use-with-atomikos-with-multiple-instances

the problem is that for your free open source version you hard coded default properties in the code , so if any user ties to set it from the property file at com.atomikos.icatch.standalone.UserTransactionServiceImp.createDefault(UserTransactionServiceImp.java:246) at com.atomikos.icatch.standalone.UserTransactionServiceImp.init(UserTransactionServiceImp.java:306) at com.atomikos.icatch.config.UserTransactionServiceImp.init(UserTransactionServiceImp.java:413) at com.atomikos.icatch.jta.UserTransactionManager.checkSetup(UserTransactionManager.java:90) at com.atomikos.icatch.jta.UserTransactionManager.init(UserTransactionManager.java:140) at org.wso2.carbon.atomikos.TransactionFactory.initTxManager(TransactionFactory.java:37)This is due to the lock file (tm.out.lck) created by atomikos in repository/log folder & deleting it makes the server boot up Thanks.

Normally, it suffices to follow the hints and then delete the lock file manually if needed. And inside the "transaction.properties" file, you define where the logs files will be located. if so, the "transaction.properties" file have to be removed from /repository/lib and should be put into each WARs classpath location. Other recent topics Powered by FogBugz (Not logged on)Register|Log OnLoading...Loading...FogBugz Documentation and SupportGet Help Now (Contact Us)Keyboard ShortcutsAbout FogBugzLoading...

at org.wso2.carbon.server.Main.startServer(Main.java:66) at org.wso2.carbon.server.Main.start(Main.java:156) ... 6 more Caused by: com.atomikos.icatch.SysException: Error in init(): Log already in use? It should be possible to point to the same CARBON_HOME and run both instances. So if it the JVM was shutdown in an unexpected situation, it can be that the lock file wasn't deleted/released, thus getting the mentioned error. Source So seems Sumedha terminated the JVM too abruptly, that even that didn't happen.

enterprise . Can we get rid of this log check?



On Wed, May 25, 2011 at 6:41 PM, \ Sumedha Rubasinghe <[email protected]> wrote:
And inside the "transaction.properties" file, you define where the logs files will be located. so what should i do now ? –Mihir Sep 7 '12 at 6:44 add a comment| up vote 0 down vote A little late maybe, but this typically happens if you Cheers, Anjana.

Here's my Spring transaction manager config as it stands now: