out of memory Post: 302440021

9 More Discussions You Might Find Interesting

1. Programming

how to round up a memory address(memory alignment problem)

Hi, I try to marshal a unsigned int and a char * into a buffer, and then unmarshal them later to get them out. I need to put the char * in the front and unsigned int at the end of the buffer. However, my system always give me "BUS ERROR". I am using Sun Sparcs Sloris 2.10. My code to marshal...

2. HP-UX

How can I get memory usage or anything that show memory used from sar file?

Refer from title: How can i get memory used or anything that can show memory from sar file example on solaris:- we can use sar with option to show memory used at time that sar crontab run. on HP-UX, it not has option to see memory used. But i think it may be have some parameter or some...

3. AIX

ulimits max locked memory virtual memory

Hi, Would any one be so kind to explain me : are ulimits defined for each user seperately ? When ? Specialy what is the impact of : max locked memory and virtual memory on performance of applications for a user. Many thanks. PS : this is what I can see in MAN : ulimit ] ...

4. Solaris

How to find Total and Free Physical Memory and Logical Memory in SOLARIS 9

Hi, Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:- 1. Total Physical Memory in the system(total RAM). 2. Available Physical Memory(i.e. RAM Usage) 3. Total (Logical) Memory in the system 4. Available (Logical) Memory. I know...

5. Programming

How to deal with lots of data in memory in order not to run out of memory

Hi, I'm trying to learn how to manage memory when I have to deal with lots of data. Basically I'm indexing a huge file (5GB, but it can be bigger), by creating tables that holds offset <-> startOfSomeData information. Currently I'm mapping the whole file at once (yep!) but of course the...

6. Solaris

restrcit physical memory with zone.max-locked-memory

Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd

7. UNIX for Advanced & Expert Users

Out of Memory error when free memory size is large

I was running a program and it stopped and showed "Out of Memory!". at that time, the RAM used by this process is around 4G and the free memory size of the machine is around 30G. Does anybody know what maybe the reason? this program is written with Perl. the OS of the machine is Solaris U8. And I...

8. Solaris

relationship or difference between entitled memory and locked memory

Hello solaris experts, Being new to solaris containers, from Linux, feeling difficulty in understanding certain concepts. Hope somebody can help me here. I understand that, & some questions .... Locked memory -- memory which will not be swapped out at any cause. is this for...

9. Solaris

[DOUBT] Memory high in idle process on Solaris 10 (Memory Utilization > 90%)

Hi Experts, Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing. Why memory utilization on solaris always looks high? I have statement about memory on solaris, is this true: Memory in solaris is used for...

LEARN ABOUT SUNOS

asmigrate

asmigrate(1m)						    Application Server Utility						     asmigrate(1m)

NAME

       asmigrate - automates migration of J2EE applications from other J2EE platforms to Sun Java System Application Server

SYNOPSIS

       asmigrate  [-h  |  --help]  [-v	|  --version]  [(-c  |--commandline)  |  (-u  --ui) ] [-q | --quiet] [-d | --debug][-s | --sourcedirectory
       source_directory] [-S | --sourceserver source_application_server] [-t |	--targetdirectory  target_directory]  [-T  |  --targetserver  tar-
       get_application_server]	[-n  |	--scan-native-apis-only  ]  [-p  | --scan-packages package_list] [-j | --java2db create-tables=true, drop-
       tables=true, db-vendor-name=dbVendorName]  [-m  |  --migrate-cmp  comment-pk-modifiers=true,  overwrite-conflicting-accessors=true]  [-f  |
       --file-filter  all-files=true,  html-files=true,  java-files=true,  jsp-files=true, xml-files=true, archive-files=true] [-a | --append-logs
       ][operands]

       Use the asmigrate utility to analyze your J2EE application and translate vendor specific settings to Sun JavaTMTM System Application Server
       specific settings making the application deployable on Sun's J2EE products.

       The following table identifies the supported J2EE product migrations:

       +--------------------------+--------------------------------+
       |  Source J2EE Platform	  |   Destination J2EE Platform    |
       +--------------------------+--------------------------------+
       |WebSphere    Application  |Sun ONE Application Server 6.5  |
       |Server 4.0		  |				   |
       |			  |				   |
       |WebLogic     Application  |				   |
       |Server 5.1		  |				   |
       +--------------------------+--------------------------------+
       |WebLogic     Application  |Sun ONE Application Server 7    |
       |Server 5.1, 6.0, 6.1	  |				   |
       |			  |				   |
       |WebSphere    Application  |				   |
       |Server 4.0		  |				   |
       |			  |				   |
       |JavaTMTM    2	Platform  |				   |
       |Enterprise Edition 1.3	  |				   |
       |			  |				   |
       |Sun   ONE    Application  |				   |
       |Server 6.x		  |				   |
       |			  |				   |
       |Sun ONE Web Server 6.0	  |				   |
       |			  |				   |
       |JBoss Application Server  |				   |
       |3.0			  |				   |
       |			  |				   |
       |Tomcat Web Server 4.1.12  |				   |
       +--------------------------+--------------------------------+
       |WebLogic     Application  |JavaTMTM 2 Platform, Enterprise |
       |Server 5.1, 6.0, 6.1	  |Edition 1.4 Application Server  |
       |			  |				   |
       |WebSphere    Application  |				   |
       |Server 4.0		  |				   |
       |			  |				   |
       |JavaTMTM   2	Platform  |				   |
       |Enterprise	 Edition  |				   |
       |1.3/1.4 		  |				   |
       |			  |				   |
       |Sun   ONE    Application  |				   |
       |Server 6.x		  |				   |
       |			  |				   |
       |Sun ONE Web Server 6.0	  |				   |
       |			  |				   |
       |JBoss Application Server  |				   |
       |3.0			  |				   |
       |			  |				   |
       |Tomcat Web Server 4.1.12  |				   |
       +--------------------------+--------------------------------+
       |WebLogic     Application  |Sun JavaTMTM System Application |
       |Server 5.1, 6.0, 6.1	  |Server Platform Edition 8	   |
       |			  |				   |
       |WebSphere    Application  |				   |
       |Server 4.0		  |				   |
       |			  |				   |
       |JavTMTMa    2	Platform  |				   |
       |Enterprise	 Edition  |				   |
       |1.3/1.4 		  |				   |
       |			  |				   |
       |Sun    ONE   Application  |				   |
       |Server 6.x		  |				   |
       |			  |				   |
       |Sun ONE Web Server 6.0	  |				   |
       |			  |				   |
       |JBoss Application Server  |				   |
       |3.0			  |				   |
       |			  |				   |
       |JBoss Application Server  |				   |
       |3.2			  |				   |
       |			  |				   |
       |Tomcat Web Server 4.1.12  |				   |
       +--------------------------+--------------------------------+

OPTIONS

       -h --help		displays the arguments for launching the MigrationTool.

       -v --version		displays the version of the MigrationTool.

       -u --ui			invokes the tool in user interface mode.

       -c --commandline 	invokes the tool in command-line mode.

       -q --quiet		launches the tool in quiet mode.

       -d --debug		launches the tool in debug mode.

       -s --sourcedirectory	identifes the directory where the source code to migrate or scan is present.

       -S --sourceserver	identifes the source application server of the applications to be migrated. Possible servers include:

				 o  wl51: WebLogic Application Server 5.1

				 o  wl60: WebLogic Application Server 6.0

				 o  wl61: WebLogic Application Server 6.1

				 o  as65: Sun ONE Application Server 6.5

				 o  as70: Sun ONE Application Server 7.0

				 o  ws40: WebSphere Application Server 4.0

				 o  ri13: JavaTMTM 2 Platform Enterprise Edition 1.3

				 o  ri14: JavaTMTM 2 Platform Enterprise Edition 1.3

				 o  s1ws: Sun ONE Web Server

				 o  jb30: JBoss Application Server 3.0

				 o  tc41: Tomcat Application Server 4.1

       -t --targetdirectory	target or output directory where the migrated application should be placed.

       -T --targetserver	target application server to which the application is to be migrated.

       -n --scan-native-apis-onlscans the source code only for the presence of application server specific proprietary APIs.

       -p --scan-packages	comma-separated list of Java packages to scan.

       -j --java2db		bypasses  the  creation of the sun-cmp-mapping.xml file. Instead, introduces the option argument into the sun-ejb-
			       jar.xml file. Option arguments are:

				 o  create-tables: if set to true (default), creates tables at deploy. If set to false tables are not created.

				 o  drop-tables: if set to true (default), tables are dropped at undeploy. If set to false tables are not dropped.

				 o  db-vendor-name: name of the database vendor for  the  application  to  be  migrated.  Supported  vendor  names
				    include: Oracle, Sybase, DB2, Generic SQL92, PointBase, MSSQL.

       -m --migrate-cmp 	migrates 1.1 compliant CMPs, if any, to 2.0. Option arguments are:

				 o  overwrite-conflicting-accessors:  if  set  to true (default), conflicting accessors are overwritten. If set to
				    false, conflicting accessors are not overwritten.

				 o  comment-pk-modifiers: if set to true (default), setters of primary key are commented. If set to false, setters
				    of primary key are not commented.

       -f --file-filter 	selects the type of files to migrate. Option arguments are:

				 o  all-files: if specified and set to true (default), migrates all types of files.

				 o  html-files: if specified and set to true (default), migrates HTML files.

				 o  java-files: if specified and set to true (default), migrates Java files.

				 o  jsp-files: if specified and set to true (default), migrates JSP type files.

				 o  archive-files: if specified and set to true (default), migrates jar/ear/war/rar file types.

       -a --append-logs 	if  specified,	appends  the  logging to the existing or previous logs without overwriting them. If not specified,
			       previous logs are overwritten.

       operands 		identifes the archive file (jar/ear/war/rar) to be migrated.

SEE ALSO

       asupgrade(1M)

J2EE 1.4 SDK							    March 2004							     asmigrate(1m)