premesh purayil

Greenhorn
+ Follow
since Nov 23, 2004
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by premesh purayil

haha. so basically your are telling me there is no way to programtically create a database in DB2?
LOL well atleast im providing some entertainment huh? The URLS i use for the other DBS are as follows:

Oracle : jdbc:oracle:thin:@localhost:1521
SQLServer : jdbc:sqlserver://localhost

Basically i want the ability to programtically create a database and users... however that is possible
So i have a utility that i use ( written in java) to setup my databases used by my application. It works like a charm on Oracle , Derby, MySQL and SQLServer. Basically it connects to the db drobs the two databases if they exist and re creates them. Problem is that i cant connect to DB2 without specifying a DB name. Ideally I do not want to have the user go into the DB2 control panel and create a dummy db just so my utility can have the db to connect to.
what should the URL be to connect to DB2 as i discribed above?
I suppose CDATA sections are an option.. basically the application allows you to store annotations ... kinda like a comment which can be any arbritary string of any size (with db limitations). The webservice call is passed an object which is the serialized version of the object that holds the string... something like "literal(length(5)value(hello))" which then it deserializes back into an object. To parse the serialisation we break up the string into tokens by the "(" and the ")".. and i use the length field to determine how long the string was so that i can extract the value correctly ( in case the string had a ")" in it or spaces etc the length param tells me the exact expected length). In this specific case the client is sending over a very large string which they created by parsing an xml doc like isaid..turns out it contains "\r \n" at the end of every line. So when i serialize on the client side the length includes the "\r" but when i desrialize on the server side the length is incorrect and my parsing breaks down. I suppose i can tell the client that we dont support "\r" in the strings so they would have to filter them out... or wrap them in CDATA tags... just wierd that its being striped out anyways... i think i know how to get around this.. but id like to know WHY its doing it
17 years ago
so there is no way to send a string across soap that contains a carriage return and have it preserve the carriage return? Basically i want to store exactly what is passed in the form it is passed so filtering out the carriage return means when i return the string to the user when they try to retrieve it , it will not be exactly what they entered... is this because of something SOAP is doing?
17 years ago
basically my string contains "\r \n" through out it...
17 years ago
thanks for the infor. Im not processing the xml here, im just essentially reading a txt file and sending the string result accross to the webservice. The value can be any arbitrary string and in this specific case it just happens to be as a result of reading an xml file. So do you mean to say that when i read a file that is xml i most do some post/pre processing?
17 years ago
So im trying to send a string that is essentially an xml document. On the client side the string length is larger then what i get on the serverside which causes problems in my application. The client side string has newline and carriage returns but when recieved in the webservice i only see the newlines which account for the missing characters. I do not want to URL encode the string since this would be suboptimal in my situation. what other options do i have to ensure exactly what i send it received in the web service??
17 years ago
I have a old db running version 7.2.2 on linux and am in the process of updating the install to a windows xp box. I want to use the latest db version ( 8.1.3) and am having difficulty figuring out how to copy my data from the old one to the other. I tried the pg_dump tool which i used in the past to copy data from one 7.2.2 installation to another 7.2.2 installtion on linux and it worked just fine but when i try it now using the pg_restore utility it gives me errors saying the format is wrong. Can anyone provide me with the proper instructions to accompilsh this?
17 years ago
The app is fairly thin. We implemented an API that basically wraps the web service which then makes db calls ( obviously there its a little more complex than that underneath) . There isnt an in memory state or any persisting being done in the web service. Im goning to try the suggestion of running the tests (using Junit in JBuilder) right until a couple before where i know it fails and then wait for 30 mins or so to see if the session count goes down so i can try to continue. It is odd that it seems like a sessions is created for every call against the API. It should be acting like one user with one session making calls agains the API ... The sessions have some information in it but its minimal.. whats the max number of sessions Tomcat can maintain on the default heap size?
will post more after the tests
18 years ago
hmmm when i use the Tomcan manager for the server status i see this while running my unit tests against the service. Shouldnt i not have this many active sessions if my unit tests are ment be consecutive tests...

Startup time: 10 ms TLD scan time: 0 ms
Active sessions: 202 Session count: 202 Max active sessions: 202 Rejected session creations: 0 Expired sessions: 0 Processing time: 0 ms
JSPs loaded: 0 JSPs reloaded: 0
default [ / ]
18 years ago
My app seems to have memory leak i would assume. Its basically an abstraction ontop of a database but when i run unit tests on a client application which calls out to this service it eventually yacks. If i run the unit test classes individually its fine (although after a number of them i run into the same problem) but if i run the whole suite (350 tests) its bombs out on the same test every time... ( that test basically causes one write and a read from the underlying DB). Whats the best way to tack where my problem specifically? takes 45 mins of unit tests to replicate this and setting breakpoints searching for the problem has been VERY difficult... suggestions?
here is the stack trace..
0060111|094336062|14|SEVERE|caught throwable
20060111|094337504|15|SEVERE|Exception invoking periodic operation:
20060111|094345516|13|SEVERE|caught throwable
20060111|094349862|11|SEVERE|caught throwable
ERROR: 'null'
FATAL ERROR: 'Could not compile stylesheet'
20060111|094351885|14|SEVERE|WSS0147.unableto.use.stylesheet
20060111|094351885|14|SEVERE|unableto.dump.soapmessage
20060111|094353197|14|SEVERE|JAXRPCTIE01: caught exception while handling reques
t: javax.xml.rpc.soap.SOAPFaultException: Unable to dump SOAPMessage
20060111|094355140|13|SEVERE|caught throwable
20060111|094401369|11|SEVERE|caught throwable
20060111|094404424|13|SEVERE|caught throwable
20060111|094405776|14|SEVERE|caught throwable
20060111|094407859|13|SEVERE|caught throwable
20060111|094410212|14|SEVERE|caught throwable
20060111|094412355|13|SEVERE|caught throwable
20060111|094414158|11|SEVERE|caught throwable
20060111|094417233|13|SEVERE|caught throwable
20060111|094417233|11|SEVERE|Caught exception (java.lang.OutOfMemoryError) execu
ting org.apache.tomcat.util.net.TcpWorkerThread@7d27b0, terminating thread
20060111|094432595|15|SEVERE|Exception invoking periodic operation:
java.lang.OutOfMemoryError
20060111|094440557|14|SEVERE|caught throwable
20060111|094442610|13|SEVERE|caught throwable
20060111|094444353|14|SEVERE|caught throwable
20060111|094445925|13|SEVERE|caught throwable
20060111|094537481|15|SEVERE|Exception invoking periodic operation:
20060111|094648857|15|SEVERE|Exception invoking periodic operation:
20060111|094800302|15|SEVERE|Exception invoking periodic operation:
20060111|094911648|15|SEVERE|Exception invoking periodic operation:
20060111|094952859|15|SEVERE|Exception invoking periodic operation:
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
18 years ago
My app seems to have memory leak i would assume. Its basically an abstraction ontop of a database but when i run unit tests on a client application which calls out to this service it eventually yacks. If i run the unit test classes individually its fine (although after a number of them i run into the same problem) but if i run the whole suite (350 tests) its bombs out on the same test every time... ( that test basically causes one write and a read from the underlying DB). Whats the best way to tack where my problem specifically? takes 45 mins of unit tests to replicate this and setting breakpoints searching for the problem has been VERY difficult... suggestions?
here is the stack trace..
0060111|094336062|14|SEVERE|caught throwable
20060111|094337504|15|SEVERE|Exception invoking periodic operation:
20060111|094345516|13|SEVERE|caught throwable
20060111|094349862|11|SEVERE|caught throwable
ERROR: 'null'
FATAL ERROR: 'Could not compile stylesheet'
20060111|094351885|14|SEVERE|WSS0147.unableto.use.stylesheet
20060111|094351885|14|SEVERE|unableto.dump.soapmessage
20060111|094353197|14|SEVERE|JAXRPCTIE01: caught exception while handling reques
t: javax.xml.rpc.soap.SOAPFaultException: Unable to dump SOAPMessage
20060111|094355140|13|SEVERE|caught throwable
20060111|094401369|11|SEVERE|caught throwable
20060111|094404424|13|SEVERE|caught throwable
20060111|094405776|14|SEVERE|caught throwable
20060111|094407859|13|SEVERE|caught throwable
20060111|094410212|14|SEVERE|caught throwable
20060111|094412355|13|SEVERE|caught throwable
20060111|094414158|11|SEVERE|caught throwable
20060111|094417233|13|SEVERE|caught throwable
20060111|094417233|11|SEVERE|Caught exception (java.lang.OutOfMemoryError) execu
ting org.apache.tomcat.util.net.TcpWorkerThread@7d27b0, terminating thread
20060111|094432595|15|SEVERE|Exception invoking periodic operation:
java.lang.OutOfMemoryError
20060111|094440557|14|SEVERE|caught throwable
20060111|094442610|13|SEVERE|caught throwable
20060111|094444353|14|SEVERE|caught throwable
20060111|094445925|13|SEVERE|caught throwable
20060111|094537481|15|SEVERE|Exception invoking periodic operation:
20060111|094648857|15|SEVERE|Exception invoking periodic operation:
20060111|094800302|15|SEVERE|Exception invoking periodic operation:
20060111|094911648|15|SEVERE|Exception invoking periodic operation:
20060111|094952859|15|SEVERE|Exception invoking periodic operation:
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
18 years ago