On Wed, May 25, 2011 at 8:41 PM, Anjana Fernando <[email protected]> wrote:
> Hi Sumedha, Azeez, > > First, this was not caused by tm.out.lck at /repository/logs, but from the > file "tmlog.lck" at /repository/data. I verified this by separately locking > both of these files manually and check which one throws the error, and I > also checked the Atomikos source code [1] to check where the error came > from. > > Just to be clear, these logs are not the usual text logs, but are the > transaction logs. These are used for the transaction recovery purposes. So > for the Azeez's question on, if we can get rid of the logs, no we can't. > Also when running many instances, basically I guess this would result in > multiple WAR files, in that case, we simply have to include separate > "transaction.properties" inside the WAR files, in a classpath location. And > inside the "transaction.properties" file, you define where the logs files > will be located. > Yes, that is an acceptable solution > > As for the error Sumedha got, this is not a usual thing that happens, also, > a property has been set in transaction.properties > (com.atomikos.icatch.force_shutdown_on_vm_exit), which cleans up the > resources and closes the log files and so on. So seems Sumedha terminated > the JVM too abruptly, that even that didn't happen. I actually tried a > "killall -9 java" in Ubuntu, and that didn't cause any problems, maybe Mac > OS behaves differently. So IMHO, I see this as to be a rare situation that > the user will encounter, and is a known issue, where a simple Google query > tells what the user have to do in order to recover from it. > > On Mac OS X I have used kill -9 many times, and I have never seen this failure. Anyway, since Sumedha came across this, it is highly likely that one of our users will see it. But yes, we can leave it as it is. > [1] > http://grepcode.com/file/repo1.maven.org/maven2/com.atomikos/transactions-jta/3.6.4/com/atomikos/icatch/standalone/UserTransactionServiceImp.java > > Cheers, > Anjana. > > > On Wed, May 25, 2011 at 6:53 PM, Afkham Azeez <[email protected]> wrote: > >> This also means that you cannot start two JVM instances by pointing to the >> same CARBON_HOME. Think of a scenario where Carbon is running within two >> appservers as a webapp. It should be possible to point to the same >> CARBON_HOME and run both instances. Can we get rid of this log check? >> >> >> On Wed, May 25, 2011 at 6:41 PM, Sumedha Rubasinghe <[email protected]>wrote: >> >>> I just killed running instance of a server & tried re-booting. >>> >>> [2011-05-25 18:33:48,741] INFO >>> {org.wso2.carbon.atomikos.TransactionFactory} - Starting Atomikos >>> Transaction Manager 3.7.0 >>> ERROR: the specified log seems to be in use already. Make sure that no >>> other instance is running, or kill any pending process if needed. >>> java.lang.RuntimeException: Log already in use? >>> 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 normally. >>> >>> -rw-r--r-- 1 sumedha staff 4358 May 25 15:00 tm.out >>> -rw-r--r-- 1 sumedha staff 0 May 25 18:33 tm.out.1 >>> -rw-r--r-- 1 sumedha staff 0 May 25 18:33 tm.out.lck >>> >>> But, shouldn't we deal with gracefully? >>> >>> Created a JIRA[1] for future checkups. >>> >>> /sumedha >>> >>> [1] https://wso2.org/jira/browse/CARBON-10291 >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> > > > -- > *Anjana Fernando* > Senior Software Engineer > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
