One more problem I encounter:

I started a tomcat once and deployed successfully drool workbench as there is no previous existing tomcat service is running.

But if I stop the /drools-wb-6.0.1.Final-tomcat7.0 from tomcat manager and again start same from manager. I encountered this error.
I think , this should not be related to tomcat . Its something with drool war.

Highlight of error:

Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a thread named [pool-4-thread-1] but has failed to stop it. This is very likely to create a memory leak.

Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a thread named [Thread-4] but has failed to stop it. This is very likely to create a memory leak.

Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a thread named [pool-7-thread-1] but has failed to stop it. This is very likely to create a memory leak.

Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a thread named [com.google.inject.internal.util.$Finalizer] but has failed to stop it. This is very likely to create a memory leak.

Jan 18, 2014 8:17:51 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/drools-wb-6.0.1.Final-tomcat7.0] appears to have started a thread named [Thread-5] but has failed to stop it. This is very likely to create a memory leak.

Full Error:

http://pastebin.com/75tAuZvu

Should I log this into jira ?

--

Mohit

On Sat, Jan 18, 2014 at 8:15 PM, Mohit Srivastava <srivastavamohit91@gmail.com> wrote:

I think thats a tomcat problem. its not shutting down properly.

But here is something new :

2014-01-18 20:13:39,469 [localhost-startStop-1] ERROR Failed to setup Repository 'uf-playground'

java.lang.RuntimeException: https://github.com/guvnorngtestuser1/guvnorng-playground.git: cannot open git-upload-pack

On Sat, Jan 18, 2014 at 8:01 PM, Mohit Srivastava <srivastavamohit91@gmail.com> wrote:

Yeah, It happens sometimes and sometimes it works normally. 

But I changes the port of tomcat as well as I restart the whole machine. Then I start the service which already deployed(i.e. drools one) and I encountered the same error.

And If there is any instance , then any Idea why they are not shutdown , while stopping tomcat ? 

On Sat, Jan 18, 2014 at 7:56 PM, Michael Anstis <michael.anstis@gmail.com> wrote:

Is the error message following a stop/restart of Tomcat? The message indicates an instance of the application may already be running or not shutdown correctly.

Sent on the move

On 18 Jan 2014 14:20, "Mohit Srivastava" <srivastavamohit91@gmail.com> wrote:

Hi Everyone,

I tried to deploy drool-workbench on tomcat 7 . But I have encountered with errors.

I am unable to figure out the reason, I like to get some help from you guys .

2014-01-18 19:44:12,202 [http-bio-8081-exec-2] INFO  KieModule was added:ZipKieModule[ ReleaseId=org.drools:drools-wb-rest-defaultapprover:6.0.1.Finalfile=/usr/tomcat/apache-tomcat-7.0.50/webapps/drools-wb-6.0.1.Final-tomcat7.0/WEB-INF/lib/drools-wb-rest-defaultapprover-6.0.1.Final.jar]

2014-01-18 19:44:17,512 [http-bio-8081-exec-2] ERROR Failed to setup Repository 'uf-playground'

java.lang.RuntimeException: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@/.index/write.lock

at org.uberfire.metadata.backend.lucene.setups.DirectoryLuceneSetup.<init>(DirectoryLuceneSetup.java:78) ~[uberfire-metadata-backend-lucene-0.3.1.Final.jar:0.3.1.Final]

at org.uberfire.metadata.backend.lucene.setups.NIOLuceneSetup.<init>(NIOLuceneSetup.java:31) ~[uberfire-metadata-backend-lucene-0.3.1.Final.jar:0.3.1.Final]

2014-01-18 19:44:17,926 [http-bio-8081-exec-2] ERROR Can't initialize FileSystemProviders

java.util.ServiceConfigurationError: org.uberfire.java.nio.file.spi.FileSystemProvider: Provider org.uberfire.java.nio.fs.jgit.JGitFileSystemProvider could not be instantiated: org.uberfire.java.nio.IOException: java.net.BindException: Address already in use

Thanks 

--

Mohit

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users