2 Replies Latest reply on Mar 23, 2009 9:24 AM by Dustin Hittenmiller

    JNDI, Quartz, and god Is it a weird issue

    Dustin Hittenmiller Newbie

      Hi folks,

      I've got a really weird issue involving a named JNDI Oracle DS, Quartz Scheduling and Crystal Reports XI for Java. I've created a micro reporting app that allows users to schedule the reports to run at a later time.

      The issue I'm having is when in the Quartz job process I created for generating the report, The Crystal component loses the JNDI Object and can't access the data base, the first bizarre thing is that I use the same connection before hand to gather the stored parameter information to pass into the report and the code I wrote can successfully use it to make database look ups.

      The next odd thing is I have a manual way to kick this process off through an applet interface that goes through the same Quartz job process and works to completion with no issues.

      The final odd thing that has got me very confused on how Jboss and JNDI operate together is that I can deploy the app undeploy it and then promptly redeploy it and have NONE of the above issues. Can some one point me in a direction to solve this deployment issue, if I can get that solved it will take care of the other two quarks.

      This issue happens on both Jboss AS 4.2.2.ga and 4.2.3.ga

      I appreciate any help that can be sent my way

        • 1. Re: JNDI, Quartz, and god Is it a weird issue
          jaikiran pai Master

          We would need some stacktrace, the relevant piece of code to get started on understanding what the issue might be. Please post them.

          While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted.

          • 2. Re: JNDI, Quartz, and god Is it a weird issue
            Dustin Hittenmiller Newbie

            Here is the stack I'm receiving,

            2009-03-23 08:19:37,906 INFO [STDOUT] [ERROR] - JRCAgent2 detected an exception: Error finding JNDI name (CAMPUSCALL)
             at com.crystaldecisions.reports.reportdefinition.datainterface.a.a(Unknown Source)
             at com.crystaldecisions.reports.reportdefinition.datainterface.a.a(Unknown Source)
             at com.crystaldecisions.reports.reportdefinition.datainterface.a.a(Unknown Source)
             at com.crystaldecisions.reports.reportdefinition.datainterface.a.a(Unknown Source)
             at com.crystaldecisions.reports.reportdefinition.datainterface.g.a(Unknown Source)
             at com.businessobjects.reports.sdk.b.b.byte(Unknown Source)
             at com.businessobjects.reports.sdk.b.b.int(Unknown Source)
             at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
             at com.crystaldecisions.proxy.remoteagent.x.a(Unknown Source)
             at com.crystaldecisions.proxy.remoteagent.q.a(Unknown Source)
             at com.crystaldecisions.sdk.occa.report.application.dd.a(Unknown Source)
             at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
             at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
             at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
             at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
             at com.crystaldecisions.reports.sdk.PrintOutputController.export(Unknown Source)
             at com.rcody.ReportEngine.batching.ReportEngineBatchJob$ExecuteSavedReports.doReportExport(ReportEngineBatchJob.java:950)
             at com.rcody.ReportEngine.batching.ReportEngineBatchJob$ExecuteSavedReports.run(ReportEngineBatchJob.java:543)
             at com.rcody.ReportEngine.batching.ReportEngineBatchJob.runJob(ReportEngineBatchJob.java:218)
             at com.rcody.ReportEngine.batching.ReportEngineBatchJob.execute(ReportEngineBatchJob.java:156)
             at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
            


            I'm not sure how much help this is going to be as, I wrote earlier it seems to be more of a JNDI configuration issue with Jboss, as it works in all instances but through the scheduled process.

            Thanks for the help!