• Post Reply Bookmark Topic Watch Topic
  • New Topic

Deploy same EJB twice in single server instance  RSS feed

 
Travis Jenniges
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I deploy an EAR file (containing an EJB module and a Web Module) twice to the same server instance. The only difference between the two EAR files is that the EJB modules are mapped to different database schemas. In WAS v4 I had to set a property on the JVM to say class sharing = false in order to get both EJBs to load. I also had to give a unique JNDI name to all EJBs. In WAS v5 I cannot find a similar JVM setting for class sharing. Supposedly the behavior in WAS v4 was a bug that was corrected in WAS v5. However, only a single EJB is loaded in my server. SO if EAR1 is loaded first, EAR2 uses the EJBs in EAR1 and therefore goes to the wrong database schema. Any idea how I resolve this issue in WAS v5?
 
wenhua yan
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
are you able to create virtual machines (or logical servers) in WAS v5 for your environment?

That should solve you problem if that's the case.
 
Frank Proue
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have some knowledge with Travis' environment. The two applications are loaded in the same JVM. With WAS 4.x and class sharing set to disabled, each application uses their own JNDI names to access their own CMP databases even their classes have the same fully qualified names (packaged and deployed in different ear files, of course). The question is do we have the similar configuration feature in WAS 5.0 to disable the class sharing?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!