[gcamacho@sandp.com]

I believe I’ve set up WebLogic 9.2 correctly in MyEclipse 6.6. It’s set up as follows:

BEA home directory: c:\bea
WebLogic installation directory: c:\bea\weblogic92
Execution domain root: C:\bea\user_projects\domains\MyDomain
Execution server name: AdminServer
Security policy file: c:\bea\weblogic92\server\lib\weblogic.policy

———————————————————————————————

I can start and stop the app server outside of MyEclipse with no problem but when I try to start it from within MyEclipse, I get an authentication error.

I entered the same username and password I use to log in to the app server outside of MyEclipse. That didn’t work.

Then I entered the encrypted values of username and password from the boot.properties file. That didn’t work either.

This is what I get:

<Mar 10, 2009 4:03:44 PM EDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
C:\bea\weblogic92\platform\lib\p13n\p13n-schemas.jar;C:\bea\weblogic92\platform\lib\p13n\p13n_common.jar;C:\bea\weblogic92\platform\lib\p13n\p13n_system.jar;C:\bea\weblogic92\platform\lib\wlp\commerce_system.jar;C:\bea\weblogic92\platform\lib\wlp\content_system.jar;C:\bea\weblogic92\platform\lib\wlp\groupspace_system.jar;C:\bea\weblogic92\platform\lib\wlp\netuix_common.jar;C:\bea\weblogic92\platform\lib\wlp\netuix_schemas.jar;C:\bea\weblogic92\platform\lib\wlp\netuix_system-full.jar;C:\bea\weblogic92\platform\lib\wlp\netuix_system.jar;C:\bea\weblogic92\platform\lib\wlp\nf-jspcmods.jar;C:\bea\weblogic92\platform\lib\wlp\nf-system.jar;C:\bea\weblogic92\platform\lib\wlp\wlp-schemas.jar;C:\bea\weblogic92\platform\lib\wlp\wps_system.jar;C:\bea\weblogic92\platform\lib\wlp\wsrp-client.jar;C:\bea\weblogic92\platform\lib\wlp\wsrp-common.jar>
<Mar 12, 2009 3:25:17 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.5.0_10-b03 from Sun Microsystems Inc.>
<Mar 12, 2009 3:25:17 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 MP2 Mon Jun 25 01:32:01 EDT 2007 952826 >
<Mar 12, 2009 3:25:20 PM EDT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : C:\bea\license.bea>
<Mar 12, 2009 3:25:20 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Mar 12, 2009 3:25:20 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Mar 12, 2009 3:25:20 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\user_projects\domains\MyDomain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
<Mar 12, 2009 3:25:21 PM EDT> <Notice> <Security> <BEA-090163> <The SAMLCredentialMapper provider did not import a duplicate LDAP entry: cn=rp_00001,ou=SAMLRelyingPartyRegistry,ou=myrealm,dc=MyDomain>
<Mar 12, 2009 3:25:23 PM EDT> <Error> <com.bea.weblogic.kernel> <000000> <[Security:090737]An exception occured while getting connection to validate the configuration settings
java.sql.SQLException: [Security:090735]The DBMS connection was not usable
at weblogic.security.providers.authentication.DBMSSQLAuthenticatorDelegateImpl.getManageableConnection(DBMSSQLAuthenticatorDelegateImpl.java:857)
at weblogic.security.providers.authentication.DBMSSQLAuthenticatorDelegateImpl.validateConfiguration(DBMSSQLAuthenticatorDelegateImpl.java:163)
at weblogic.security.providers.authentication.DBMSSQLAuthenticatorDelegateImpl.<init>(DBMSSQLAuthenticatorDelegateImpl.java:89)
at weblogic.security.providers.authentication.DBMSAuthenticatorDelegateImpl.getInstance(DBMSAuthenticatorDelegateImpl.java:445)
at weblogic.security.providers.authentication.DBMSSQLAuthenticationProviderImpl.initialize(DBMSSQLAuthenticationProviderImpl.java:52)
Truncated. see log file for complete stacktrace
>
<Mar 12, 2009 3:25:23 PM EDT> <Notice> <Security> <BEA-090163> <The SAMLIdentityAssertor provider did not import a duplicate LDAP entry: cn=type@E@Fremote@G:wsrpconsumer__81_COMPAT:0,ou=KeyPair,ou=ResourceMapping,ou=PKICredentialMap,ou=myrealm,dc=MyDomain>
<Mar 12, 2009 3:25:23 PM EDT> <Notice> <Security> <BEA-090163> <The SAMLIdentityAssertor provider did not import a duplicate LDAP entry: cn=ap_00001,ou=SAMLAssertingPartyRegistry,ou=myrealm,dc=MyDomain>
<Mar 12, 2009 3:25:23 PM EDT> <Notice> <Security> <BEA-090163> <The SAMLIdentityAssertor provider did not import a duplicate LDAP entry: cn=wsrpconsumerrsa,ou=SAMLCertificateRegistry,ou=myrealm,dc=MyDomain>
<Mar 12, 2009 3:25:24 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 12, 2009 3:25:26 PM EDT> <Error> <com.bea.weblogic.kernel> <000000> <[Security:090735]The DBMS connection was not usable>
<Mar 12, 2009 3:25:26 PM EDT> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
<Mar 12, 2009 3:25:26 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:941)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
>
<Mar 12, 2009 3:25:26 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Mar 12, 2009 3:25:26 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Mar 12, 2009 3:25:26 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

[Loyal Water]

Have you set the connector up to launch *specifically* with the JDK (not JRE) that is installed under the BEA home directory for WebLogic 9.2?

[gcamacho@sandp.com]

Thank you, Nipun.

I pointed it to C:\bea\jdk150_10 and it correctly determined that the JDK is jdk150_10.

Do you see the error message that says “The user name and/or password from the boot identity file (boot.properties) is not valid.”?

I can start/stop the app server fine outside of MyEclipse using the same UserName/Password for logging in to the Admin Server console.

I also checked that the policy file in the Admin Server log from the instance I started outside MyEclipse is exactly the same name as that in the MyEclipse configuration.

Would it help if I posted both logs, the good (started outside MyEclipse) and bad (server started within MyEclipse)?

[Loyal Water]

Your configuration looks fine. This is a weird issue. How are you running the server fro outside of MyEclipse? Are you using a shortcut? What is the working directory pointing to?

[gcamacho@sandp.com]

Outside MyEclipse, I’m running the standard startup script
C:\bea\user_projects\domains\MyDomain\bin\startWebLogic.cmd
which points to
C:\bea\user_projects\domains\MyDomain
as a working directory.

[gcamacho@sandp.com]

In case it helps, here are the full VM arguments:

Djava.library.path=C:/bea/jdk150_10/bin;C:/bea/jdk150_10/jre/bin;C:/bea/weblogic92/server/native/win/32;C:/bea/weblogic92/server/bin;C:/bea/weblogic92/server/native/win/32/oci920_8 -Djava.security.policy=C:/bea/weblogic92/server/lib/weblogic.policy -Dweblogic.management.discover=false -Dplatform.home=C:/bea/weblogic92 -Dwls.home=C:/bea/weblogic92/server -Dwli.home=C:/bea/weblogic92/integration -Dweblogic.Name=AdminServer -Dweblogic.management.username=weblogic -Dweblogic.management.password=weblogic -Dweblogic.ext.dirs=C:/bea/patch_weblogic901/profiles/default/sys_manifest_classpath/weblogic_patch.jar -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -da

I matched the policy to that noted in the log when I succesfully start BEA up outside MyEclipse and it is exactly the same.

I’m thinking of trying this in straight Eclipse and see if it works.

[Loyal Water]

This is a very strange issue. I’ll check with the dev team till you try the other options and let you know what they have to say.

[Author]

Posts