gandalf

Greenhorn
+ Follow
since Oct 24, 2002
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 gandalf

A developer launches the EJB Test Client by selecting the EJB in the J2EE View and selecting "Run on Server." After the server starts, the following message is observed:
not perform lookup with JNDI name: a/b/MyEJB
What should the developer do to diagnose the problem?
a) Look at the Bindings page of the EJB Extension Editor.
b) Use netstat to identify port conflicts.
c) Look at the LoggingUtil.log file in the workspace's .metadata folder.
d) Look at the server's console to search for "Error starting" message for the MyEJB bean.
e) Look at the trace.log file under the workspace's .metadata\.plugins\com.ibm.etools.websphere.tools\logs directory.
Multiple Select - Please select all of the correct answers (this question has 3 correct choices).
The right answers:
a,d,e
100% of all
Thanks everybody.

A developer launches the EJB Test Client by selecting the EJB in the J2EE View and selecting "Run on Server." After the server starts, the following message is observed:
not perform lookup with JNDI name: a/b/MyEJB
What should the developer do to diagnose the problem?
a) Look at the Bindings page of the EJB Extension Editor.
b) Use netstat to identify port conflicts.
c) Look at the LoggingUtil.log file in the workspace's .metadata folder.
d) Look at the server's console to search for "Error starting" message for the MyEJB bean.
e) Look at the trace.log file under the workspace's .metadata\.plugins\com.ibm.etools.websphere.tools\logs directory.
Multiple Select - Please select all of the correct answers (this question has 3 correct choices).
The right answers:
a,d,e
100% of all
Thanks everybody.