Chandima Janakantha

Greenhorn
+ Follow
since Aug 31, 2006
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 Chandima Janakantha

You should be able to do this in the same session. after executing the first query use
session.flush(); to load the results for the query.
To have access to Intial context you need to run within a EJB or Web Module, or else it should be a J2EE Client.

Then to access the beans through local JNDI reference you need to have EJB Reference created and access through java:comp/env/ intial context.
Have a look at the server logs when this is happening. if server logs are posted it would be easier to diagnose the problem.
15 years ago
The problem here is which ever the application first starts, loads the dll file and second application sees this. The easiest fix (if possible) is to run the the two applications in different JVMs. In websphere you can do this by creating a different Application Servers though Websphere Admin Console (browser based). Each Application Server runs in a different JVM and won't cause this issue.

But if you need to run both apps in the same server you may need to investigate whether you can share a dll loaded by another class loader. Try catching the UnsatisfiedLinkError and NOT throwing it in both apps so that the second application will try to work without loading the dll. (note that UnsatisfiedLinkError is an Error not an Exception, So catch UnsatisfiedLinkError or Throwable instead of catching Exception).
15 years ago
double check whether you have included jdom.jar in your manifest file. if not include it and re-deploy.
15 years ago
In testapp project try following.
testapp> right click> select properties> java Jar Dependancies
and check whether log4j.jar is selected there. if not select and give it a try.
15 years ago