Skip to Main Content
Forums

Java Development Tools

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Switching facets from 'WebLogic EJB Extensions' to 'WebLogic EJBGen Support

tom_1st-JavaNetSep 6 2010 — edited Sep 6 2010
If i create a new EJB project called 'XYZService' two more projects are conveniently generated:

- XYZServiceClient
- XYZServiceEAR

So far so good.
Later when i want to switch to 'Oracle Weblogic EJBGen Support' (in the Projects Facets) I get the following warning:

The existing EJB Client JAR dependency on 'XYZServiceClient' must be removed before adding the WebLogic EJBGen facet. Manual editing of .settings\org.eclipse.wst.common.component may be required.

->With ejbgen my interfaces + XML descriptors are correctly generated however not into my client project (which the warning probably was about)
Is there anyway to configure eclipse/ejbgen to generate the interfaces into the client project?
Or does the other facet supports this?

Thanks & Regards,
ToM

Comments

Dude!
Answer

Yes. Each database will require its own SGA segment and additional databases will add too the total size required. POSIX or /dev/shm shared memory is similar to a RAM disk, which maps memory to virtual files to be shared among processes. By default, the maximum size of /dev/shm is 50 % of the physical or installed RAM. It does however not reserve or allocate RAM other than what is actually being used.

Keep in mind that Oracle database AMM and /dev/shm are not recommended for large memory configurations. As I recall, if your SGA is greater than 2 GB, you should use kernel hugepages instead. Kernel hugepages are more efficient due to larger memory pages, which requires far less resources for memory management and results in much better performance.

An Oracle database instance can use SYS V shared memory, which is either kernel hugepages or conventional 4k memory pages, but cannot use POSIX /dev/shm for SGA and SYS V at the same time. You can however use different shared memory concepts for different Oracle database instances on the same server. For example, running an +ASM instance using AMM and another Oracle database using kernel hugepages and ASMM.

Speaking of shared memory, the SHMMAX kernel parameter applies to SYS V shared memory only. It's a safeguard parameter to limit how much shared memory a process can possibly use and needs to be large enough to fit the largest SGA of any of your Oracle databases. SHMMAX for a server that runs Oracle database is typically set to 4 TB or whatever the platform being x86 or x64 theoretically supports. SHMMAX does not apply to POSIX /dev/shm and Oracle AMM.

For more info, see the following:

https://docs.oracle.com/cd/E11882_01/server.112/e10839/appi_vlm.htm#UNXAR385

Btw, if you have to use OS release 5, use 5.11 at least. There is no reason to run 5.6, which is obsolete.

Marked as Answer by Jhil · Sep 27 2020
1 - 1
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 4 2010
Added on Sep 6 2010
#application-development-in-java, #enterprise-pack-for-eclipse
0 comments
850 views