Erik Eide
2004-12-29 15:40:35 UTC
Hi
Are there any limitations/restrictions on calling out to a third-party library within an ejbCreate method of a stateless session bean.
I've set <initial-beans-in-free-pool> to 1 so that when I deploy the bean ejbCreate is invoked, but only the first System.out appears. The weblogic console shows the EJB deployment status as available, no stack traces of exceptions are shown.
[pre]
public void ejbCreate() {
try {
System.out.println(new Date() + " EJB XTestBeam ejbCreate invoked");
searcher = new SearcherService();
System.out.println(new Date() + " EJB XTestBean created SearchService " + searcher);
System.out.println(new Date() + " EJB XTestBean ejbCreate completed ok");
} catch (EJBException e) {
e.printStackTrace();
throw e;
} catch (RuntimeException e) {
e.printStackTrace();
throw e;
} catch (Exception e) {
e.printStackTrace();
}
}
[/pre]
The environment is WLS 8.1 SP4, W2K, HotSpot Client VM 1.4.2_05.
Rgs
Erik
Are there any limitations/restrictions on calling out to a third-party library within an ejbCreate method of a stateless session bean.
I've set <initial-beans-in-free-pool> to 1 so that when I deploy the bean ejbCreate is invoked, but only the first System.out appears. The weblogic console shows the EJB deployment status as available, no stack traces of exceptions are shown.
[pre]
public void ejbCreate() {
try {
System.out.println(new Date() + " EJB XTestBeam ejbCreate invoked");
searcher = new SearcherService();
System.out.println(new Date() + " EJB XTestBean created SearchService " + searcher);
System.out.println(new Date() + " EJB XTestBean ejbCreate completed ok");
} catch (EJBException e) {
e.printStackTrace();
throw e;
} catch (RuntimeException e) {
e.printStackTrace();
throw e;
} catch (Exception e) {
e.printStackTrace();
}
}
[/pre]
The environment is WLS 8.1 SP4, W2K, HotSpot Client VM 1.4.2_05.
Rgs
Erik