Nickolas Case

Ranch Hand
+ Follow
since Apr 26, 2008
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
In last 30 days
0
Forums and Threads

Recent posts by Nickolas Case

I solved my issue. I hadn't implemented JTA correctly and I didn't need to. After I reverted my code to JNDI lookup and added the following jars my code worked.

com.bea.core.diagnostics.instrumentor_1.0.1.0.jar
com.bea.core.repackaged.asm_1.5.2.jar
com.bea.core.xml.beaxmlbeans_2.2.0.0


Of course, you'll still need the wlfullclient.jar using the jarbuilder.

Also, you don't want weblogic.jar along with wlfullclient.jar as this can cause errors too.

Cheers!
12 years ago
Hello all!

I have been racking my brain for the last few days trying to convert a standalone java application from a standard database connection to a JNDI lookup on a weblogic server and I can't seem to get it to work.

applicationContext.xml follows:



persistence.xml:



I apologize if this isn't the correct forum.

12 years ago
When I get the Runtime object, it shows four processors available and lots of memory. I thought it might be how the command was being sent in one string so I broke the string up into an array and it still failed intermittently. I have googled my issue with no luck.


I am considering rewriting this application but I am afraid the issue will persist. Does anyone have any suggestions?
13 years ago
A little more troubleshooting has revealed when the Process errors out the string isn't parsed and sent to the Process object. Shouldn't that throw a null pointer exception?
13 years ago
I can run the command passed to the exec() method on the command line without a problem. As part of my troubleshooting, I had the command printed out to the console. I have cut and pasted the printout to the command line and it has run every time.

I am consuming the error and output streams associated with the run. From debugging, it looks like the call is never even sent to the system. I ran truss on the command as part of the troubleshooting to see what was going on. When the waitFor() returns a 1, the truss is never executed.
13 years ago
Hello all!

First off, I apologize if this is in the wrong forum.

I have been troubleshooting an intermittent problem where a system call Process automatically returns a waitFor() value of one. There is no rhyme or reason that I can find, nor does any type of error occur.

Has anyone ever experienced this type of behavior?

I am really stumped at this point...

Thanks in advance!
13 years ago
Have you solved your issue?

I am also not very good with generics but hopefully my response will get the creative juices flowing for the other guys

The error looks to me like it is looking for the constructor(T,V) and finding (V,T) instead. The compiler, not finding what it is looking for, stops.


Is this a correct assumption or am I way off base?
13 years ago
Yes. My apologies for not stating that up front.
13 years ago
Bag API


The easiest to explain it would be likening it to an online shopping cart. One instance of the object is kept along with a quantity.

13 years ago
Have you looked at using a Bag instead of a Set?
13 years ago
Hello all,

I have a threaded application that can make multiple changes to single rows/fields and the final change is not being persisted through dirty checking.


Examples:
Row 1 has change A made to it. Change A is not persisted
Row 2 has change A made to it, then change B. Only change A is persisted

This is a very heavy application, with changes numbering in the thousands per run. Could this be the culprit?


Unit tests pass which leads me to believe it is a concurrency issue, has anyone ran into this issue before?

some code:





All threads process similarly...


The following code returns all files from the directory. Why?





13 years ago
Hello all,

I have an application with multiple threads, each reading different data(possibly from the same rows) from the same table, and makes changes based on data pulled from other pertinent rows in the table. Each thread has its own @Transaction annotation and according to the log, they are all getting their own transaction. The app pulls all data, logs changes to be made, makes the changes to the JPA object etc. fine but the program never persists any of the changes made back to the table.

All my research has led me to believe this should be working.


The flow for my program according to the log file seems to be that each thread gets a transaction, gets an EntityManager, pulls the data, closes the EM, and as they are processing(getting the other pertinent data), getting new EM's for each data pull.



This program was working before I threaded it as it was taking far too long as a single thread application.

I know I haven't given a lot of information out because I don't want to scare anyone away...

I will answer/provide info for any questions.

Thanks in advance for any help!
13 years ago