cancel
Showing results for 
Search instead for 
Did you mean: 

ExceptionInInitializerError

Former Member
0 Kudos

Hi!

We are facing a strange problem at the moment. Our PageBuilder class usually instantiates the MAM095 manager, but since a couple of days, the line "ZWom095Manager manager095 = (Zwom095Manager)naming.lookup(ZWom095Manager.class.getName())" results in a ExceptionInInitializerError. Because of this, the FrontServlet cant be initialized aka no running application.

I tried to find the problem, but I got stuck. Anyone get any ideas how to solve this problem?

With regards,

Mike

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

hi mike,

it might be just a missing class in the classpath.

do you have the actual exception trace?

regards

jo

Former Member
0 Kudos

Hi Jo,

I dont have a trace a this moment, but I can get one. The strange thing about this is, I can run the application from within NWDS without any problems, but the created war file sometimes gives problems. Not always, but in certain cases (depends on installation, I get this error.

I have debugged some more. The problem lies in the call PageBuilder.setDisplayBundle(prop). When this call is made, it first tries to initialize all variables of the PageBuilder class. The error occurs on the line where a manager is instantiated. Now I try to find out whats wrong with that manager. But there can't be anything wrong, because this war file has been deployed and installed thousands of times already and it has not been changed since creation. I really think it has anything to do with errornous Java installation etc, but I cant find it.

With regards,

Mike

Former Member
0 Kudos

Okay, I did some additional debugging. The manager has some variables:

protected static final SyncBoDescriptorFacade DESC_FACADE = SmartSyncRuntime.getInstance().getSyncBoDescriptorFacade();

protected static final SyncBoDescriptor SYNC_BO_DESC = DESC_FACADE.getSyncBoDescriptor (SYNC_BO_NAME);

The problems lies within the SyncBoDescriptorFacade: it has NO SyncBoDescriptors in it. I got the SyncBoDescriptorIterator and its size was 0.

So the question now is, why does the SyncBoDescriptorFacade not instantiates its descriptors?

With regards,

Mike

Former Member
0 Kudos

hi mike,

was your application deployed successfully? or do you have the meRepMeta.xml

included in your application archive when it was dployed? might worth checking the

trace during the deployment process. there could be some xml parsing exceptions

or other else that had caused the metadata serialization to fail.

or if you are using fileIO, you can visually confirm if the metadata files are created

in the data folder with your apps' convid as the folder name.

reards

jo

Former Member
0 Kudos

Hi Jo,

Thanks for your help.

The application has been deployed properly, the standard way and by setup package. The meRepMeta.xml is included. We use db2e, so its hard to check whether the XML file has been processed correctly.

The strange part is, sometimes it helps to reinstall the application. Then after 2,3,4,5,6 times it suddenly works.

Cheers,

Mike