Problems with deploying Grails-App with Search-Pluging
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
Problems with deploying Grails-App with Search-Pluging
by habi
::
Rate this Message:
I have a Grails App that uses the Searchable Plugin. This app is working fine with run-app in Jetty. But if i try to deploy the application on a tomcat server it fails.
If i look in the cataline-log file i can see the following exception. Has anyone an idea whats going wrong??? 17.07.2008 09:44:05 org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load org.compass.core.impl.DefaultCompass$TransactionalSearchEngineOptimizer$2. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1246) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1206) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at org.compass.core.impl.DefaultCompass$TransactionalSearchEngineOptimizer.optimize(DefaultCompass.java:519) at org.compass.core.lucene.engine.optimizer.ScheduledLuceneSearchEngineOptimizer.optimize(ScheduledLuceneSearchEngineOptimizer.java:104) at org.compass.core.lucene.engine.optimizer.AbstractLuceneSearchEngineOptimizer.optimize(AbstractLuceneSearchEngineOptimizer.java:78) at org.compass.core.impl.DefaultCompass$TransactionalSearchEngineOptimizer.optimize(DefaultCompass.java:495) at org.compass.core.lucene.engine.optimizer.ScheduledLuceneSearchEngineOptimizer.optimize(ScheduledLuceneSearchEngineOptimizer.java:96) at org.compass.core.lucene.engine.optimizer.ScheduledLuceneSearchEngineOptimizer$ScheduledOptimizeRunnable.run(ScheduledLuceneSearchEngineOptimizer.java:128) at org.compass.core.util.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:443) at org.compass.core.util.backport.java.util.concurrent.FutureTask.runAndReset(FutureTask.java:198) at org.compass.core.util.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:103) at org.compass.core.util.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:190) at org.compass.core.util.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:214) at org.compass.core.util.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at org.compass.core.util.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) |
|
|
Re: Problems with deploying Grails-App with Search-Pluging
by Daniel Honig
::
Rate this Message:
Do you have write permissons where lucene is trying to create the index files?
On Thu, Jul 17, 2008 at 5:36 AM, habi <Timo.Haberkern@...> wrote: > > I have a Grails App that uses the Searchable Plugin. This app is working fine > with run-app in Jetty. But if i try to deploy the application on a tomcat > server it fails. > > If i look in the cataline-log file i can see the following exception. Has > anyone an idea whats going wrong??? > > 17.07.2008 09:44:05 org.apache.catalina.loader.WebappClassLoader loadClass > INFO: Illegal access: this web application instance has been stopped > already. Could not load > org.compass.core.impl.DefaultCompass$TransactionalSearchEngineOptimizer$2. > The eventual following stack trace is caused by an error thrown for > debugging purposes as well as to attempt to terminate the thread which > caused the illegal access, and has no functional impact. > java.lang.IllegalStateException > at > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1246) > at > org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1206) > at java.lang.ClassLoader.loadClassInternal(Unknown Source) > at > org.compass.core.impl.DefaultCompass$TransactionalSearchEngineOptimizer.optimize(DefaultCompass.java:519) > at > org.compass.core.lucene.engine.optimizer.ScheduledLuceneSearchEngineOptimizer.optimize(ScheduledLuceneSearchEngineOptimizer.java:104) > at > org.compass.core.lucene.engine.optimizer.AbstractLuceneSearchEngineOptimizer.optimize(AbstractLuceneSearchEngineOptimizer.java:78) > at > org.compass.core.impl.DefaultCompass$TransactionalSearchEngineOptimizer.optimize(DefaultCompass.java:495) > at > org.compass.core.lucene.engine.optimizer.ScheduledLuceneSearchEngineOptimizer.optimize(ScheduledLuceneSearchEngineOptimizer.java:96) > at > org.compass.core.lucene.engine.optimizer.ScheduledLuceneSearchEngineOptimizer$ScheduledOptimizeRunnable.run(ScheduledLuceneSearchEngineOptimizer.java:128) > at > org.compass.core.util.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:443) > at > org.compass.core.util.backport.java.util.concurrent.FutureTask.runAndReset(FutureTask.java:198) > at > org.compass.core.util.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:103) > at > org.compass.core.util.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:190) > at > org.compass.core.util.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:214) > at > org.compass.core.util.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) > at > org.compass.core.util.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) > -- > View this message in context: http://www.nabble.com/Problems-with-deploying-Grails-App-with-Search-Pluging-tp18504802p18504802.html > Sent from the grails - user mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Problems with deploying Grails-App with Search-Pluging
by habi
::
Rate this Message:
it is a windowsserver so there should be no permission restrictions
|
|
|
Re: Problems with deploying Grails-App with Search-Pluging
by Siddharth Bala Ravi
::
Rate this Message:
Did you specify the path to store your index file
in the SearchableConfiguration.groovy file? By default this should be
something like this:
String compassConnection = SearchableCompassUtils.getDefaultConnection() In this case, you will need permissions to write to this folder (usually is found at <drive letter>:\Documents and Settings\<profile name>\.grails\projects\<project name>\searchable-index\<development or production>\index\<Index Name> if you have changed to default location to write to some other folder, then you should ensure that the appropriate permissions are granted. On the other hand, if you are storing the index in memory, then this error should just go away (you may want to use this case to test whether your issue is related to permission denial) HTH --Sid habi wrote: it is a windowsserver so there should be no permission restrictions Daniel Honig wrote:Do you have write permissons where lucene is trying to create the index files? On Thu, Jul 17, 2008 at 5:36 AM, habi Timo.Haberkern@... wrote: |
|
|
Re: Problems with deploying Grails-App with Search-Pluging
by habi
::
Rate this Message:
thanks for the ideas but none of them helped. Still ahve the problem even if i use the ramdiak
Timo
|
|
|
Re: Problems with deploying Grails-App with Search-Pluging
by Daniel Honig
::
Rate this Message:
Sorry I cant pinpoint it better.
But this is all due-dillgence to try to isolate potential problems. Let us know if the index is going to memory or the filesytem. I believe default is the filesystem. So do you know how to find your indexes and manually delete them? Weird things happen when trying to index your domain classes and you already have an index in some sort of invalid state. Before proceeding we need to make sure that we are starting fresh? and when you run run-app or test-app or run-war? no problems? On Thu, Jul 17, 2008 at 11:21 AM, habi <Timo.Haberkern@...> wrote: > > thanks for the ideas but none of them helped. Still ahve the problem even if > i use the ramdiak > > Timo > > > habi wrote: >> >> it is a windowsserver so there should be no permission restrictions >> >> >> Daniel Honig wrote: >>> >>> Do you have write permissons where lucene is trying to create the index >>> files? >>> >>> On Thu, Jul 17, 2008 at 5:36 AM, habi <Timo.Haberkern@...> >>> wrote: >>>> >>>> I have a Grails App that uses the Searchable Plugin. This app is working >>>> fine >>>> with run-app in Jetty. But if i try to deploy the application on a >>>> tomcat >>>> server it fails. >>>> >>>> If i look in the cataline-log file i can see the following exception. >>>> Has >>>> anyone an idea whats going wrong??? >>>> >>>> 17.07.2008 09:44:05 org.apache.catalina.loader.WebappClassLoader >>>> loadClass >>>> INFO: Illegal access: this web application instance has been stopped >>>> already. Could not load >>>> org.compass.core.impl.DefaultCompass$TransactionalSearchEngineOptimizer$2. >>>> The eventual following stack trace is caused by an error thrown for >>>> debugging purposes as well as to attempt to terminate the thread which >>>> caused the illegal access, and has no functional impact. >>>> java.lang.IllegalStateException >>>> at >>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1246) >>>> at >>>> org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1206) >>>> at java.lang.ClassLoader.loadClassInternal(Unknown Source) >>>> at >>>> org.compass.core.impl.DefaultCompass$TransactionalSearchEngineOptimizer.optimize(DefaultCompass.java:519) >>>> at >>>> org.compass.core.lucene.engine.optimizer.ScheduledLuceneSearchEngineOptimizer.optimize(ScheduledLuceneSearchEngineOptimizer.java:104) >>>> at >>>> org.compass.core.lucene.engine.optimizer.AbstractLuceneSearchEngineOptimizer.optimize(AbstractLuceneSearchEngineOptimizer.java:78) >>>> at >>>> org.compass.core.impl.DefaultCompass$TransactionalSearchEngineOptimizer.optimize(DefaultCompass.java:495) >>>> at >>>> org.compass.core.lucene.engine.optimizer.ScheduledLuceneSearchEngineOptimizer.optimize(ScheduledLuceneSearchEngineOptimizer.java:96) >>>> at >>>> org.compass.core.lucene.engine.optimizer.ScheduledLuceneSearchEngineOptimizer$ScheduledOptimizeRunnable.run(ScheduledLuceneSearchEngineOptimizer.java:128) >>>> at >>>> org.compass.core.util.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:443) >>>> at >>>> org.compass.core.util.backport.java.util.concurrent.FutureTask.runAndReset(FutureTask.java:198) >>>> at >>>> org.compass.core.util.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:103) >>>> at >>>> org.compass.core.util.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:190) >>>> at >>>> org.compass.core.util.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:214) >>>> at >>>> org.compass.core.util.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) >>>> at >>>> org.compass.core.util.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/Problems-with-deploying-Grails-App-with-Search-Pluging-tp18504802p18504802.html >>>> Sent from the grails - user mailing list archive at Nabble.com. >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >>> >> >> > > -- > View this message in context: http://www.nabble.com/Problems-with-deploying-Grails-App-with-Search-Pluging-tp18504802p18510978.html > Sent from the grails - user mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: Problems with deploying Grails-App with Search-Pluging
by habi
::
Rate this Message:
Hi,
the application works with run-app and run-war. No problem there. But if I want to deploy the application on a tomecat server i get this error. Startup always fails. I have tested it with all combinations (RAM-Disk, Default-Location, Fix path) nothing worked. This occures on two systems, so it seems not to be system dependend. I run windows (XP and server 2003) with Tomcat 6.0.16, grails 1.0.2 and SearchablePlugin 0.42 Snapshot Timo
|
| Free Forum Powered by Nabble | Forum Help |