RAD7 WAS 6.1.1 单个服务器/JVM 和 2 个版本不同的应用程序出现问题
我在 RAD7 (WAS 6.1.1) 中遇到一个独特的问题。我们有两个相同的应用程序，但版本不同，运行在同一台服务器上（部署了两个耳朵）。当用户同时登录两个应用程序并尝试某些操作时，旧版本和新版本的功能将组合在一起，并且其行为是随机的。这是否与使用两个应用程序版本的通用对象池的单个 JVM 有关，或者...
我很困惑..
帮助谢谢和问候， DJ
I have a unique problem in RAD7 (WAS 6.1.1). We have two same applications but different versions, running on the same server(deployed two ear's). When a user logs in both the application simultaneously and tries some action, the functionality(ies) of older version and newer versions are combined and it behaves randomly. Is it something to do with a single JVM using a common object pool for both application versions or...
I am befuddled..Help
Thanks and regards,
dj
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我不是 100% 确定为什么你在同一服务器上有相同的应用程序......但可以这样想：
两个应用程序都针对特定上下文（即：/myApp/）注册，并且它们都在服务器上处于活动状态。每当有请求到来时，哪一个应该采取行动？这是“计算机无法知道你真正想要做什么”的情况之一。由于两个应用程序实际上都在执行操作，因此这听起来像是两个应用程序之间的竞争条件。有时一个应用程序获胜，有时另一个应用程序获胜。
您确实不应该将这两个应用程序放在同一台服务器上。
I'm not 100% sure why you have the same app on the same server... but think of it this way:
Both applications register against a certain context (i.e.: /myApp/) and they're both active on the server. Which one is supposed to act whenever a request comes in? This is one of those "the computer has no way of knowing what you really want to do" situations. Since both applications are actually performing actions, it sounds like a race condition between both applications. Sometimes one app wins, sometimes the other wins.
You -really- shouldn't have both of those applications on the same server.
Deepak，
您提供的信息不够（没有提供足够的信息来帮助我们帮助您）
WAS 上每个应用程序 (EAR) 的默认行为是拥有自己的类加载器，除了一些可能是服务器的一部分的类加载器。类加载器。
该应用程序使用什么？它只是一个带有 POJO 的 Web 应用程序还是也使用 EJB？
您是否使用在服务器级别定义的任何共享库？
登录应用程序意味着什么？如果用户登录到一个应用程序并且 SSO 已打开，则用户不会被要求登录第二个应用程序（假设它是同一域 - 因为 LTPA 令牌在第一次登录时可用。
请提供附加信息） 。
Deepak,
The info you have provided is not sufficient (does not provide adequate info to help us help you)
The default behavior for each application (EAR) on WAS is to have it own classloader, except for some which could be part of the server's classloader.
What does the application use? Is it only a web app with POJOs or does it use EJBs too?
Do you use any shared libraries that are defined at the server level?
What does login to the applications mean? If the user logs in to one application and the SSO is turned on, the user will not be challenged to log into the second application (assuming it is the same domain - as the LTPA token is available from the first login.
Please provide additional info.
Manglu