Subject:
[Incident 030423-000002] An issue that has arisen with PB 4.5 (restricted edition) for use for S1AS. S...
From:
###@###.###
Date:
Wed, 23 Apr 2003 19:01:53 -0700 (PDT)
To:
###@###.###

Your question has been received. You will receive a response by e-mail
from the Pointbase technical support team.

Our hours of operation are:
8:30 - 5:00 Pacific Time Monday-Friday


Question Reference #030423-000002
---------------------------------------------------------------
            Summary: An issue that has arisen with PB 4.5 (restricted
                     edition) for use for S1AS. S...
            Product: PointBase Server
           Category: Features
Contact Information: ###@###.###
       Date Created: 04/23/2003 07:01 PM
       Last Updated: 04/23/2003 07:01 PM
             Status: Critical
            Version: 4.5
                JVM: 1.4.1_02
                 OS: Solaris


Discussion Thread
---------------------------------------------------------------
Customer (Jonathan Bruce) - 04/23/2003 07:01 PM
An issue that has arisen with PB 4.5 (restricted edition) for use for S1AS.

Synopsis: Manually deploying the timer.ear requires a server restart after java2db create

 Synopsis: Manually deploying the timer.ear requires a server restart After manually deploying the timer.ear (timer application) the java2db kicks in to create the table gets created in the POINTBASE database. Immediately after the table gets created if I run the devtest (sessiontimer) I get an execption
 
EJB5102:Unable to complete container-managed transaction
javax.transaction.SystemException: org.omg.CORBA.INTERNAL: JTS5031: Exception
[org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed: Maybe] on
Resource [commit one phase] operation. vmcid: 0x0 minor code: 0 completed: No

After this point the only way to get back into a clean state I need to restart both the application server and the Pointbase database.

In the above scenario, if I restart the application server after I have deployed the timer.ear and then tried the ant sessiontimer (under devtests/ejb/timer), the test works correctly.

I have attached the various log files under /home/pramodg/04152003. Also when running the same scenario using the old Pointbase (4.2) server I get some error on the ./StartServer screen. I have captured these messages into the file "server_error_messages".

I also tested this against Oracle database and found that I did not have to do this restart business for Oracle. But we cannot accept the users to have Oracle datasource configured for ejb timer service to be working.

Justification:

For the Timer service to be working with the bundled Pointbase, we need this bug to be fixed. The plan is to have the timer application come up as system application. If we do not fix this then we would have to recommend to the user to restart the application server after the timer application gets deployed.

Work around:
The current workaround is to restart the application server after the timer application has been deployed but before any applications have invoked method on the timer server. This is not acceptable.