Out of Memory Error running bea WLCS5.1

Hi everybody !
My team and I have to cope with the following bug :
Java.lang.OutOfMemoryError :
at weblogic.db.oci.OciCursor
at weblogic.jdbcbase.oci.Statement.executeQuery....
It runs under a cluster composed by 2 x BEA WLS 5.1 sp6.
heap min is 500Mo
heap max is 750Mo
total RAM is 1Go per machine
When memory use reaches 750Mo (max allowed), server should put
current instances in a queuing system while the garbage
collector is running.
At this point it appears that client requests are not queued but
canceled, returning an error to the client.
Why do we have to specify a heap limit if JVM goes over it anyway ?
Please give us a rope about it.

Moi non plus.
Cameron Purdy <[email protected]> wrote:
Je ne sais pas. Je ne parle pas francais.
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
Tangosol Server: Enabling enterprise application customization
"Dimitri Rakitine" <[email protected]> wrote in message
news:[email protected]..
Pourquoi est-ce dommage?
Cameron Purdy <[email protected]> wrote:
C'est dommage.
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
Tangosol Server: Enabling enterprise application customization
"Mike Reiche" <[email protected]> wrote in message
news:3b0a99c5$[email protected]..
Salut Laurent -
Faut que tu ecrit 'Mb' au lieu de 'Mo' puisse que les americains tecomprendre
The JVM does not exceed what you specify for max heap - the Java heap
is
only
part of the memory that the JVM uses.
Out-of-Memory exception occurs when the garbage collection cannot
recover
sufficient
memory for your application. A heap of 750Mb is very large - you may
wish
to verify
with JProbe that your application is not hanging on to memory that itdoesn't
need. Also the JVM arguments -verbose:gc will give you some additionalinformation
on GC. Specifying it twice will give you more information.
Mike
"bea" <[email protected]> wrote:
Hi everybody !
My team and I have to cope with the following bug :
Java.lang.OutOfMemoryError :
at weblogic.db.oci.OciCursor
at weblogic.jdbcbase.oci.Statement.executeQuery....
It runs under a cluster composed by 2 x BEA WLS 5.1 sp6.
heap min is 500Mo
heap max is 750Mo
total RAM is 1Go per machine
When memory use reaches 750Mo (max allowed), server should put
current instances in a queuing system while the garbage
collector is running.
At this point it appears that client requests are not queued but
canceled, returning an error to the client.
Why do we have to specify a heap limit if JVM goes over it anyway ?
Please give us a rope about it.
Dimitri
Dimitri

Similar Messages

Out of Memory Error in Java Agents running in lotus notes

I have a java agent running inside lotus notes jvm. It runs fine for some days but after some days start giving out of memory error and terminates.
I need to restart agent manager in notes to enable java agent running. Is there a way to catch out of memory error so that on its catch i could restart agent manager.
Regards,
Saitu

Dear Peter,
The agent is written in java and
I need to know a way to enter catch block of 'OUTOFMEMORYERROR'.
My whole code is in a try block with two catches, one for outofmemoryerror and another for exception. When outofmemory error occurs control passes to the exception catch and not outofmemoryerror catch.
Since out of memory is an error and not an exception, is there a way to catch it or run some code when out of memory occurs.
Regards,
Saitu

Why do I get a Track out of memory error while running open loop frequency response?

MatrixX Build 61mx1411: I get a "Track out of memory" error when I run the Open Loop Frequency Response from the MatrixX pull down tools. What can I do to prevent this? We are running on an HP B1000 with 768 MB of RAM under HP-UX 10.2.

In the old days of Mx say Version 5 and prior the user actually selected the amount of memory that would be allocated. Depending on the size of the model etc. you would have to allocate memory. In version 6.0 and going forward there is no need for the user to manually allocate the memory.
Build {rstack=50000,istack=200000,sstack=50000,cstack=500 000}
If this is a command in a script file that you are running and the error is resulting from that then I would try commenting out everything after the letter d in the word build and then starting it back up.
i.e. only use Build
I don't believe that there is a way to manually allocate the initial SystemBuild Stack size.
I believe initially the stack size is set to 10010.
However, one way
you can manually set the initial SystemBuild stack size,is to create a large StateSpace as soon as you start up SystemBuild. This will prevent piece-meal reallocs while using SystemBuild.
You can created a new SuperBlock in SystemBuild and then drop down a StateSpace Block with 199 inputs and 199 Outputs and 1 State and entered ones(200,200)as the StateSpace Matrix without any problems. This would resize this internal stack to at least 40000.
You really should not have to do this but if that helps then you might think about doing this in your startup.ms file you could use SBA or load the file then you could delete the superblock and begin working.
"Bob" gave me this little tid bit.
Please let me know if any of this is of use.
Garrett
Garrett Thurston
[email protected]
Phone: 781.993.5540

CS6 Running out of memory Error while rendering

Hey everyone,
I recently upgraded to After Effects CS6 thinking it would be a great investment. So far, I have been horribly wrong!
Here's my computer's specs: (this is a huge upgrade from the computer I was running 5.5 on without any problems other than it being slow)
Intel i7-3615QM 2.3GHz Ivy Bridge processor
8GB GDDR5 RAM
NVIDIA GeForcs 650M w/ 2GB GDDR5 dedicated RAM
Here's what's happening:
I've been doing recording for my job at 1080p in front of a green screen. I record 16 minute sections. I use Keylight to replace the background with a still picture, and then export the video at half resolution, with audio as H.264 (.mp4) files. Normally I would set up the 16 minute sections to render in queue, but it kept having the "out of memory" error shortly after starting the one second in line. So then I started just doing one at a time... and now it won't even make it through one!
I have noticed that even after rendering is done, AE is still using 6 gigs of RAM! Usually I can purge the ram, but now even doing that doesn't change anything - I have to close the program to get my RAM back. I have tried enlarging my page file, I've tried rendering in different resolutions and file types - I feel like I've tried everthing. I've looked all over the internet and I haven't found any real solutions (just talk from 2008 about "secret" menus that I can't get to work).
Please help!!
Thank you!!
Dominic

I wouldn't mind getting more RAM except that the computer I used to do this very same work with (except with 5.5) only had 6GHz of RAM and a pathetic processor and GPU in comparison.
I've tried doing the same editing in PrP but it just doesn't have enough tools . Changing my output format hasn't helped either unfortunately. I think the program has a memory leak.
I really think I might just go back to 5.5. I called support today and it took forever just to get the poor girl helping me to understand my name has an "m" in it. She wasn't really able to understand the problem. As far as I can tell, CS6 has been a 100% downgrade.
Thank you both for the help!
Dominic

Weblogic generating out of memory error when commandline run doesn't

Hello,
I am just beginning to use weblogic. I have a jar file which runs fine if run from command line with the options
"C:\Program Files (x86)\Java\jre6\bin\java" -jar -Xms1024m -Xmx1024m Report.jarIt connects to oracle and selects some data around (500k records) and writes it to a csv.
When I run the same jar from within a web application (I mean obvoiusly a servlet calling the jar's main method) the webapp generates
out of memory error after 80k records itself.
I tried changing the configuration the server Startup arguments from the console (Server Start and then Arguments) and then restart.
I just wrote the same thing there -Xms1024m -Xmx1024m
I guess I am missing something. Please share your answers.
Environment :
Win2k8, weblogic 10gR3, jdk 1.5. The application is installed as a service.
Thanks,
Neetesh
Edited by: user13312817 on 5 Dec, 2011 12:15 AM

If you are not using NodeManager, then I don't think those server settings actually control anything. If you are just exploring WLS, then I suspect you are simply starting an AdminServer in a basic domain and don't have a cluster/nodemanager based environment. I could be wrong, please correct as needed!
If you are simply starting your WebLogic Server instance using the startWebLogic.sh|cnd script, you can set an environment variable on the command shell that will be picked up and used when the server starts.
set USER_MEM_ARGS=-Xmx1024 -Xms1024m
* apply appropriate *nix changes as appropriate.
Then use the startWebLogic.sh|cmd script to start the server and test your application.
It may very well be the case that your particular application consumes > 1GB heap so you may need more. Remember that you now have a server environment running over your "main" class, so there is bound to be more memory used that could be just sneaking your heap use over 1GB. For example.
-steve-

Out of Memory error while builng HTML String from a Large HashMap.

Hi,
I am building an HTML string from a large map oject that consits of about 32000 objects using the Transformer class in java. As this HTML string needs to be displayed in the JSP page, the reponse time was too high and also some times it is throwing out of memory error.
Please let me know how i can implement the concept of building the library tree(folder structure) HTML string for the first set of say 1000 entries and then display in the web page and then detect an onScroll event and handle it in java Script functions and come back and build the tree for the next set of entries in the map and append this string to the previous one and accordingly display it.
please let me know whether
1. the suggested solution was the advisable one.
2. how to build tree(HTML String) for a set of entries in the map while iterating over the map.
3. How to detect a onScroll event and handle it.
Note : Handling the events in the JavaScript functions and displaying the tree is now being done using AJAX.
Thanks for help in Advance,
Kartheek

Hi
Sorry,
I haven't seen any error in the browser as this may be Out of memory error which was not handled. I got the the following error from the web logic console
org.apache.struts.actions.DispatchAction">Dispatch[serviceCenterHome] to method 'getUserLibraryTree' returned an exceptionjava.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:276)
     at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:196)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:226)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6452)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.OutOfMemoryError
</L_MSG>
<L_MSG MN="ILHD-1109" PID="adminserver" TID="ExecuteThread: '14' for queue: 'weblogic.kernel.Default'" DT="2012/04/18 7:56:17:146" PT="WARN" AP="" DN="" SN="" SR="org.apache.struts.action.RequestProcessor">Unhandled Exception thrown: class javax.servlet.ServletException</L_MSG>
<Apr 18, 2012 7:56:17 AM CDT> <Error> <HTTP> <BEA-101017> <[ServletContext(id=26367546,name=fcsi,context-path=/fcsi)] Root cause of ServletException.
*java.lang.OutOfMemoryError*
Please Advise.
Thanks for your help in advance,
Kartheek

Oracle Service Bus For loop getting out of memory error

I have a business service that is based on a JCA adapter to fetch an undertimed amout of records from a database. I then need to upload those to another system using a webservice designed by an external source. This web service will only accept upto to x amount of records.
The process:
for each object in the Jca Response
      Insert object into Service callout Request body
      if object index = number of objects in jca response or object index = next batch index
           Invoke service callout
           Append service callout Response to a total response object (xquery transform)
           increase next batch index by Batch size
           reset service callout to empty body
       endif
end for
replace body with total response object.
If I use the data set that only has 5 records and use a batch size of 2 the process works fine.
If I use a data set with 89 records and a batch size of 2 I get the below out of memory error after about 10 service callouts
the quantity of data in the objects is pretty small, less than 1kB for each JCA Object
Server Name:
AdminServer
Log Name:
ServerLog
Message:
Failed to process response message for service ProxyService Sa/Proxy Services/DataSync:
java.lang.OutOfMemoryError: allocLargeObjectOrArray:
[C, size 67108880 java.lang.OutOfMemoryError: allocLargeObjectOrArray:
[C, size 67108880 at org.apache.xmlbeans.impl.store.Saver$TextSaver.resize(Saver.java:1700)
at org.apache.xmlbeans.impl.store.Saver$TextSaver.preEmit(Saver.java:1303) at
org.apache.xmlbeans.impl.store.Saver$TextSaver.emit(Saver.java:1234)
at org.apache.xmlbeans.impl.store.Saver$TextSaver.emitXmlns(Saver.java:1003)
at org.apache.xmlbeans.impl.store.Saver$TextSaver.emitNamespacesHelper(Saver.java:1021)
at org.apache.xmlbeans.impl.store.Saver$TextSaver.emitElement(Saver.java:972)
at org.apache.xmlbeans.impl.store.Saver.processElement(Saver.java:476)
at org.apache.xmlbeans.impl.store.Saver.process(Saver.java:307)
at org.apache.xmlbeans.impl.store.Saver$TextSaver.saveToString(Saver.java:1864)
at org.apache.xmlbeans.impl.store.Cursor._xmlText(Cursor.java:546)
at org.apache.xmlbeans.impl.store.Cursor.xmlText(Cursor.java:2436)
at org.apache.xmlbeans.impl.values.XmlObjectBase.xmlText(XmlObjectBase.java:1500)
at com.bea.wli.sb.test.service.ServiceTracer.getXmlData(ServiceTracer.java:968)
at com.bea.wli.sb.test.service.ServiceTracer.addDataType(ServiceTracer.java:944)
at com.bea.wli.sb.test.service.ServiceTracer.addDataType(ServiceTracer.java:924)
at com.bea.wli.sb.test.service.ServiceTracer.addContextChanges(ServiceTracer.java:814)
at com.bea.wli.sb.test.service.ServiceTracer.traceExit(ServiceTracer.java:398)
at com.bea.wli.sb.pipeline.debug.DebuggerTracingStep.traceExit(DebuggerTracingStep.java:156)
at com.bea.wli.sb.pipeline.PipelineContextImpl.exitComponent(PipelineContextImpl.java:1292)
at com.bea.wli.sb.pipeline.MessageProcessor.finishProcessing(MessageProcessor.java:371)
at com.bea.wli.sb.pipeline.RouterCallback.onReceiveResponse(RouterCallback.java:108)
at com.bea.wli.sb.pipeline.RouterCallback.run(RouterCallback.java:183)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Subsystem:
OSB Kernel
Message ID:
BEA-382005
It appears to be the service callout that is the problem (it calls another OSB service that logins and performs the data upload to the External service) because If I change the batch size up to 100 the loop will load all the 89 records into the callout request and execute it fine. If I have a small batch size then I run out of memory.
Is there some settings I need to change? Is there a better way in OSB (less memory intensive than service callout in a for loop)?
Thanks.

hi,
Could you please let me know if you get rid off this issue as we are also facing the same issue.
Thanks,
SV

Weblogic 6.1 deployment out of memory error - please help

I am getting an out of memory error when deploying an ear to a weblogic 6.1 server. I tried increasing heap size with the startup param. I also tried upgrading the jdk to 1.3.1_02. Here is how I am starting weblogic -
"%JAVA_HOME%\bin\java" -hotspot -XX:MaxPermSize=256m -ms64m -mx64m -classpath "%CLASSPATH%" -Dweblogic.Domain=mydomain -Dweblogic.management.discover=false -Dweblogic.Name=myserver "-Dbea.home=C:\bea" -Dweblogic.management.password=%WLS_PW% -Dweblogic.ProductionModeEnabled=%STARTMODE% "-Djava.security.policy==C:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Server
I tried 64, 128, and 256 for the MaxPermSize param and the larger I make this number, the longer the deploy takes. I also tried lowering the session timeout to 1 min from 30. Now, when I deploy to the weblogic connection, jdev writes the war, then hangs. The rest of my desktop is slow but responsive, but I let jdev go for up to 1hr when running this deploy, and it never even starts the weblogic.deploy call. I end up killing it. This ear is not very big and is a simple servlet.
Any thoughts?

repost

Jrockit out of memory error

We are getting out of memory error with jrockit1.4.2_08. We used memory debugger tools to find the leak. Apparently there do not seem to be a leak from application perspective. Here is the core dump. Please help me resolve this.
===== BEGIN DUMP =============================================================
JRockit dump produced after 0 days, 05:37:55 on Thu Jun 5 20:39:11 2008
Additional information is available in:
/opt/obs/obs_app/obs31.0/user_projects/admin/jrockit.17430.dump
No core file will be created because core dumps have been
disabled. To enable core dumping, try "ulimit -c unlimited"
before starting JRockit again.
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at http://forums.bea.com in
the forum jrockit.developer.interest.general.
Error code: 52
Error Message: Null pointer exception in native code
Signal info : si_signo=11, si_code=2
Version : BEA WebLogic JRockit(TM) 1.4.2_08 JVM R24.5.0-61 ari-49095-20050826-1856-linux-ia32
Threads / GC : Native Threads, GC strategy: parallel
: mmHeap->data = 0x40416000, mmHeap->top = 0x7ec16000
: mmStartCompaction = 0x45236000, mmEndCompaction = 0x4a056000
CPU : Intel Pentium 4 (HT)
Number CPUs : 4
Tot Phys Mem : 4021997568
OS version : Red Hat Enterprise Linux ES release 2.1 (Panama)
Linux version 2.4.9-e.72smp ([email protected]) (gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-129.7.2)) #1 SMP Tue Jul 3 22:04:51 EDT 2007
State : JVM is running
Command Line : -Djava.class.path=<my own jars list>
java.library.path=/opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/jrockit:/opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386:/opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/../lib/i386:/opt/mqm/java/lib:/opt/tib/rv7.1.2/lib:/opt/obs/obs_app/obs31.0/thirdparty:/opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686:/opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686/oci920_8
C Heap : Good; no memory allocations have failed
Registers (from context struct at 0x8d5b724/0x8d5b80c):
EAX = 000005f4 EBX = 0000007f
ECX = 7ff8bd90 EDX = 24a18f94
ESI = 7ff46af0 EDI = 00000100
ESP = 7f262bc0 EIP = 4026d58f
EBP = 7f262bd8 EFL = 00010203
CS = 0023 DS = 002b ES = 002b
SS = 002b FS = 00df GS = 00df
Stack:
7f262bc0 :00000000 7ff46af0 00000f94 00000000 00028000 00000000
7f262bd8 :7f262c08 401ffcae 7ff8bd90 24a18f94 00028000 a0000000
7f262bf0 :0a5f1800 7f262c74 08d137a0 00000050 00000000 7f262c34
7f262c08 :7f262c48 4028a7fb 24a18f94 00000000 08d137a0 08d139e4
7f262c20 :581a664c 00000003 08d137a0 00000001 7f262c74 00000000
7f262c38 :7f262ca8 402c28bd 7f262c74 20040144 7f262ca8 402c292f
7f262c50 :7f262c74 00000000 00000000 7f262c84 581a6640 08d137a0
7f262c68 :08d1382c 414d2db8 210d41e8 0a5f1800 08d137a0 7f262d9c
7f262c80 :24a18f95 00000002 00000000 7f262cf8 08d1382c 581a6640
7f262c98 :00000000 00000000 00000000 00000000 7f262ce8 402e0861
7f262cb0 :08d137a0 581a6640 00000020 7f262cf8 210cc499 00000001
7f262cc8 :00000000 7f262ce4 08d139e8 7f262cf0 581a66c0 53b8d780
7f262ce0 :00000000 00000020 08d137a0 210cc43e 08d1382c 08d139e4
7f262cf8 :08116840 08d139e4 00000000 581a6400 210b41ff 00000001
7f262d10 :581a6618 581a6560 210cc499 581a6565 581a6618 581a6560
7f262d28 :210d2744 581a62f0 581a6560 210d2725 2112a995 2112a985
7f262d40 :2112a975 23a67584 581a6578 00000001 00000001 220e35a9
7f262d58 :23a53381 581a62f0 00000000 00000000 581a6548 00000046
7f262d70 :00000000 00000002 00000000 581a62f0 00000001 00000000
7f262d88 :00000000 00000000 581a6530 581a62f0 23a56e15 24a18f95
7f262da0 :24a18ba3 00000000 581a6130 210bead9 581a6038 581a6038
7f262db8 :581a6038 53b88f50 40fa9ca8 581a6308 55b54b00 40fa9c38
7f262dd0 :80000000 55a06030 581a6020 581a6038 581a6020 24a189bb
7f262de8 :40fa9c38 581a6020 40fa9ca8 581a60c0 55a06030 53942ff8
7f262e00 :55b54b00 40fa9ca8 40fa9c38 08d137a0 7f262e24 210b34d8
7f262e18 :40fa9c38 40fa9c68 40fa9ca8 24a18800 402e3a4d 7f262fb3
7f262e30 :0000002c 00000003 7f262ec4 08d1382c 24b196e0 249c4f84
7f262e48 :581a5390 00000000 00000058 7f262e84 402b861a 249c4f84
7f262e60 :7f262e80 08d1382c 00000001 00000001 00000008 00000013
7f262e78 :00000005 581a5fd8 08d139dc 7f262e18 00000003 00000005
7f262e90 :00000005 00000000 00000000 55a06030 55b54b00 7f262e24
7f262ea8 :7f262e24 08d137a0 7f262ee0 24a18800 210b34a0 0000002c
7f262ec0 :7f262fb3 7f262f04 402c8931 08d1382c 1aea85c0 24b196e0
7f262ed8 :00000000 7f262f5c 402c8b74 7f262f54 401aaab0 00000000
7f262ef0 :7f262f5c 7f262f54 401aaab0 401aa6a0 1aea85c0 7f262f64
7f262f08 :402c8c41 08d1382c 249c4f84 00000000 7f262f5c 402c8b74
7f262f20 :00000000 7f262f54 08d13dd0 08d1382c 7f262f9c 00000000
7f262f38 :00000000 7f262f7c 402f2b2d 08d137a0 00000001 7f262f7c
7f262f50 :402f2b24 08d13dd0 402f2b24 7f262fd4 08d1382c 7f262f94
7f262f68 :402dbd4c 08d1382c 08d139dc 249c4f84 7f262fd4 08d139e4
7f262f80 :581a5ee0 00000000 476bd4c0 210b67f6 00000000 08d137a0
7f262f98 :210e7b1b 08d1382c 08d139e0 249c4f84 08d139dc 7f262fd4
7f262fb0 :083e6898 08d139dc 00000000 210eb30d 40fa9ca8 210eb184
7f262fc8 :405bff10 00000005 210e7c48 581a5fb8 581a5fb8 581a5fe0
7f262fe0 :00000000 00000000 581a5690 210e7253 581a5fb8 00000009
7f262ff8 :73a44aa8 73a44aa8 00000005 581a5fb8 00000009 581a5690
7f263010 :246e7cd0 581a5fb8 581a53e8 581a5f48 40fa9b90 40fa9be8
7f263028 :55a06030 55b54b00 40fa9be8 40fa9bd0 246e7b13 55b54b00
7f263040 :55a06030 40fa9b60 55b54b00 55a06030 581a5378 246e79b6
7f263058 :55a06030 55b54b00 57712968 405c6858 40fa9b40 00000001
7f263070 :40fa9b40 2426bab4 55a06030 57712968 57712928 57712968
7f263088 :55b54b00 55b54b00 4b345448 2426ba1b 2426b717 53b88f50
7f2630a0 :405c6858 5393c038 53b88f50 00000002 53b88f40 24266f1f
7f2630b8 :53b88f50 53b88f50 53b88f40 5393c038 53b849c0 00000000
7f2630d0 :53912b90 5393acd0 5393c038 53912b90 242613c8 5393c038
7f2630e8 :00000000 5393acd0 00000000 5393aa60 5393c038 24658a31
7f263100 :5393acd0 4a0dbf40 00000000 4a0dbf40 539125c0 23a74a88
7f263118 :539126e8 00000001 6553be00 539125c0 246587dc 53ebb610
7f263130 :4a0dbf40 00000000 4a124210 00000000 00000000 5393aa60
7f263148 :218aff64 09ccec00 221aa582 5393a440 4a1507e8 4a1507e8
7f263160 :536f07d8 533cdee0 5393a440 533cdee0 000378b6 536f07d8
7f263178 :5393a430 00000004 210b48f0 00000050 0000000f 211080dd
7f263190 :40576ec8 21108145 5393a480 5393aa60 5393aa60 21108074
7f2631a8 :00000003 536f07d8 4a124210 7d1c9048 5393a430 654d5040
7f2631c0 :4a090428 232a5328 7d1c9048 4a124210 229f2aeb 7d1c9048
7f2631d8 :4a124210 4a127090 538f80a8 654d5040 536f07d8 4a127090
7f2631f0 :536f07d8 242438f0 536f07d8 7d1c9048 7d1c9048 538f80a8
7f263208 :5393a418 7d1c9048 229f2a12 536f07d8 7d1c9048 22147208
7f263220 :40528fa8 4056b138 00000000 00000000 405d4858 7d1c9048
7f263238 :2214718a 5393a418 7d1c9048 229f239d 5393a418 536f07d8
7f263250 :7d1c9048 4056b138 41356f20 00000000 536f07d8 40528fa8
7f263268 :4a127090 7d1c9048 5393a418 538f80a8 42562b68 538f81e0
7f263280 :229f2230 219161d1 41356f20 218e2089 42562b6d 41356f20
7f263298 :7f2632b4 210b8c73 402e37ef 7f2633e8 08d137a0 7f2632b4
7f2632b0 :210b3478 210b8c60 402e3a4d ffffffff 00000010 00000000
7f2632c8 :7f263354 08d1382c 200920e0 200282cc 00000000 00000000
7f2632e0 :00000000 7f263314 402b861a 200282cc 7f263310 08d1382c
7f2632f8 :00000001 00000001 00000006 00000006 00000001 08d137a0
7f263310 :00000000 7f2632b4 00000000 00000001 00000001 00000000
7f263328 :00000000 00000000 42562b68 7f2632b4 7f2632b4 08d137a0
7f263340 :00000000 210b8c60 210b3440 00000010 ffffffff 7f263394
7f263358 :402c8931 08d1382c 080d97e0 200920e0 00000000 7f2633e8
7f263370 :402e3550 7f2633cc 00000000 08d1382c 08d1382c 7f263aac
7f263388 :00000000 00000000 080d97e0 7f2633d4 402c9e9f 08d1382c
7f2633a0 :200282cc 00000000 7f2633e8 402e3550 00000001 7f2633cc
7f2633b8 :00000000 00000000 00000000 00000000 00000000 00000000
Code:
4026d48f :83403d9a 008bf4c4 166be850 c4830009 f4c48310 a817e853
4026d4a7 :b70f0009 c0010643 06438966 0ff8c483 048dc0b7 02e0c140
4026d4bf :08438b50 57b7e850 43890003 20c48308 53f4c483 09a87ce8
4026d4d7 :9a38a100 8b64403d 30050300 83403d9a c48310c4 50008bf4
4026d4ef :0915f4e8 084b8b00 4574c985 0f0c558b 8d0443b7 14894004
4026d507 :10558b81 0443b70f c140048d 430302e0 04508908 0f14558b
4026d51f :8d0443b7 e0c14004 08430302 66085089 b80443ff 00000001
4026d537 :b48d09eb 00000026 8bc03100 ec89e85d 768dc35d e5895500
4026d54f :570cec83 458b5356 08558b08 00fc45c7 83000000 b70ff4c4
4026d567 :478d0478 8df8d101 e852ff58 0009a7ed 8310c483 4974fffb
4026d57f :084d8b90 8b5b148d 048d0841 0c558b90 77045039 0850391c
4026d597 :188b0f72 51f4c483 09a7fce8 ebd88900 fc5d892e 768d05eb
4026d5af :8bdf8900 de89fc4d 8939148d 1fe8c1d0 d1101c8d 75f339fb
4026d5c7 :08458bb8 50f4c483 09a7cce8 8dc03100 5e5be865 5dec895f
4026d5df :e58955c3 571cec83 458b5356 fc45c70c 00000000 04788366
4026d5f7 :c7627400 0000f845 558b0000 f8458b0c 8b084203 8b118b08
4026d60f :388b0442 8b08428b 8b028b30 f8c48300 8b04598b 08418b10
4026d627 :5040d829 145d2b52 52575653 10458b53 2c406850 558b4036
4026d63f :bae85208 8bc7ddb3 c4830c55 f8458330 fc45ff0c 0442b70f
4026d657 :7cfc4539 d8658da5 895f5e5b 89c35dec e58955f6 572cec83
4026d66f :38a15356 64403d9a 0503008b 403d9a30 8bf4c483 5ee85000
4026d687 :83000914 c48310c4 e45d8df4 19bbe853 b2e80009 e8000918
Loaded modules:
(* denotes the module causing the exception)
0x08048000-0x0804ce46 /opt/obs/wls/jrockit-j2sdk1.4.2_08/bin/java
0x4001d000-0x40029fab /lib/i686/libpthread.so.0
0x4004e000-0x4006fb42 /lib/i686/libm.so.6
0x40071000-0x4007300c /lib/libdl.so.2
0x40075000-0x401a76e5 /lib/i686/libc.so.6
0x401b2000-0x40388eef* /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/jrockit/libjvm.so
0x7ec57000-0x7ec66fa5 /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/libverify.so
0x7ec75000-0x7ec94a0f /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/libjava.so
0x7ec9c000-0x7ecae3ba /lib/libnsl.so.1
0x7ec97000-0x7ec98705 /opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686/libweblogicunix1.so
0x7f5f2000-0x7f5f3eff /opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686/libmuxer.so
0x7f5f6000-0x7f5f95c1 /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/libioser12.so
0x80318000-0x8031f8bf /opt/obs/obs_app/obs31.0/thirdparty/libXMLC.so
0x80344000-0x8034c66f /opt/tib/rv7.1.2/lib/libtibrvj.so
0x8034e000-0x803563e0 /opt/tib/rv7.1.2/lib/libtibrvcmq.so
0x803d2000-0x803e66bb /opt/tib/rv7.1.2/lib/libtibrvcm.so
0x7fef9000-0x7fefdcaf /opt/tib/rv7.1.2/lib/libtibrvft.so
0x803e8000-0x804341a4 /opt/tib/rv7.1.2/lib/libtibrv.so
Thread Stack Trace:
WARNING: Memory exhausted
at java/lang/Throwable.fillInStackTrace0(Native Method)@0x210cc3f0
at java/lang/Throwable.fillInStackTrace(Unknown Source)@0x210cc499
at java/lang/Throwable.<init>(Unknown Source)@0x210d2744
at java/lang/Exception.<init>(Exception.java:41)@0x210d2725
at java/lang/RuntimeException.<init>(RuntimeException.java:43)@0x2112a995
at java/lang/IllegalArgumentException.<init>(IllegalArgumentException.java:36)@0x2112a985
at java/lang/NumberFormatException.<init>(NumberFormatException.java:38)@0x2112a975
at java/lang/NumberFormatException.forInputString(NumberFormatException.java:48)@0x23a67584
at java/lang/FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1207)@0x220e35a9
at java/lang/Double.parseDouble(Double.java:220)@0x23a56e15

I can't tell from the crash dump what the exact problem is - maybe you are running out of native memory?
You are running a very old JRockit version. Since you are a Oracle/BEA customer, you can get a newer one from BEA Support, or through edelivery.oracle.com.
-- Henrik

Out of memory error - WLW Schema Project build

hi
Wasn't sure which group (workshop vs xmlbeans) but here goes.
I'm doing a persomal eval of the WLS 8.1.1. platform.
My current focus is on XML Schema support, XML Beans, transformations etc
and in particular how it all copes with large schema.
I'm using Justice XML Data Dictionary (3.0.0.0) as an example of a large
schema
(http://it.ojp.gov/jxdd/)
I am getting an out of memory error when I build this within WLW.
The build appears to be in the javac phase (and occurs when the memory goes
over 256M) so I think it's the ANT task.
WLW doesn't seem to be running out of memory and the build machine is not
running out of resources.
Where do I configure this? The <xmlbean> tag ? Is there any doco?
regards
Jim Nicolson
=============== Build trace below ====================
Build project JXDDSchema started.
BUILD STARTED
build:
check-uptodate:
build-sub:
Updating property file:
C:\data\projects\bea\integration\wlitest\.workshop\.ide\JXDDSchema\build.pro
perties
Deleting directory
C:\DOCUME~1\JIMNIC~1\LOCALS~1\Temp\.wlw-temp\wlw_compile38940\JXDDSchema
Created dir:
C:\DOCUME~1\JIMNIC~1\LOCALS~1\Temp\.wlw-temp\wlw_compile38940\JXDDSchema
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\jxdds_3.0.0.0_full-doc.x
sd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\iso_639-2t_1.0.0.0_full-
doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ut_offender-tracking-mis
c_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-gun_1.0.0.0_fu
ll-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-other-transact
ions_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-uniform-offens
e_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\mn_offense_1.0.0.0_full-
doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\dod_jcs-pub2.0-misc_1.0.
0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\cap_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\nibrs_misc_1.0.0.0_full-
doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\fips_6-4_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\iso_3166_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\dod_misc_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-misc_1.0.0.0_f
ull-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-boat_1.0.0.0_f
ull-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-securities_1.0
.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-article_1.0.0.
0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\unece_rec20-misc_1.0.0.0
_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-state-country_
1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\iso_4217_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\fips_10-4_1.0.0.0_full-d
oc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ansi_d20_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\iso_639-2b_1.0.0.0_full-
doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\fips_5-2_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-vehicle_1.0.0.
0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\dod_exec-12958_1.0.0.0_f
ull-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-personal-descr
iptors_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\usps_states_1.0.0.0_full
-doc.xsd
Time to build schema type system: 6.75 seconds
The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError
BUILD FAILED
BUILD FAILED

hi Kevin
Thanks I'll take a look there.
I think it's a good move to make XMLBeans open source.
(I've been using Castor for the same purpose for the last two years).
I was mainly focussed on XMLBeans as they are used in WLW context and my
testing suggested that I would probably want to know more about the ANT
build/tasks etc. (Just to be able to deal with unexpected issues)
It's not urgent - I'm just doing a personal eval to come up to speed with
WLS 8.1 platform.
thanks
Jim Nicolson
"Kevin Krouse" <[email protected]> wrote in message
news:[email protected]..
Sorry, the first URL should have been:
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-xmlbeans/v1/xkit/anttask.html?rev=1.2
>
--k
On Tue, 30 Sep 2003 22:35:58 -0700, Kevin Krouse wrote:
Hi Jim,
Well, the XMLBean docs are in a process of moving into the Apache
XMLBeans
project (http://xml.apache.org/xmlbeans), so I can point you to where
they
are in the cvs repository. You can also look at the source if you'dlike!
>>
Here's an html doc for the xmlbean task:
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-xmlbeans/v1/xkit/anttask.html?rev=1.2http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-xmlbeans/v1/xkit/anttask.html?rev=1.2
>>
Here's the code for the xmlbean task:
http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v1/src/xmlcomp/org/apache/xmlbeans/impl/tool/XMLBean.java?rev=HEAD&content-type=text/vnd.viewcvs-markup
>>
>>
As to your second question about WLW becoming unresponsive, after the
Schemas.jar is built, the source for the entire project is re-scanned
which could take several minutes. The performance impact of rescanning
the project is improved in SP2 and will be addressed even more in future
releases. Stay tuned.
--k

Acrobat XI Pro "Out of Memory" Error.

We just received a new Dell T7600 workstation (Win7, 64-bit, 64GB RAM, 8TB disk storage, and more processors than you can shake a stick at). We installed the Adobe CS6 Master Collection which had Acrobat Pro X. Each time we open a PDF of size greater than roughly 4MB, the program returns an "out of memory" error. After running updates, uninstalling and reinstalling (several times), I bought a copy of Acrobat XI Pro hoping this would solve the problem. Same problem still exists upon opening the larger PDFs. Our business depends on opening very large PDF files and we've paid for the Master Collection, so I'd rather not use an freeware PDF reader. Any help, thoughts, and/or suggestions are greatly appreciated.
Regards,
Chris

As mentioned, the TEMP folder is typically the problem. MS limits the size of this folder and you have 2 choices: 1. empty it or 2. increase the size limit. I am not positive this is the issue, but it does crop up at times. It does not matter how big your harddrive is, it is a matter of the amount of space that MS has allocated for virtual memory. I am surprised that there is an issue with 64GB of RAM, but MS is real good at letting you know you can't have it all for use because you might want to open up something else. That is why a lot of big packages turn off some of the limits of Windows or use Linux.

Acrobat XI Pro "Out of Memory" error after Office 2010 install

Good Afternoon,
We recently pushed Office 2010 to our users and are now getting reports of previous installs of Adobe Acrobat XI Pro no longer working but throwing "Out of Memory" errors.
We are in a Windows XP environment. All machines are HP 8440p/6930p/6910 with the same Service pack level (3) and all up to date on security patches.
All machines are running Office 2010 SP1.
All machines have 2GB or 4GB of RAM (Only 3.25GB recognized as we are a 32bit OS environment).
All machines have adequate free space (ranging from 50gb to 200gb of free space).
All machines are set to 4096mb initial page file size with 8192mb maximum page file size.
All machines with Acrobat XI Pro *DO NOT* have Reader XI installed alongside. If Reader is installed, it is Reader 10.1 or higher.
The following troubleshooting steps have been taken:
Verify page file size (4096mb - 8192mb).
Deleted local user and Windows temp files (%temp% and c:\WINDOWS\Temp both emptied).
Repair on Adobe Acrobat XI Pro install. No change.
Uninstall Acrobat Pro XI, reboot, re-install. No change.
Uninstall Acrobat Pro XI Pro along with *ALL* other Adobe applications presently installed (Flash Player, Air), delete all Adobe folders and files found in a full search of the C drive, delete all orphaned Registry entries for all Adobe products, re-empty all temp folders, reboot.
Re-install Adobe Acrobat XI Pro. No change.
Disable enhanced security in Acrobat XI Pro. No change.
Renamed Acrobat XI's plug_ins folder to plug_ins.old.
You *can* get Acrobat to open once this is done but when you attempt to edit a file or enter data into a form, you get the message, "The "Updater" plug-in has been removed. Please re-install Acrobat to continue viewing the current file."
A repair on the Office 2010 install and re-installing Office 2010 also had no effect.
At this point, short of re-imaging the machines (which is *not* an option), we are stumped.
We have not yet tried rolling back a user to Office 2007 as the upgrade initiative is enterprise-wide and rolling back would not be considered a solution.
Anyone have any ideas beyond what has been tried so far?

As mentioned, the TEMP folder is typically the problem. MS limits the size of this folder and you have 2 choices: 1. empty it or 2. increase the size limit. I am not positive this is the issue, but it does crop up at times. It does not matter how big your harddrive is, it is a matter of the amount of space that MS has allocated for virtual memory. I am surprised that there is an issue with 64GB of RAM, but MS is real good at letting you know you can't have it all for use because you might want to open up something else. That is why a lot of big packages turn off some of the limits of Windows or use Linux.

Out of Memory Error While deploying as EAR file

Hai,
I was trying to deploy an EAR file of size 63 MB which inturn containing about 60 EJB.jars. No WARs. application.xml has all the entries for the JARs. While I am deploying it is giving Out of Memory Error. Is there any way to tweak this problem. I am using my own hand written java application which uses the SunONE deployment APIs for deployment. Can u please tell how to tackle this problem. I am running my application through a batch file which uses jdk1.4.
Please help me regarding this issue.

You can set the initial heap size and maximum heap size for the JVM, either in the app-server admin console, or maybe in one of your scripts. You look-up the syntax!...
I had this error yesterday. I too had run out of memory (150Mb). You simply need to allocate more to the app-server.

Uploading large files from applet to servlet throws out of memory error

I have a java applet that needs to upload files from a client machine
to a web server using a servlet. the problem i am having is that in
the current scheme, files larger than 17-20MB throw an out of memory
error. is there any way we can get around this problem? i will post
the client and server side code for reference.
Client Side Code:
import java.io.*;
import java.net.*;
// this class is a client that enables transfer of files from client
// to server. This client connects to a servlet running on the server
// and transmits the file.
public class fileTransferClient
private static final String FILENAME_HEADER = "fileName";
private static final String FILELASTMOD_HEADER = "fileLastMod";
// this method transfers the prescribed file to the server.
// if the destination directory is "", it transfers the file to
"d:\\".
//11-21-02 Changes : This method now has a new parameter that
references the item
//that is being transferred in the import list.
public static String transferFile(String srcFileName, String
destFileName,
String destDir, int itemID)
if (destDir.equals(""))
destDir = "E:\\FTP\\incoming\\";
// get the fully qualified filename and the mere filename.
String fqfn = srcFileName;
String fname =
fqfn.substring(fqfn.lastIndexOf(File.separator)+1);
try
//importTable importer = jbInit.getImportTable();
// create the file to be uploaded and a connection to
servlet.
File fileToUpload = new File(fqfn);
long fileSize = fileToUpload.length();
// get last mod of this file.
// The last mod is sent to the servlet as a header.
long lastMod = fileToUpload.lastModified();
String strLastMod = String.valueOf(lastMod);
URL serverURL = new URL(webadminApplet.strServletURL);
URLConnection serverCon = serverURL.openConnection();
// a bunch of connection setup related things.
serverCon.setDoInput(true);
serverCon.setDoOutput(true);
// Don't use a cached version of URL connection.
serverCon.setUseCaches (false);
serverCon.setDefaultUseCaches (false);
// set headers and their values.
serverCon.setRequestProperty("Content-Type",
"application/octet-stream");
serverCon.setRequestProperty("Content-Length",
Long.toString(fileToUpload.length()));
serverCon.setRequestProperty(FILENAME_HEADER, destDir +
destFileName);
serverCon.setRequestProperty(FILELASTMOD_HEADER, strLastMod);
if (webadminApplet.DEBUG) System.out.println("Connection with
FTP server established");
// create file stream and write stream to write file data.
FileInputStream fis = new FileInputStream(fileToUpload);
OutputStream os = serverCon.getOutputStream();
try
// transfer the file in 4K chunks.
byte[] buffer = new byte[4096];
long byteCnt = 0;
//long percent = 0;
int newPercent = 0;
int oldPercent = 0;
while (true)
int bytes = fis.read(buffer);
byteCnt += bytes;
//11-21-02 :
//If itemID is greater than -1 this is an import file
transfer
//otherwise this is a header graphic file transfer.
if (itemID > -1)
newPercent = (int) ((double) byteCnt/ (double)
fileSize * 100.0);
int diff = newPercent - oldPercent;
if (newPercent == 0 || diff >= 20)
oldPercent = newPercent;
jbInit.getImportTable().displayFileTransferStatus
(itemID,
newPercent);
if (bytes < 0) break;
os.write(buffer, 0, bytes);
os.flush();
if (webadminApplet.DEBUG) System.out.println("No of bytes
sent: " + byteCnt);
finally
// close related streams.
os.close();
fis.close();
if (webadminApplet.DEBUG) System.out.println("File
Transmission complete");
// find out what the servlet has got to say in response.
BufferedReader reader = new BufferedReader(
new
InputStreamReader(serverCon.getInputStream()));
try
String line;
while ((line = reader.readLine()) != null)
if (webadminApplet.DEBUG) System.out.println(line);
finally
// close the reader stream from servlet.
reader.close();
} // end of the big try block.
catch (Exception e)
System.out.println("Exception during file transfer:\n" + e);
e.printStackTrace();
return("FTP failed. See Java Console for Errors.");
} // end of catch block.
return("File: " + fname + " successfully transferred.");
} // end of method transferFile().
} // end of class fileTransferClient
Server side code:
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
import java.util.*;
import java.net.*;
// This servlet class acts as an FTP server to enable transfer of
files
// from client side.
public class FtpServerServlet extends HttpServlet
String ftpDir = "D:\\pub\\FTP\\";
private static final String FILENAME_HEADER = "fileName";
private static final String FILELASTMOD_HEADER = "fileLastMod";
public void doGet(HttpServletRequest req, HttpServletResponse resp)
throws ServletException,
IOException
doPost(req, resp);
public void doPost(HttpServletRequest req, HttpServletResponse
resp)
throws ServletException,
IOException
// ### for now enable overwrite by default.
boolean overwrite = true;
// get the fileName for this transmission.
String fileName = req.getHeader(FILENAME_HEADER);
// also get the last mod of this file.
String strLastMod = req.getHeader(FILELASTMOD_HEADER);
String message = "Filename: " + fileName + " saved
successfully.";
int status = HttpServletResponse.SC_OK;
System.out.println("fileName from client: " + fileName);
// if filename is not specified, complain.
if (fileName == null)
message = "Filename not specified";
status = HttpServletResponse.SC_INTERNAL_SERVER_ERROR;
else
// open the file stream for the file about to be transferred.
File uploadedFile = new File(fileName);
// check if file already exists - and overwrite if necessary.
if (uploadedFile.exists())
if (overwrite)
// delete the file.
uploadedFile.delete();
// ensure the directory is writable - and a new file may be
created.
if (!uploadedFile.createNewFile())
message = "Unable to create file on server. FTP failed.";
status = HttpServletResponse.SC_INTERNAL_SERVER_ERROR;
else
// get the necessary streams for file creation.
FileOutputStream fos = new FileOutputStream(uploadedFile);
InputStream is = req.getInputStream();
try
// create a buffer. 4K!
byte[] buffer = new byte[4096];
// read from input stream and write to file stream.
int byteCnt = 0;
while (true)
int bytes = is.read(buffer);
if (bytes < 0) break;
byteCnt += bytes;
// System.out.println(buffer);
fos.write(buffer, 0, bytes);
// flush the stream.
fos.flush();
} // end of try block.
finally
is.close();
fos.close();
// set last mod date for this file.
uploadedFile.setLastModified((new
Long(strLastMod)).longValue());
} // end of finally block.
} // end - the new file may be created on server.
} // end - we have a valid filename.
// set response headers.
resp.setContentType("text/plain");
resp.setStatus(status);
if (status != HttpServletResponse.SC_OK)
getServletContext().log("ERROR: " + message);
// get output stream.
PrintWriter out = resp.getWriter();
out.println(message);
} // end of doPost().
} // end of class FtpServerServlet

OK - the problem you describe is definitely what's giving you grief.
The workaround is to use a socket connection and send your own request headers, with the content length filled in. You may have to multi-part mime encode the stream on its way out as well (I'm not about that...).
You can use the following:
http://porsche.cis.udel.edu:8080/cis479/lectures/slides-04/slide-02.html
on your server to get a feel for the format that the request headers need to take.
- Kevin
I get the out of Memory Error on the client side. I
was told that this might be a bug in the URLConnection
class implementation that basically it wont know the
content length until all the data has been written to
the output stream, so it uses an in memory buffer to
store the data which basically causes memory issues..
do you think there might be a workaround of any kind..
or maybe a way that the buffer might be flushed after
a certain size of file has been uploaded.. ?? do you
have any ideas?

Photoshop CS6 has out of memory errors under Mac OS X 10.7.4

Has anyone who has a 2008 MacBoo Pro with the NVIDIA GeForce 8600M GT 512 MB graphics card tried running Photoshop CS6 under Mac OS X 10.7.4?
On my MacBook Pro, PS CS6 launches; however, any action results in an out of memory error. The CS6 versions of After Effects, Premiere Pro and Illustrator all launch and run as expected under 10.7.4.
If I switch to my Mac OS X 10.6.8 startup volume, Photoshop CS6 runs as expected.
I have support cases open with Adobe, NVidia and Apple. Adobe thinks I need to update the display drivers. NVidia says display drivers must be provided by Apple. Apple says that the display drivers are current. The Apple support agent said that he can escalate the case if the issue can be reproduced on more than one computer.
I'd love to keep my MacBook Pro running another year or so without having to reboot in 10.6.8 every time I need to use Photoshop. I'd stay with 10.6.8, but of course iCloud requires 10.7.4.
I have not tried 10.8 yet, but it's on my troubleshooting list.
Also, PS CS6 runs fine under Mac OS X 10.7.4 on my 2010 iMac.
Thanks in advance for any feedback.
- Warren

It looks like it was indeed the display driver for the NVIDIA GeForce 8600 GT 512 MB graphics card inside my 2008 MacBook Pro.
It seems that this driver only gets installed if you upgrade from Mac OS X 10.6.7 to 10.7.4 while the startup drive is connected to the MacBook Pro itself. I had updated while the startup drive was connected to my 2010 iMac. Accordingly, I could have reinstalled Photoshop 100 times without it ever launching as expected. Having used the external startup drive with three other Apple computers (all 2010 or newer machines) with Photoshop CS6 launching as expected, I had just assumed (mistakenly) that it would work as expected with my 2008 computer.
So, this was simple enough to resolve by upgrading the OS on the external startup drive while having it connected to the MacBook Pro. In hindsight, this makes perfect sense.
-Warren

Out of Memory Error running bea WLCS5.1

Similar Messages

Maybe you are looking for