« Return to Thread: Problems with deploying Grails-App with Search-Pluging
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
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
« Return to Thread: Problems with deploying Grails-App with Search-Pluging
| Free Forum Powered by Nabble | Forum Help |
