WebLogic 10.5.3 + Seam 2.2.1:应用程序无法启动 [英] WebLogic 10.5.3 + Seam 2.2.1: Application does not start

问题描述

我们有一个WAR打包的Web应用程序，可在开发计算机上工作.它由Java EE 5 + Seam 2.2.1 + Hibernate 3.3.1组成.它使用Oracle 10g XE数据库，并使用JDK 1.6.0_24在最新的Tomcat 6上运行.该系统是64位Windows 7 Pro，并使用Firefox 6.

we have a WAR packaged web application which works on a development machine. It consists of Java EE 5 + Seam 2.2.1 + Hibernate 3.3.1. It uses an Oracle 10g XE database and runs on the latest Tomcat 6 using JDK 1.6.0_24. The system is a 64bit Windows 7 Pro and uses Firefox 6.

现在，我们尝试将应用程序迁移到Oracle WebLogic 10.3.5.我们遵循Seam手册来指定数据源，部署JSF库和配置必要的xml文件.同时，我们验证了使用同一数据源并按规定配置xml文件的新的接缝生成的应用程序是否可以正常工作.

Now, we tried to migrate the application to Oracle WebLogic 10.3.5. We followed the Seam manual for specifying the datasource, deploying the JSF lib and configuring the necessary xml-Files. In parallel to that, we verified that a newly seam-gen generated application using the same datasource and having the xml files configured as stated works fine.

但是，如果我们在WebLogic上尝试自己的应用程序，尽管部署可以正常进行，但是当尝试在浏览器中打开Web应用程序时，这表明发生了无尽的重定向.即使在WebLogic中配置log4j，我们也看不到任何堆栈跟踪或日志错误.当使用Firebug分析请求时，我们看到get请求为"login.seam"，然后是对"error.seam"(或设置调试模式时为"debug.seam")的get请求的20倍，响应为"302 Moved Temporarily"

But if we try our own application on WebLogic, allthough the deployment works fine, when trying to open the web application in the browser, it shows that endless redirection occured. We don't see any stacktrace or log error, even when configuring log4j in WebLogic. When analyzing the request with Firebug, we see the get request to "login.seam" and then 20 times a get request for "error.seam" (or "debug.seam when setting debug mode) with the response "302 Moved Temporarily".

我整个星期都在工作，试图比较所有配置并且无法解决它-所以我希望能获得任何可能导致该问题以及如何解决的想法！

I worked on that all week now, trying to compare all configurations and couldn't solve it - so I hope to get any ideas what could cause that problem and how to solve it!

推荐答案

我可以将问题归结为在JTA持久性上下文上启动事务. 我仍然不明白为什么我没有看到任何日志消息或stacktrace，以及为什么在调试/错误页面上也会发生这种情况(这就是无休止的重定向发生的原因).

I could pin down the problem to starting a transaction on the JTA persistence context. I still don't understand why I didn't see any log message or stacktrace and why this also happens on the debug/error page (that's why the endless redirect occured).

到目前为止，我最终还是使用RESOURCE_LOCAL，但是我不确定这是否是正确的选择. 另一种方法是禁用接缝事务设置，但是随后它无法与仍在Tomcat上运行的开发版本一起使用.

I ended up using RESOURCE_LOCAL so far, but I'm not sure if this is the right thing to do. The alternative is disabling the seam transaction setting, but then it didn't work together with the development build which still runs on Tomcat.

这篇关于WebLogic 10.5.3 + Seam 2.2.1:应用程序无法启动的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！