Print

[lolo]

Ok, I got the status problem nailed down. It was a stupid mistake in my code that was causing waitForResults() to not wait at all 
I also finally reproduced the ClassNotFoundException. It was not occurring because JPPF_J2EE_Demo_JBoss.ear was also deployed, and for some reason JBoss would look for the class in its libs. I fixed that as well.
I tried from a fresh installation, and it is working for me, I do get the option value in the soap response. I do not have jppf-j2ee-client.jar in the /lib folder of the server

I have updated the jppf_ra_JBoss.rar (same URL for download). Can you give it a try?

Thanks,
-Laurent

[anand6998]

Thank you very much Laurent. It all works now. Much appreciate the time you put into helping me work through the issues

Now, I am past the first hurdle, I have a couple of questions about trying to use JPPF for full fledged pricing library
a. How can I enable logging in OptionValuationTask - I have been getting by with System.out statements but I would like to write out to a log file for each node. Right now it gives me an error saying Logger is not Serializable.
b. As the code base for the library grows how can I NOT serialize all the classes from client to server. Is there a server deployment mechanism that would save me the serialization time.

Thanks a lot for your help
Amit

[lolo]

Hi Amit,

Thanks for sharing the good news.

To avoid the problem with the Logger, you should make it static. Static fields are never serialized. This is also a common practice.

Regarding the other point, I'm not sure if you're talking about object serialization or about class loading, could you clarify?
If this is about class  loading, then there are 2 different things you can do:
- just ignore it, the class loading overhead will happen only once for a given JPPF client instance (which is create dby the resource adapter). This means the first job execution will take longer,  but then the nodes will have the required classes loaded and won't need to load them again and subsequent jobs will have the expected execution time. So the class loading overhead is a one-time thing
- you may also deploy your libraries in the classpath of the server or of the nodes. I suggest you read this other thread where more details are provided on this.

Sincerely,
-Laurent