Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Sign up

Sign up | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Error when starting up Maximo
Starting up Maximo 7.6.1.x on WebLogic 12
September 17, 2020
1:10 pm
Avatar
Brad
New Member
Members
Forum Posts: 1
Member Since:
October 10, 2013
sp_UserOfflineSmall Offline

I’m a developer for Maximo. Since Maximo 6.x, we have written custom java code, using Eclipse for development and WebLogic to test.

Currently, I set up my development environment with WebLogic 12 running Maximo as an “exploded” ear, where code can be directly compiled into the /businessobjects/classes directory rather than building an ear.

 

I occasionally have issues when setting up a new Maximo environment on my development PC. On startup, I will get the following error:

 

<Sep 17, 2020, 8:03:20,735 AM CDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application “maximo” due to error weblogic.management.DeploymentException: weblogic.application.naming.ReferenceResolutionException:

[J2EE:160200]Error resolving ejb-ref “ejb/maximo/remote/accesstokenprovider” from module “/mbojava/javamodule” of application “maximo”.

The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified.

Attempts to automatically link the ejb-ref to its target bean failed because no EJBs in the application were found to implement the “psdi.security.ejb.AccessTokenProviderHomeRemote” interface.

Link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.

weblogic.management.DeploymentException: weblogic.application.naming.ReferenceResolutionException: [J2EE:160200]Error resolving ejb-ref “ejb/maximo/remote/accesstokenprovider” from module “/mbojava/javamodule” of application “maximo”. The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified. Attempts to automatically link the ejb-ref to its target bean failed because no EJBs in the application were found to implement the “psdi.security.ejb.AccessTokenProviderHomeRemote” interface. Link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.

at weblogic.application.internal.flow.ReferenceResolutionFlow.resolveReferences(ReferenceResolutionFlow.java:42)

at weblogic.application.internal.flow.ReferenceResolutionFlow.prepare(ReferenceResolutionFlow.java:31)

at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:727)

at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)

at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:239)

Truncated. see log file for complete stacktrace

 

Does anyone know what causes this and how to fix it?

 

I cannot tell a difference in a maximo environment that give me this error, and one that doesn’t, even for identical versions of Maximo. I’ve checked the /mbojava/javamodule directory that the error refers to, and in all Maximo instances I have, they all look the same.

 

Thanks!

Forum Timezone: America/New_York

Most Users Ever Online: 54

Currently Online:
1 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

sun kim: 60

madd0g17: 59

v.barsamov: 51

Maximofresher: 45

cgregory: 45

matta0990: 33

Member Stats:

Guest Posters: 0

Members: 14009

Moderators: 0

Admins: 3

Forum Stats:

Groups: 1

Forums: 8

Topics: 1564

Posts: 4277

Newest Members:

Daniel Trujillo, Madge Stringfield, Sima Howard, Columbus Ainsworth, R B, Maricruz Kabu

Administrators: Chon: 1118, kristensibilia: 0, Joe Grassia: 0