Grails › Grails - user

Native Library jline_.dll already loaded in another classloader

Classic

List

Threaded

12 messages Options

mtyson

Native Library jline_.dll already loaded in another classloader

I am seeing the following error when trying to run various grails tasks (like generate-controller) from the String STS ide. It seems like this start after I installed EGit, but I'm not sure about that.

Anyone seen things like this before?

Error:

An internal error occurred during: "Building workspace".

Native Library C:\Users\mtyson\AppData\Local\Temp\jline_.dll already loaded in another classloader

Thanks,

Matt Tyson

Rclanahan

RE: Native Library jline_.dll already loaded in another classloader

Yes…. I’m getting this too. Just attempted to upgrade a grails 1.3.5 project to grails 2.1… and also upgraded my sts edi to 2.9.2 from 2.8.1. I’m getting this same error and cannot find any useful information on how to correct it. It is difficult for me to believe that grail 2.1 is the direct cause. I am running windows 7… and here is the error message I get. I get it when I do practically anything, but this message is when I do a project clean and rebuild.

Errors occurred during the build.

Errors running builder 'Java Builder' on project 'xxxgrails'.

Native Library C:\Users\RClanahan\AppData\Local\Temp\jline_.dll already loaded in another classloader

From: Matthew Tyson [mailto:[hidden email]]
Sent: Saturday, July 07, 2012 8:03 PM
To: [hidden email]
Subject: [grails-user] Native Library jline_.dll already loaded in another classloader

Anyone seen things like this before?

Error:

An internal error occurred during: "Building workspace".

Native Library C:\Users\mtyson\AppData\Local\Temp\jline_.dll already loaded in another classloader

Thanks,

Matt Tyson

mtyson

Re: Native Library jline_.dll already loaded in another classloader

Randy,

Here's what I found.

You are running run-app in spring eclipse (either debug or just straight). You run 'grails clean' in spring eclipse. Now, the console no longer shows the app is running, you assume that the run-app process is gone. You attempt to run-app (either debug or straight), again. You get the .dll error.

Open the task manager. You'll see the run-app java process is still alive. Kill it (its the less memory intensive process vs. eclipse). Attempt to run-app now - it should work.

Hopefully, that helps your situation also.

Matt Tyson

On Fri, Jul 20, 2012 at 2:09 PM, Randy Clanahan <[hidden email]> wrote:

Yes…. I’m getting this too. Just attempted to upgrade a grails 1.3.5 project to grails 2.1… and also upgraded my sts edi to 2.9.2 from 2.8.1. I’m getting this same error and cannot find any useful information on how to correct it. It is difficult for me to believe that grail 2.1 is the direct cause. I am running windows 7… and here is the error message I get. I get it when I do practically anything, but this message is when I do a project clean and rebuild.

Errors occurred during the build.

Errors running builder 'Java Builder' on project 'xxxgrails'.

Native Library C:\Users\RClanahan\AppData\Local\Temp\jline_.dll already loaded in another classloader

From: Matthew Tyson [mailto:[hidden email]]
Sent: Saturday, July 07, 2012 8:03 PM
To: [hidden email]
Subject: [grails-user] Native Library jline_.dll already loaded in another classloader

I am seeing the following error when trying to run various grails tasks (like generate-controller) from the String STS ide. It seems like this start after I installed EGit, but I'm not sure about that.

Anyone seen things like this before?

Error:

An internal error occurred during: "Building workspace".

Native Library C:\Users\mtyson\AppData\Local\Temp\jline_.dll already loaded in another classloader

Thanks,

Matt Tyson

Rclanahan

RE: Native Library jline_.dll already loaded in another classloader

No, I cannot even run the app. I get this error when simply doing a clean and build in eclipse (sts). Appreciate your suggested solution but for me this is not it.

I simply took an existing grails 1.3.5 project and upgraded it to 2.04 (I tried 2.1 but then thought I’d just attempt iteratively… it did the same in both cases). I even uninstalled and installed all my plugins more than once. … and also did this from the command line, outside of eclipse.

For test purposes I created a new grails project in the same workspace and created a simple domain class and performed a “generate-all”. It validates and runs okay. I have scoured the web trying to figure this out and have been unsuccessful. I am using sts 2.9.2… just upgraded this also. Not sure what is going on. I am stumped.

From: Matthew Tyson [mailto:[hidden email]]
Sent: Friday, July 20, 2012 10:43 PM
To: [hidden email]
Subject: Re: [grails-user] Native Library jline_.dll already loaded in another classloader

Randy,

Here's what I found.

Open the task manager. You'll see the run-app java process is still alive. Kill it (its the less memory intensive process vs. eclipse). Attempt to run-app now - it should work.

Hopefully, that helps your situation also.

Matt Tyson

On Fri, Jul 20, 2012 at 2:09 PM, Randy Clanahan <[hidden email]> wrote:

Errors occurred during the build.

Errors running builder 'Java Builder' on project 'xxxgrails'.

Native Library C:\Users\RClanahan\AppData\Local\Temp\jline_.dll already loaded in another classloader

Anyone seen things like this before?

Error:

An internal error occurred during: "Building workspace".

Native Library C:\Users\mtyson\AppData\Local\Temp\jline_.dll already loaded in another classloader

Thanks,

Matt Tyson

Graeme Rocher-2

Re: Native Library jline_.dll already loaded in another classloader

This would happen if you had 2 versions of jline on your classpath, check your dependencies and ensure this is not the case

Graeme Rocher

On Tuesday, July 24, 2012 at 4:52 PM, Randy Clanahan wrote:

No, I cannot even run the app. I get this error when simply doing a clean and build in eclipse (sts). Appreciate your suggested solution but for me this is not it.

I simply took an existing grails 1.3.5 project and upgraded it to 2.04 (I tried 2.1 but then thought I’d just attempt iteratively… it did the same in both cases). I even uninstalled and installed all my plugins more than once. … and also did this from the command line, outside of eclipse.

For test purposes I created a new grails project in the same workspace and created a simple domain class and performed a “generate-all”. It validates and runs okay. I have scoured the web trying to figure this out and have been unsuccessful. I am using sts 2.9.2… just upgraded this also. Not sure what is going on. I am stumped.

From: Matthew Tyson [[hidden email]]
Sent: Friday, July 20, 2012 10:43 PM
To: [hidden email]
Subject: Re: [grails-user] Native Library jline_.dll already loaded in another classloader

Randy,

Here's what I found.

You are running run-app in spring eclipse (either debug or just straight). You run 'grails clean' in spring eclipse. Now, the console no longer shows the app is running, you assume that the run-app process is gone. You attempt to run-app (either debug or straight), again. You get the .dll error.

Open the task manager. You'll see the run-app java process is still alive. Kill it (its the less memory intensive process vs. eclipse). Attempt to run-app now - it should work.

Hopefully, that helps your situation also.

Matt Tyson

On Fri, Jul 20, 2012 at 2:09 PM, Randy Clanahan <[hidden email]> wrote:

Yes…. I’m getting this too. Just attempted to upgrade a grails 1.3.5 project to grails 2.1… and also upgraded my sts edi to 2.9.2 from 2.8.1. I’m getting this same error and cannot find any useful information on how to correct it. It is difficult for me to believe that grail 2.1 is the direct cause. I am running windows 7… and here is the error message I get. I get it when I do practically anything, but this message is when I do a project clean and rebuild.

Errors occurred during the build.

Errors running builder 'Java Builder' on project 'xxxgrails'.

Native Library C:\Users\RClanahan\AppData\Local\Temp\jline_.dll already loaded in another classloader

From: Matthew Tyson [mailto:[hidden email]]
Sent: Saturday, July 07, 2012 8:03 PM
To: [hidden email]
Subject: [grails-user] Native Library jline_.dll already loaded in another classloader

I am seeing the following error when trying to run various grails tasks (like generate-controller) from the String STS ide. It seems like this start after I installed EGit, but I'm not sure about that.

Anyone seen things like this before?

Error:

An internal error occurred during: "Building workspace".

Native Library C:\Users\mtyson\AppData\Local\Temp\jline_.dll already loaded in another classloader

Thanks,

Matt Tyson

Rclanahan

RE: Native Library jline_.dll already loaded in another classloader

Sorry… I’m feeling a bit dense… but when you generally say “…check your dependencies…”, I’m not quite sure exactly what to do to “check” my dependencies.

From: Graeme Rocher [mailto:[hidden email]]
Sent: Wednesday, July 25, 2012 1:30 AM
To: [hidden email]
Subject: Re: [grails-user] Native Library jline_.dll already loaded in another classloader

This would happen if you had 2 versions of jline on your classpath, check your dependencies and ensure this is not the case

Graeme Rocher

On Tuesday, July 24, 2012 at 4:52 PM, Randy Clanahan wrote:

No, I cannot even run the app. I get this error when simply doing a clean and build in eclipse (sts). Appreciate your suggested solution but for me this is not it.

I simply took an existing grails 1.3.5 project and upgraded it to 2.04 (I tried 2.1 but then thought I’d just attempt iteratively… it did the same in both cases). I even uninstalled and installed all my plugins more than once. … and also did this from the command line, outside of eclipse.

For test purposes I created a new grails project in the same workspace and created a simple domain class and performed a “generate-all”. It validates and runs okay. I have scoured the web trying to figure this out and have been unsuccessful. I am using sts 2.9.2… just upgraded this also. Not sure what is going on. I am stumped.

From: Matthew Tyson [[hidden email]]
Sent: Friday, July 20, 2012 10:43 PM
To: [hidden email]
Subject: Re: [grails-user] Native Library jline_.dll already loaded in another classloader

Randy,

Here's what I found.

You are running run-app in spring eclipse (either debug or just straight). You run 'grails clean' in spring eclipse. Now, the console no longer shows the app is running, you assume that the run-app process is gone. You attempt to run-app (either debug or straight), again. You get the .dll error.

Open the task manager. You'll see the run-app java process is still alive. Kill it (its the less memory intensive process vs. eclipse). Attempt to run-app now - it should work.

Hopefully, that helps your situation also.

Matt Tyson

On Fri, Jul 20, 2012 at 2:09 PM, Randy Clanahan <[hidden email]> wrote:

Yes…. I’m getting this too. Just attempted to upgrade a grails 1.3.5 project to grails 2.1… and also upgraded my sts edi to 2.9.2 from 2.8.1. I’m getting this same error and cannot find any useful information on how to correct it. It is difficult for me to believe that grail 2.1 is the direct cause. I am running windows 7… and here is the error message I get. I get it when I do practically anything, but this message is when I do a project clean and rebuild.

Errors occurred during the build.

Errors running builder 'Java Builder' on project 'xxxgrails'.

Native Library C:\Users\RClanahan\AppData\Local\Temp\jline_.dll already loaded in another classloader

From: Matthew Tyson [mailto:[hidden email]]
Sent: Saturday, July 07, 2012 8:03 PM
To: [hidden email]
Subject: [grails-user] Native Library jline_.dll already loaded in another classloader

I am seeing the following error when trying to run various grails tasks (like generate-controller) from the String STS ide. It seems like this start after I installed EGit, but I'm not sure about that.

Anyone seen things like this before?

Error:

An internal error occurred during: "Building workspace".

Native Library C:\Users\mtyson\AppData\Local\Temp\jline_.dll already loaded in another classloader

Thanks,

Matt Tyson

Graeme Rocher-4

Re: Native Library jline_.dll already loaded in another classloader

Administrator

In this case it is a STS error, so check your STS classpath in Eclipse
project settings, alternatively if you believe there is an issue with
STS raise a JIRA in the STS JIRA

Cheers

On Thu, Jul 26, 2012 at 2:48 PM, Randy Clanahan
<[hidden email]> wrote:

> Sorry… I’m feeling a bit dense… but when you generally say “…check your
> dependencies…”, I’m not quite sure exactly what to do to “check” my
> dependencies.
>
>
>
> From: Graeme Rocher [mailto:[hidden email]]
> Sent: Wednesday, July 25, 2012 1:30 AM
>
>
> To: [hidden email]
> Subject: Re: [grails-user] Native Library jline_.dll already loaded in
> another classloader
>
>
>
> This would happen if you had 2 versions of jline on your classpath, check
> your dependencies and ensure this is not the case
>
>
>
> --
>
> Graeme Rocher
>
>
>
> On Tuesday, July 24, 2012 at 4:52 PM, Randy Clanahan wrote:
>
> No, I cannot even run the app. I get this error when simply doing a clean
> and build in eclipse (sts). Appreciate your suggested solution but for me
> this is not it.
>
> I simply took an existing grails 1.3.5 project and upgraded it to 2.04 (I
> tried 2.1 but then thought I’d just attempt iteratively… it did the same in
> both cases). I even uninstalled and installed all my plugins more than
> once. … and also did this from the command line, outside of eclipse.
>
>
>
> For test purposes I created a new grails project in the same workspace and
> created a simple domain class and performed a “generate-all”. It validates
> and runs okay. I have scoured the web trying to figure this out and have
> been unsuccessful. I am using sts 2.9.2… just upgraded this also. Not sure
> what is going on. I am stumped.
>
>
>
> From: Matthew Tyson [mailto:[hidden email]]
> Sent: Friday, July 20, 2012 10:43 PM
> To: [hidden email]
> Subject: Re: [grails-user] Native Library jline_.dll already loaded in
> another classloader
>
>
>
> Randy,
>
>
>
> Here's what I found.
>
>
>
> You are running run-app in spring eclipse (either debug or just straight).
> You run 'grails clean' in spring eclipse. Now, the console no longer shows
> the app is running, you assume that the run-app process is gone. You
> attempt to run-app (either debug or straight), again. You get the .dll
> error.
>
>
>
> Open the task manager. You'll see the run-app java process is still alive.
> Kill it (its the less memory intensive process vs. eclipse). Attempt to
> run-app now - it should work.
>
>
>
> Hopefully, that helps your situation also.
>
>
>
> Matt Tyson
>
> On Fri, Jul 20, 2012 at 2:09 PM, Randy Clanahan
> <[hidden email]> wrote:
>
> Yes…. I’m getting this too. Just attempted to upgrade a grails 1.3.5
> project to grails 2.1… and also upgraded my sts edi to 2.9.2 from 2.8.1.
> I’m getting this same error and cannot find any useful information on how to
> correct it. It is difficult for me to believe that grail 2.1 is the direct
> cause. I am running windows 7… and here is the error message I get. I get
> it when I do practically anything, but this message is when I do a project
> clean and rebuild.
>
>
>
> Errors occurred during the build.
>
> Errors running builder 'Java Builder' on project 'xxxgrails'.
>
> Native Library C:\Users\RClanahan\AppData\Local\Temp\jline_.dll already
> loaded in another classloader
>
>
>
> From: Matthew Tyson [mailto:[hidden email]]
> Sent: Saturday, July 07, 2012 8:03 PM
> To: [hidden email]
> Subject: [grails-user] Native Library jline_.dll already loaded in another
> classloader
>
>
>
> I am seeing the following error when trying to run various grails tasks
> (like generate-controller) from the String STS ide. It seems like this
> start after I installed EGit, but I'm not sure about that.
>
>
>
> Anyone seen things like this before?
>
>
>
> Error:
>
>
>
> An internal error occurred during: "Building workspace".
>
> Native Library C:\Users\mtyson\AppData\Local\Temp\jline_.dll already loaded
> in another classloader
>
>
>
> Thanks,
>
>
>
> Matt Tyson
>
>
>
>

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

mtyson

Re: Native Library jline_.dll already loaded in another classloader

Also, you probably have already tried, but try 'refresh-dependencies'.

On Thu, Jul 26, 2012 at 5:04 AM, Graeme Rocher <[hidden email]> wrote:

In this case it is a STS error, so check your STS classpath in Eclipse
project settings, alternatively if you believe there is an issue with
STS raise a JIRA in the STS JIRA

Cheers

On Thu, Jul 26, 2012 at 2:48 PM, Randy Clanahan

<[hidden email]> wrote:
> Sorry… I’m feeling a bit dense… but when you generally say “…check your
> dependencies…”, I’m not quite sure exactly what to do to “check” my
> dependencies.
>
>
>
> From: Graeme Rocher [mailto:[hidden email]]
> Sent: Wednesday, July 25, 2012 1:30 AM
>
>
> To: [hidden email]
> Subject: Re: [grails-user] Native Library jline_.dll already loaded in
> another classloader
>
>
>
> This would happen if you had 2 versions of jline on your classpath, check
> your dependencies and ensure this is not the case
>
>
>
> --
>
> Graeme Rocher
>
>
>
> On Tuesday, July 24, 2012 at 4:52 PM, Randy Clanahan wrote:
>
> No, I cannot even run the app. I get this error when simply doing a clean
> and build in eclipse (sts). Appreciate your suggested solution but for me
> this is not it.
>
> I simply took an existing grails 1.3.5 project and upgraded it to 2.04 (I
> tried 2.1 but then thought I’d just attempt iteratively… it did the same in
> both cases). I even uninstalled and installed all my plugins more than
> once. … and also did this from the command line, outside of eclipse.
>
>
>
> For test purposes I created a new grails project in the same workspace and
> created a simple domain class and performed a “generate-all”. It validates
> and runs okay. I have scoured the web trying to figure this out and have
> been unsuccessful. I am using sts 2.9.2… just upgraded this also. Not sure
> what is going on. I am stumped.
>
>
>
> From: Matthew Tyson [mailto:[hidden email]]
> Sent: Friday, July 20, 2012 10:43 PM
> To: [hidden email]
> Subject: Re: [grails-user] Native Library jline_.dll already loaded in
> another classloader
>
>
>
> Randy,
>
>
>
> Here's what I found.
>
>
>
> You are running run-app in spring eclipse (either debug or just straight).
> You run 'grails clean' in spring eclipse. Now, the console no longer shows
> the app is running, you assume that the run-app process is gone. You
> attempt to run-app (either debug or straight), again. You get the .dll
> error.
>
>
>
> Open the task manager. You'll see the run-app java process is still alive.
> Kill it (its the less memory intensive process vs. eclipse). Attempt to
> run-app now - it should work.
>
>
>
> Hopefully, that helps your situation also.
>
>
>
> Matt Tyson
>
> On Fri, Jul 20, 2012 at 2:09 PM, Randy Clanahan
> <[hidden email]> wrote:
>
> Yes…. I’m getting this too. Just attempted to upgrade a grails 1.3.5
> project to grails 2.1… and also upgraded my sts edi to 2.9.2 from 2.8.1.
> I’m getting this same error and cannot find any useful information on how to
> correct it. It is difficult for me to believe that grail 2.1 is the direct
> cause. I am running windows 7… and here is the error message I get. I get
> it when I do practically anything, but this message is when I do a project
> clean and rebuild.
>
>
>
> Errors occurred during the build.
>
> Errors running builder 'Java Builder' on project 'xxxgrails'.
>
> Native Library C:\Users\RClanahan\AppData\Local\Temp\jline_.dll already
> loaded in another classloader
>
>
>
> From: Matthew Tyson [mailto:[hidden email]]
> Sent: Saturday, July 07, 2012 8:03 PM
> To: [hidden email]
> Subject: [grails-user] Native Library jline_.dll already loaded in another
> classloader
>
>
>
> I am seeing the following error when trying to run various grails tasks
> (like generate-controller) from the String STS ide. It seems like this
> start after I installed EGit, but I'm not sure about that.
>
>
>
> Anyone seen things like this before?
>
>
>
> Error:
>
>
>
> An internal error occurred during: "Building workspace".
>
> Native Library C:\Users\mtyson\AppData\Local\Temp\jline_.dll already loaded
> in another classloader
>
>
>
> Thanks,
>
>
>
> Matt Tyson
>
>
>
>

--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Rclanahan

RE: Native Library jline_.dll already loaded in another classloader

Yep… did it 100 times J

From: Matthew Tyson [mailto:[hidden email]]
Sent: Thursday, July 26, 2012 10:30 AM
To: [hidden email]
Subject: Re: [grails-user] Native Library jline_.dll already loaded in another classloader

Also, you probably have already tried, but try 'refresh-dependencies'.

On Thu, Jul 26, 2012 at 5:04 AM, Graeme Rocher <[hidden email]> wrote:

<[hidden email]> wrote:
> Sorry… I’m feeling a bit dense… but when you generally say “…check your
> dependencies…”, I’m not quite sure exactly what to do to “check” my
> dependencies.
>
>
>
> From: Graeme Rocher [mailto:[hidden email]]
> Sent: Wednesday, July 25, 2012 1:30 AM
>
>
> To: [hidden email]
> Subject: Re: [grails-user] Native Library jline_.dll already loaded in
> another classloader
>
>
>
> This would happen if you had 2 versions of jline on your classpath, check
> your dependencies and ensure this is not the case
>
>
>
> --
>
> Graeme Rocher
>
>
>
> On Tuesday, July 24, 2012 at 4:52 PM, Randy Clanahan wrote:
>
> No, I cannot even run the app. I get this error when simply doing a clean
> and build in eclipse (sts). Appreciate your suggested solution but for me
> this is not it.
>
> I simply took an existing grails 1.3.5 project and upgraded it to 2.04 (I
> tried 2.1 but then thought I’d just attempt iteratively… it did the same in
> both cases). I even uninstalled and installed all my plugins more than
> once. … and also did this from the command line, outside of eclipse.
>
>
>
> For test purposes I created a new grails project in the same workspace and
> created a simple domain class and performed a “generate-all”. It validates
> and runs okay. I have scoured the web trying to figure this out and have
> been unsuccessful. I am using sts 2.9.2… just upgraded this also. Not sure
> what is going on. I am stumped.
>
>
>
> From: Matthew Tyson [mailto:[hidden email]]
> Sent: Friday, July 20, 2012 10:43 PM
> To: [hidden email]
> Subject: Re: [grails-user] Native Library jline_.dll already loaded in
> another classloader
>
>
>
> Randy,
>
>
>
> Here's what I found.
>
>
>
> You are running run-app in spring eclipse (either debug or just straight).
> You run 'grails clean' in spring eclipse. Now, the console no longer shows
> the app is running, you assume that the run-app process is gone. You
> attempt to run-app (either debug or straight), again. You get the .dll
> error.
>
>
>
> Open the task manager. You'll see the run-app java process is still alive.
> Kill it (its the less memory intensive process vs. eclipse). Attempt to
> run-app now - it should work.
>
>
>
> Hopefully, that helps your situation also.
>
>
>
> Matt Tyson
>
> On Fri, Jul 20, 2012 at 2:09 PM, Randy Clanahan
> <[hidden email]> wrote:
>
> Yes…. I’m getting this too. Just attempted to upgrade a grails 1.3.5
> project to grails 2.1… and also upgraded my sts edi to 2.9.2 from 2.8.1.
> I’m getting this same error and cannot find any useful information on how to
> correct it. It is difficult for me to believe that grail 2.1 is the direct
> cause. I am running windows 7… and here is the error message I get. I get
> it when I do practically anything, but this message is when I do a project
> clean and rebuild.
>
>
>
> Errors occurred during the build.
>
> Errors running builder 'Java Builder' on project 'xxxgrails'.
>
> Native Library C:\Users\RClanahan\AppData\Local\Temp\jline_.dll already
> loaded in another classloader
>
>
>
> From: Matthew Tyson [mailto:[hidden email]]
> Sent: Saturday, July 07, 2012 8:03 PM
> To: [hidden email]
> Subject: [grails-user] Native Library jline_.dll already loaded in another
> classloader
>
>
>
> I am seeing the following error when trying to run various grails tasks
> (like generate-controller) from the String STS ide. It seems like this
> start after I installed EGit, but I'm not sure about that.
>
>
>
> Anyone seen things like this before?
>
>
>
> Error:
>
>
>
> An internal error occurred during: "Building workspace".
>
> Native Library C:\Users\mtyson\AppData\Local\Temp\jline_.dll already loaded
> in another classloader
>
>
>
> Thanks,
>
>
>
> Matt Tyson
>
>
>
>

Rclanahan

RE: Native Library jline_.dll already loaded in another classloader

Finally got past this problem… or at least I don’t see it in my problem log any more. I deleted (renamed) c:\users\xxxxx\.grails\ivy-cache and ran the upgrade from the command line again. It replaced this folder and no longer see the jline error described below.

Now I have no errors in my problem tab. Now when I run the app (run as -> Grails Command (run-app)) I get this. I’m going to cut-n-past the whole console output (sorry). I find snippets on the web about this but no real solution. All I am doing is trying to upgrade and existing grails 1.3.5 project to a grails 2.1 project. I keep reading the information about upgrading from 1.3.x to 2.1 but am not able to find anything that I can do so far to fix this. I appreciate the help I have gotten so far. FYI… I can upgrade to 1.3.7 easily… but I had these same issues when iteratively trying to go from 1.3.7 to 2.1…. so I don’t think it is specifically a 1.3.5 to 2.1 issue.

I am really wanting to go to 2.1… but I am about to give up. It is a rather large project. I don’t really want to create a new 2.1 project and piece-meal the code from one to the other… which may be my only option. ?????

------ here is my console output (I am running sts 2.9.2) ---------------------------

Note: Some input files use unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

| Compiling 172 source files..

| Compiling 312 source files

Note: C:\ICM\stsGrails21\vsograils\src\java\com\irondata\icmgrails\util\DateCalculator.java uses or overrides a deprecated API.

Note: Recompile with -Xlint:deprecation for details.

| Compiling 312 source files.....

| Running Grails application

Configuring Spring Security Core ...

... finished configuring Spring Security Core

| Error 2012-07-26 18:18:57,870 [pool-4-thread-1] ERROR context.GrailsContextLoader - Error executing bootstraps: Error creating bean with name 'instanceControllerTagLibraryApi': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire method: public void org.codehaus.groovy.grails.plugins.web.api.ControllerTagLibraryApi.setGspTagLibraryLookup(org.codehaus.groovy.grails.web.pages.TagLibraryLookup); nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'gspTagLibraryLookup': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.irondata.icmgrails.ICMCalendarTagLib': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'permissionService': Scope 'session' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

Message: Error creating bean with name 'instanceControllerTagLibraryApi': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire method: public void org.codehaus.groovy.grails.plugins.web.api.ControllerTagLibraryApi.setGspTagLibraryLookup(org.codehaus.groovy.grails.web.pages.TagLibraryLookup); nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'gspTagLibraryLookup': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.irondata.icmgrails.ICMCalendarTagLib': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'permissionService': Scope 'session' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

Line | Method

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

Caused by BeanCreationException: Could not autowire method: public void org.codehaus.groovy.grails.plugins.web.api.ControllerTagLibraryApi.setGspTagLibraryLookup(org.codehaus.groovy.grails.web.pages.TagLibraryLookup); nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'gspTagLibraryLookup': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.irondata.icmgrails.ICMCalendarTagLib': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'permissionService': Scope 'session' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

Caused by BeanCreationException: Error creating bean with name 'gspTagLibraryLookup': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.irondata.icmgrails.ICMCalendarTagLib': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'permissionService': Scope 'session' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

Caused by BeanCreationException: Error creating bean with name 'com.irondata.icmgrails.ICMCalendarTagLib': Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'permissionService': Scope 'session' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

Caused by BeanCreationException: Error creating bean with name 'permissionService': Scope 'session' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

Caused by IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

From: Randy Clanahan [mailto:[hidden email]]
Sent: Thursday, July 26, 2012 10:34 AM
To: [hidden email]
Subject: RE: [grails-user] Native Library jline_.dll already loaded in another classloader

Yep… did it 100 times J

From: Matthew Tyson [[hidden email]]
Sent: Thursday, July 26, 2012 10:30 AM
To: [hidden email]
Subject: Re: [grails-user] Native Library jline_.dll already loaded in another classloader

Also, you probably have already tried, but try 'refresh-dependencies'.

On Thu, Jul 26, 2012 at 5:04 AM, Graeme Rocher <[hidden email]> wrote:

Rclanahan

ERROR context.GrailsContextLoader

I have no errors in my problem tab. Now when I run the app (run as -> Grails Command (run-app)) I get this. I’m going to cut-n-past the whole console output (sorry). I find snippets on the web about this but no real solution. All I am doing is trying to upgrade and existing grails 1.3.5 project to a grails 2.1 project. I keep reading the information about upgrading from 1.3.x to 2.1 but am not able to find anything that I can do so far to fix this. I appreciate the help I have gotten so far. FYI… I can upgrade to 1.3.7 easily… but I had these same issues when iteratively trying to go from 1.3.7 to 2.1…. so I don’t think it is specifically a 1.3.5 to 2.1 issue.

------ here is my console output (I am running sts 2.9.2) ---------------------------

Note: Some input files use unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

| Compiling 172 source files..

| Compiling 312 source files

Note: C:\ICM\stsGrails21\vsograils\src\java\com\irondata\icmgrails\util\DateCalculator.java uses or overrides a deprecated API.

Note: Recompile with -Xlint:deprecation for details.

| Compiling 312 source files.....

| Running Grails application

Configuring Spring Security Core ...

... finished configuring Spring Security Core

Line | Method

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

->> 303 | innerRun in java.util.concurrent.FutureTask$Sync

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

| 138 | run in java.util.concurrent.FutureTask

| 886 | runTask in java.util.concurrent.ThreadPoolExecutor$Worker

| 908 | run in ''

^ 619 | run . . in java.lang.Thread

From: Randy Clanahan [[hidden email]]
Sent: Thursday, July 26, 2012 10:34 AM
To: [hidden email]
Subject: RE: [grails-user] Native Library jline_.dll already loaded in another classloader

Yep… did it 100 times J

Also, you probably have already tried, but try 'refresh-dependencies'.

On Thu, Jul 26, 2012 at 5:04 AM, Graeme Rocher <[hidden email]> wrote:

alexx

Re: Native Library jline_.dll already loaded in another classloader

In reply to this post by Graeme Rocher-4

I am also encountering this pesky jline_.dll issue.

I removed my entire STS installation and re-installed from scratch. (I did not delete anything under the cache folders, however.)

It's still showing up. I never saw this thing, until I upgraded to Grails 2.1.0.