cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
122
Views
0
Helpful
0
Comments
cdnadmin
Community Member
This document was generated from CDN thread

Created by: null on 07-09-2005 04:34:15 PM
We have an existing Audium environment running Audium applications.
I developed a new application which ran also once. Then I changed something and after that when I copied the application directory into the Audium run time environment, and ran the 'updateApp.bat' script, it did not say "Application 'xxxx' has been updated. but simply says "Press any key to continue".

Usually, when this happens, the application is deployed but I am not able to make phone calls to it. The application seems to be in a weird state.

I have tried to reboot the machine, restart the Audium servers with no success. Please advise what else to do ?

Deepak

Subject: RE: running the updateApp.bat script
Replied by: Vance Vagell on 07-09-2005 05:04:52 PM
Hi Deepak,

In order to assist you with this issue, we need some additional information:

1) Did you deploy the Audium application from Audium Builder for Studio, and then copy the deployed folder into AUDIUM_HOME/applications? From your post, it sounds as though you may have copied the application directory (from within Studio's workspace directory) without first deploying it.

2) If you [i:36d7d87210]did[/i:36d7d87210] deploy the application and copied the correct folder, then could you please elaborate on the nature of the changes you made? Also, what does Audium Call Services report when the application server is started? When the application server is started, Audium Call Services will list each Audium application, and an error if there is a problem loading that application.

3) What version of Audium Studio and Call Services are you using? What version of Java? Which application server and version?

Regards,
Vance

Subject: RE: running the updateApp.bat script
Replied by: null on 07-09-2005 05:32:43 PM
Hi,

My replies below. Deepak

Hi Deepak,

In order to assist you with this issue, we need some additional information:

1) Did you deploy the Audium application from Audium Builder for Studio, and then copy the deployed folder into AUDIUM_HOME/applications? From your post, it sounds as though you may have copied the application directory (from within Studio's workspace directory) without first deploying it.

Reply:Yes, application was deployed from audium 3.3 builder for studio on one m/c and then I copied the deployed folder into the AUDIUM_HOME/applications directory on another machine. The first time I did this, I ran the deployApp.bat script in the destination m/c and may be the updateApp.bat script(I don't remember). Anyway, the updateApp.bat most likely was a redundant operation.

The application ran successfully with the activity_logs tracing the call. Then I made some changes(I don't remember what but they ranged from may be minor changes in the call flow and minor changes in the java classes ). Then I copied the application folder(after doing a save and generate each time) from the source to the destination folder. Then when I tried to run updateApp.bat, it simply came back saying "press any key to continue..."

2) If you [i:761ffc47fa]did[/i:761ffc47fa] deploy the application and copied the correct folder, then could you please elaborate on the nature of the changes you made? Also, what does Audium Call Services report when the application server is started? When the application server is started, Audium Call Services will list each Audium application, and an error if there is a problem loading that application.

Reply:Some changes I did were copying existing java classes from other applications into this application's java classes folder. We are using Audium 3.3, it doesn't seem to report any errors when the updateApp.bat script is run. Also, when I run the deployApp script, it says that the application is already deployed.

3) What version of Audium Studio and Call Services are you using? What version of Java? Which application server and version?

Reply:Audium 3.3, Call Services - don't know, j2sdk1.4.2_06,
application server is IBM WebSphere Application server ver 4.0.5

Regards,
Vance[/quote:761ffc47fa]

Subject: RE: running the updateApp.bat script
Replied by: null on 07-09-2005 06:34:29 PM
Hi Vance,
More info: I am able to bring my application in the Audium builder and "save & generate" it successfully on the destination m/c also.
But updateApp script still behaves the same as discussed below.

Deepak

Hi,

My replies below. Deepak

Hi Deepak,

In order to assist you with this issue, we need some additional information:

1) Did you deploy the Audium application from Audium Builder for Studio, and then copy the deployed folder into AUDIUM_HOME/applications? From your post, it sounds as though you may have copied the application directory (from within Studio's workspace directory) without first deploying it.

Reply:Yes, application was deployed from audium 3.3 builder for studio on one m/c and then I copied the deployed folder into the AUDIUM_HOME/applications directory on another machine. The first time I did this, I ran the deployApp.bat script in the destination m/c and may be the updateApp.bat script(I don't remember). Anyway, the updateApp.bat most likely was a redundant operation.

The application ran successfully with the activity_logs tracing the call. Then I made some changes(I don't remember what but they ranged from may be minor changes in the call flow and minor changes in the java classes ). Then I copied the application folder(after doing a save and generate each time) from the source to the destination folder. Then when I tried to run updateApp.bat, it simply came back saying "press any key to continue..."

2) If you [i:58ec0c40b6]did[/i:58ec0c40b6] deploy the application and copied the correct folder, then could you please elaborate on the nature of the changes you made? Also, what does Audium Call Services report when the application server is started? When the application server is started, Audium Call Services will list each Audium application, and an error if there is a problem loading that application.

Reply:Some changes I did were copying existing java classes from other applications into this application's java classes folder. We are using Audium 3.3, it doesn't seem to report any errors when the updateApp.bat script is run. Also, when I run the deployApp script, it says that the application is already deployed.

3) What version of Audium Studio and Call Services are you using? What version of Java? Which application server and version?

Reply:Audium 3.3, Call Services - don't know, j2sdk1.4.2_06,
application server is IBM WebSphere Application server ver 4.0.5

Regards,
Vance[/quote:58ec0c40b6][/quote:58ec0c40b6]

Subject: RE: running the updateApp.bat script
Replied by: null on 07-09-2005 07:00:53 PM
Hi Vance,

To make the application to work, I tried stopping and starting the Audium server. It worked as a result of this operation. Now, the question, I have is why updateApp and deployApp script did not make the application to work but bouncing the server cleared the problem. I was moving some java classes around when the application was not able to start properly.
I think that caused the Audium server to get into this state. Please let us why and how this could happen. Any help would prevent us from creating this situation again.

Thanks

Deepak

Subject: RE: running the updateApp.bat script
Replied by: Vance Vagell on 07-09-2005 07:48:16 PM
Hi Deepak,

In your original post you said that restarting the server had no effect on the problem. However, you just now posted that this has resolved the problem. What changed since the first time you tried restarting the server?

I believe that this problem is related to the custom classes that this application uses. Running updateApp will attempt to load all of the application's classes, and you mentioned that one of the changes was to the classes. Does this problem affect other Audium applications on the same server? If so, do they share any common classes? Also, could you please explain what the classes you modified are used for (e.g. custom elements, on call start classes, etc.)?

It is highly likely that one of the modified classes has a problem that is preventing updateApp from running smoothly.

Regards,
Vance

Subject: RE: running the updateApp.bat script
Replied by: null on 08-09-2005 06:54:37 PM
Hi Vance,

Sorry for the delayed response. I had to really dig into why restarting the server did not work before but worked later.

We had an earlier version of a class X that was subclassed from an action base class which was later subclassed from a decision base class. When the new class X was replaced with the old call flow accessing it still as an action class, caused this problem. The updateApp script doesn't give a reason ( or even a pointer to a problem causing class) which makes it very hard to debug. This I believe is a big limitation to using Audium.

Please advise any ways for debugging such problems.

Another related issue that I see is that within an application, all classes must have unique names even though they are part of different java packages( placed in different directory heirarchies under the application/classes). Any reason why you treat them this way but never give an error of such duplication when updateApp script is run.

Thanks

Deepak

Hi Deepak,

In your original post you said that restarting the server had no effect on the problem. However, you just now posted that this has resolved the problem. What changed since the first time you tried restarting the server?

I believe that this problem is related to the custom classes that this application uses. Running updateApp will attempt to load all of the application's classes, and you mentioned that one of the changes was to the classes. Does this problem affect other Audium applications on the same server? If so, do they share any common classes? Also, could you please explain what the classes you modified are used for (e.g. custom elements, on call start classes, etc.)?

It is highly likely that one of the modified classes has a problem that is preventing updateApp from running smoothly.

Regards,
Vance[/quote:ca1952a736]

Subject: RE: running the updateApp.bat script
Replied by: Vance Vagell on 08-09-2005 08:32:02 PM
Hi Deepak,

There is an existing feature request for Audium Call Services to output stack traces for custom code issues during execution of the administrative scripts (e.g. updateApp), this has been logged in our internal issue tracking system. For now, if you suspect that custom code is the cause of your problems while running an administrative script, try reworking your application (temporarily) to not use custom code, and then add the custom classes back in one by one until the script has issues. The class that causes the script to malfunction is where to look for problems.

In regards to unique class names, the requirement you described is not quite accurate. Audium requires that the package plus the class name be unique, therefore there can exist two classes of the same name as long as they are in different packages. For example, com.test.myclass and com.someothertest.myclass can both coexist. If you were to add a standard Action element that utilizes the first of these example classes, you would enter "com.test.myclass" into the element configuration. What situation did you encounter that led you to believe otherwise?

Regards,
Vance

Subject: RE: running the updateApp.bat script
Replied by: null on 08-09-2005 08:59:15 PM
Hi Vance,

Thanks for your valuable information. In regards to unique names.
We copied an identical class name say 'X' in directory
common/classes/dir1/X and common/classes/dir2/X.

This class was compiled under package dir1. Did this fact made them identical for the class loader ?

Thanks

Deepak

Hi Deepak,

There is an existing feature request for Audium Call Services to output stack traces for custom code issues during execution of the administrative scripts (e.g. updateApp), this has been logged in our internal issue tracking system. For now, if you suspect that custom code is the cause of your problems while running an administrative script, try reworking your application (temporarily) to not use custom code, and then add the custom classes back in one by one until the script has issues. The class that causes the script to malfunction is where to look for problems.

In regards to unique class names, the requirement you described is not quite accurate. Audium requires that the package plus the class name be unique, therefore there can exist two classes of the same name as long as they are in different packages. For example, com.test.myclass and com.someothertest.myclass can both coexist. If you were to add a standard Action element that utilizes the first of these example classes, you would enter "com.test.myclass" into the element configuration. What situation did you encounter that led you to believe otherwise?

Regards,
Vance[/quote:734e5a3168]

Subject: RE: running the updateApp.bat script
Replied by: Vance Vagell on 08-09-2005 09:09:58 PM
Hi Deepak,

Per the Java specification, the location of a class file must match its package. For example, if a class named myclass is part of the com.test package, the myclass.class file must be located within com/test/ for it to work properly.

In the example you gave, you have a class named dir1.x, and have distributed it both to dir1/ and dir2/. The copy in dir2/ will have problems, because its location does not match its package.

Hope this helps,
Vance
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links