Anytime I add a new Attribute, I get "Duplicate ID" error

BenHayat

eagles9999 wrote
Just to do Update and Keep Locked from the BS Context Menu after the Ctrl-I fix.

As to why?.... Some things are intended to remain a mystery for mortals such as myself. 😉

Are you lately adding new attributes? If yes, how often do you get that error to do CTRL-I fix? What puzzles me, this started about a month ago. During initial development, when the BS was small and I was changing and adding attributes, no error. but now, it has become more fragile and when I add a new attribute, bang, I get the error. And I don't do any funky stuff.

customaware

These days it is rare Ben....

Probably 3-4 times over the last year.

customaware

Meant to say.....

Depending where you are in your dev cycle and depending what you have done.....

Make sure you keep an eye on BAS_IDGEN.

I screwed that up (Importing data from production server without recognising that the value on the PS was much higher than on my local machine)
[Always import that as well] and then all my IDs were screwed becasue they already existed.

Once I kicked that number up to match the PS it was fine.

BenHayat

Support had requested to send them the BSV and detailed step-by-step. I have...

Now I hope they can see what is causing it or a work around. Let's keep our fingers crossed! 🙂

ACDC

I have a very complex app in production and continuously changing and adding new features on a monthly basis, the bsv is almost 5MB and I have never experienced any of the problems mentioned in this post.

The one thing I make sure is to have all my development running on a remote server in a very clean and secure environment. Also, I continuously clean out all the previous published versions, the most I keep is two prior versions at any given time. (If you are developing on a laptop or a desktop that you use for other things as well, you are at risk of damaging your development environment, I have learnt that the hard way. ) BTW, faulty ram or disk drive could easily be the cause of these kinds of problems

Also, making sure that I have sufficient ram at all times when testing and publishing and before publishing always down the AwareIM server and then restart. If you run out of ram when going into Test or Publish then all sorts of things can happen without you even knowing it, only to discover two or three days down the track something has gone wrong, and then the crap starts

BenHayat

ACDC wrote
I have a very complex app in production and continuously changing and adding new features on a monthly basis, the bsv is almost 5MB and I have never experienced any of the problems mentioned in this post.

The one thing I make sure is to have all my development running on a remote server in a very clean and secure environment. Also, I continuously clean out all the previous published versions, the most I keep is two prior versions at any given time. (If you are developing on a laptop or a desktop that you use for other things as well, you are at risk of damaging your development environment, I have learnt that the hard way. ) BTW, faulty ram or disk drive could easily be the cause of these kinds of problems

Also, making sure that I have sufficient ram at all times when testing and publishing and before publishing always down the AwareIM server and then restart. If you run out of ram when going into Test or Publish then all sorts of things can happen without you even knowing it, only to discover two or three days down the track something has gone wrong, and then the crap starts

Thanks ACDC;
The dev machine, is a brand new I7 with 16GB RAM that is dedicated to Aware.
This issue only happens when adding attributes to an existing BSV. It started about a month ago, one in a while, and then got more frequent as of now. Everything else woks perfectly.

chris29

Hi Ben

We experience that same issue as you do for a number of years now. Its very difficult to replicate so support can fix the problem. Our bsv is 9meg in size and require 64bit java running with 6 gig, the configtool must have at least 3-4gig available to prevent out of memory issues.

The duplicate id issue happens generally if its objects/attributes that haven't been touched for a long time and all I do is add a new attribute to the object. The attribute is removed off all forms and queries and the data will be lost. With the new feature in 6.0 I can see it removing the attribute from the object and the adding it again.

I hope support can fix this issue.

kklosson

This is totally unsat. I can think of no higher priority for Support to focus on. It's clear this is not some fluke or user error. HAS. TO. BE. FIXED.

BenHayat

chris29 wrote
Hi Ben

We experience that same issue as you do for a number of years now. Its very difficult to replicate so support can fix the problem. Our bsv is 9meg in size and require 64bit java running with 6 gig, the configtool must have at least 3-4gig available to prevent out of memory issues.

The duplicate id issue happens generally if its objects/attributes that haven't been touched for a long time and all I do is add a new attribute to the object. The attribute is removed off all forms and queries and the data will be lost. With the new feature in 6.0 I can see it removing the attribute from the object and the adding it again.

I hope support can fix this issue.

Chris, this is it. But how can you run it in production? It looses data?

Another info. I run Aware server (development) and Tomcat as Windows Service, and not from Control Panel. Could this be the cause?
This is my memory configuration. Do I need to bump it up?

Please advise!

BenHayat

ACDC wrote
I have a very complex app in production

Tony, Question. Do you run Aware (during development and production) from control panel or from Windows service?
Thanks!

If you don't run into this and some of us do, then there has to be something in the environment that affects it.

BenHayat

Question: for Support and others;

The configurator, stores all our codes and configurations in the database plus it's own tracking system. I have a feeling something in that tracking data is out of balance.
My question is, is there a away to tell Aware to reset all the counters and recreate the whole BSV again, without loosing application data?

I mean I can export my app, delete the BS from configurator and then re-create the BS and re-import, but doing so, I will loose all my app data.

kklosson

I do not run as a service in dev or production and I've experience this.

BenHayat

kklosson wrote
I do not run as a service in dev or production and I've experience this.

Thanks, so it's not running as service that causes it.

I still strongly believe the internal counters get out of balance, and I don't know how to clean or reset them.

chris29

Control Panel and ConfigTool are run Standalone.

BenHayat

Chris, did you point out to Support that this phenomenon, actually "drops" a column (causing data loss) and then puts the column back, in these past years of having this problem? This is very serious, especially I never know what column is going to get sacrificed, because it seems it's randomly picked or whichever attribute that has the same ID as the new one. The error doesn't provide data which column is going to get killed.

Somehow, the newly added attribute gets an ID that already exists, so Aware basically removes the old attribute (causing the column drop and drop from forms), gives the old ID to the newly created attribute, creates a new ID and assigns it to the old attribute and gets added to database. This seems to be the process that takes place.

Seems like the total count of IDs gets out of sequence somehow.
Just my two cents, hope it helps to pinpoint the problem.

ACDC

Ben

If you don't run into this and some of us do, then there has to be something in the environment that affects it.

The fact that I have not experienced this problem may be because I am not going through a sequence of events in the configurator as you are doing, so the problem could well be there. What I am suggesting is make sure your environment is 100% intact and your BSV is not corrupt before trying to find the problem in AIM

Losing data is a severe problem, maybe you should export your BSV and do a clean install, also dump your DB to a sql file, delete it and re- import

I run on a Windows Server 2008 R2, MySql5.6 , AIM - 3Gb , Tomcat 2.5GB ,Config 1.5GB.
I try keep my memory utilisation at 60 % of the settings. I monitor this from time to time in the windows task manager

Also, monitoring memory usage is a good indicator of your rule behavior, memory usage should maintain a good average usage and flush itself out periodically . If you have configured a rule incorrectly your system could become unstable. Because of the delinquent rule its uses up all available allocated memory space . So being vigilant in this area is a good idea.

BTW, I found version 6 is very unforgiving when it comes to custom html, I had to redo all my forms for this upgrade, So if something suddenly disappears off the form it could be a corrupt form - but deleting data in the DB sounds like something more sinister

chris29

Yes Ben I have reported this in the past. When it occurs the attribute is output in the console so I generally am aware of which one if going to be dropped.

I don't believe its anything to do with our environment. I think its a bug in the configtool when maintaining objects and the allocation of the ID. We can do several changes to objects without a problem then the duplicate id will occur on a single change.

If support can replicate in your bsv then hopefully it can be fixed.

BenHayat

chris29 wrote
Yes Ben I have reported this in the past. When it occurs the attribute is output in the console so I generally am aware of which one if going to be dropped.

I don't believe its anything to do with our environment. I think its a bug in the configtool when maintaining objects and the allocation of the ID. We can do several changes to objects without a problem then the duplicate id will occur on a single change.

If support can replicate in your bsv then hopefully it can be fixed.

You said it perfectly. That is my case, I can't replicate it, knowing when it will happen.

tford

I have never experienced the issue you are describing.

I develop 100% on my laptop with Derby database, then always export the BSV to my laptop. When I'm ready to update the production BSV on our server, I always use Standard | Upload Version (after backing up the production MySql database of course) to grab the BSV from my laptop & publish the new version on the server.

BenHayat

I've decided to take baby steps to avoid this problem. Today I have to add a series of attributes, so this is what I've done so far, and have not received the error yet:
1) Update & lock BS
2) Add an attribute
3) Save
4) Update & lock BS
5) click on TEST button to commit that attribute to DB.

If this works and doesn't cause me loose other attributes, then I don't mind the steps.

« Previous Page Next Page »