我遇到在这个问题。主要错误消息:
错误pojo.BasicLazyInitializer - Javassist增强失败
我不知道它已经发生的频率,因为部署仍然成功。我试图解决上述问题时偶然发现了这个错误。我正在尝试部署到glassfish应用服务器(测试环境)。 基本上,我的应用程序在我的本地环境中工作正常,也使用 test run-war (请参阅我的上一个问题进一步的细节)。我打开了一个新问题,因为我觉得这可能会导致应用程序服务器上的许多问题的根源,因为增强在每次部署时都会失败。
已经有一个 JIRA ,但解决方法与webflow插件相关,该插件甚至不是用在我的项目中。我知道必须存在与javassist相关的依赖性问题,但我无法在JIRA或互联网上的其他地方找到任何有用的信息, other 插件也可能具有javassist依赖性。在我的Grails依赖项中,我只能看到一个javassist jar。
本地环境:
- Java 1.6.0_45
- Grails Tomcat插件7.0.5.3(适用于run-war) $ b
应用服务器:
- Glassfish 3.0.1 build 22
- Java 1.6.0_07
ORM策略:每个子类的表
解决方案暗示,这是Glassfish应用服务器的问题。我不知道是什么原因导致这个bug,但这绝对不是预期的行为。
我能够在本地Glassfish 3.0.1环境中重现相同的部署例外情况。幸运的是,在当地的Glassfish 3.1.2.2环境中,一切工作都很好。
Grails 1.3.7在Glassfish 3.0.1上运行良好;但是,在升级到Grails 2.4.x(第一个2.4.0,然后是2.4.1,然后是2.4.2)之后,这个异常在部署时被抛出。我不知道是否确实是导致这种情况发生的Grails更新 - 尤其是因为我在项目中做了很多其他更改,例如,到域模型,新的hibernate版本 - ,但如果遇到与grails 2.4.x和Glassfish部署类似的问题,请提供版本3.1.2。一枪。
如果我找到一些时间,我会尝试创建一个简单可重复的示例并发布JIRA问题。如果您阅读本文并感觉对此问题感兴趣,请自由创建JIRA;)。 我已经回答我的另一个问题,与部署例外直接相关。
I am encountering an error specified in the stacktrace at the bottom of this question. Main error message:
ERROR pojo.BasicLazyInitializer - Javassist Enhancement failed
I do not know how often it has occurred already, because the deployment still succeeded. I just stumbled upon this error when trying to fix the issue linked above. I am trying to deploy to a glassfish app server (test environment).
Basically, my app works fine in my local environment, also with test run-war (see my previous question for further detail). I opened a new question because i feel like this could lead to the root of many problems on the app server, since the enhancement fails on every deployment.
There is already a JIRA on that one, but the workaround relates to the webflow plugin, which is not even used in my project. I know there must be a dependency issue related to javassist, but I fail to find any useful information in the JIRA or elsewhere on the internet what other plugins might have a javassist dependency as well. In my Grails Dependencies, I can only see one javassist jar.
Local Environment:
- Java 1.6.0_45
- Grails Tomcat plugin 7.0.5.3 (for run-war)
App Server:
- Glassfish 3.0.1 build 22
- Java 1.6.0_07
ORM strategy: Table per Subclass
解决方案As my environment overview in the question already seems to imply, it was a problem with the Glassfish application server. I don't know what causes this bug, but this is definitely not expected behaviour.
I was able to reproduce the same exceptions on deployment in a local Glassfish 3.0.1 environment. Then, fortunately, in a local Glassfish 3.1.2.2 environment, everything worked fine on deployment.
Grails 1.3.7 runs well on Glassfish 3.0.1; however, after upgrading to Grails 2.4.x (first 2.4.0, then 2.4.1, then 2.4.2), this exception was thrown on deployment. I don't know if it really was the Grails update that caused this to happen -- especially since I made a lot of other changes in the project, e.g. to the domain model, new hibernate version --, but if you run into similar issues with grails 2.4.x and Glassfish deployment, give Version 3.1.2. a shot.
If I find some time, I will try to create an easy reproducible example and post a JIRA issue. Feel free to create a JIRA yourself if you read this and feel interested about this issue ;).
I have answered another question of mine that was directly related to the exceptions on deployment.
更多推荐
Javassist增强功能在部署上失败
发布评论