Issue Details (XML | Word | Printable)

Key: GLASSFISH-18245
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Romain Grécourt
Reporter: Alex Pineda
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

[Regression] SDK sample EJB Timer (bundled with GF 3.1.2) fails to run - javax.naming.NamingException: Lookup failed

Created: 24/Jan/12 05:26 PM   Updated: 01/Feb/12 04:02 PM   Resolved: 01/Feb/12 04:02 PM
Component/s: sample_apps
Affects Version/s: 3.1.2_b18
Fix Version/s: 3.1.2_b20

Time Tracking:
Not Specified


Oracle Enterprise Linux 6, JDK1.6.0_30. Used promoted build. Firefox Browser 3.6.25. Default "typical" installation with no password. CLASSPATH=$S1AS_HOME/lib/javaee.jar

Tags: 3_1_2-approved
Participants: Alex Pineda, Romain Grécourt and scatari

 Description  « Hide

The EJB Timer sample worked and was functional with promoted build 16.

The problem is seen with promoted build 18, when "ant run" target is invoked. The sequence of steps are:
o machine$ cd $S1AS_HOME/sample/javaee/ejb/automatic-timer
o ant compile
o ant package
o ant run

The error message seen is as follows:
[java] Waiting for the timer to expire
[java] Logged timeouts :
[java] javax.naming.NamingException: Lookup failed for 'java:global/automat ic-timer-ejb/StatelessSessionBean' in SerialContext[myEnv={java.naming.factory.i nitial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.fact ory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba. ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is javax.naming.N ameNotFoundException: automatic-timer-ejb]
[java] at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialCon
[java] at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialCon
[java] at javax.naming.InitialContext.lookup(
[java] at tRecords(
[java] at in(
[java] Caused by: javax.naming.NameNotFoundException: automatic-timer-ejb
[java] at com.sun.enterprise.naming.impl.TransientContext.resolveContex t(
[java] at com.sun.enterprise.naming.impl.TransientContext.lookup(Transi
[java] at com.sun.enterprise.naming.impl.TransientContext.lookup(Transi
[java] at com.sun.enterprise.naming.impl.SerialContextProviderImpl.look up(
[java] at com.sun.enterprise.naming.impl.RemoteSerialContextProviderImp l.lookup(
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
[java] at java.lang.reflect.Method.invoke(
[java] at ToMethod(
[java] at
[java] at pl.dispatchToServant(
[java] at pl.dispatch(
[java] at eRequestRequest(
[java] at eRequest(
[java] at eInput(
[java] at 1_2.callback(
[java] at eRequest(
[java] at tch(
[java] at k(
[java] at$Worke rThread.performWork(
[java] at$Worke
[java] Exception in thread "main" java.lang.NullPointerException
[java] at in(

scatari added a comment - 25/Jan/12 12:17 AM

Romain, please evaluate to see if a workaround can be documented.

Romain Grécourt added a comment - 26/Jan/12 07:14 PM - edited

A possible workaround would be to provide "" at comandline.
For instance: ant run.

Romain Grécourt added a comment - 26/Jan/12 07:14 PM

What is the impact on the customer of the bug?

User following instructions will not be able to run the sample.
It is a regression.

  • What is the cost/risk of fixing the bug?
    The fix is very simple.
  • Is there an impact on documentation or message strings?
  • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
    Try to run the sample again.
  • Which is the targeted build of 3.1.2 for this fix?