For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 6 replies, 3 voices, and was last updated 20 years, 7 months ago by
jeffo.
-
AuthorPosts
-
jeffoMemberI’m trying to start the Weblogic server via MyEclipse, and am getting a security exception that I am not sure how to get passed. Any thoughts as to what this means? Thanks
Jun 22, 2005 5:10:35 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_04-b05 from Sun Microsystems Inc.>
<Jun 22, 2005 5:10:37 PM PDT> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
<Jun 22, 2005 5:10:37 PM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic Portal 8.1 SP4 Tue Nov 30 10:31:06 PST 2004 471877>
<Jun 22, 2005 5:10:37 PM PDT> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at C:\vykor\vykor\base\domain\config.xml.>
<Jun 22, 2005 5:10:42 PM PDT> <Notice> <Log Management> <BEA-170019> <The server log file C:\vykor\vykor\base\domain\portalServer\portalServer.log is opened. All server side log events will be written to this file.>
<Jun 22, 2005 5:10:46 PM PDT> <Critical> <WebLogicServer> <BEA-000364> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:205)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
>
<Jun 22, 2005 5:10:46 PM PDT> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.>
***************************************************************************
The WebLogic Server did not start up properly.
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:205)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
at weblogic.Server.main(Server.java:32)
Reason: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
***************************************************************************June 28, 2005 at 11:12 am #231829
Riyad KallaMemberjeffo,
No idea. I would suggest a clean install of weblogic unless these custom security settings are necessary. Does it run from the command line correctly?June 28, 2005 at 11:37 am #231841
jeffoMemberYes, WL starts from the command line just fine. Its only through the MyEclipse interface that causes this. What custom security settings are you referring to? Thanks again.
June 28, 2005 at 11:39 am #231842
Riyad KallaMemberjeffo,
Our connectors are designed to start out-of-the-box default installs of every server, and my local copy of WL 8.1 spins up without a problem, so what I meant by custom was that it seems you have some custom settings somewhere in WL that are not being duplicate in the connector configuration, so it isn’t quite the same as when the startup script runs it.What are all your settings for all the values in your weblogic connector (including your JDK and Paths panels).
June 29, 2005 at 7:02 pm #231977
jeffoMemberIs there a way to dump all of this information to you?
Here’s the line used to start weblogic from the command line (pointing to the same domain directory):
C:\bea\JDK142~2\bin\java -server -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket
,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xmx1024m -XX:CompileThre
shold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea.
.. -da:javelin… -da:weblogic… -Dplatform.home=C:\bea\WEBLOG~1 -Dwls.home=C:\
bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.configuratio
n=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.management.disco
ver=true -Dweblogic.ProductionModeEnabled= -Dejbruntime.database=pointbase44 -Dw
eblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.te
stConsole=true -Dwlw.logErrorsToConsole=true -Dmedia.physical.path=C:\vykor\vyko
r/base/domain/mediastore -Drequire.ssl=false -Drules.home=C:\vykor\vykor/rules/d
eploySupplierMapping -Dvykor.home=C:\vykor\vykor -Dweblogic.Name=portalServer -D
weblogic.ProductionModeEnabled= -Djava.security.policy=C:\bea\WEBLOG~1\server\li
b\weblogic.policy -Dp6.home=C:\vykor\vykor\base\domain weblogic.Server
<Jun 29, 2005 4:40:18 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting Web
Logic Server with Java HotSpot(TM) Server VM Version 1.4.2_05-b04 from Sun Micro
systems Inc.>June 29, 2005 at 8:16 pm #231980
Scott AndersonParticipantJeffo,
Excellent. So you’re starting WebLogic portal, not WebLogic server. Then there are several things you’ll need to add. Several of those settings need to be set in the WebLogic connector in MyEclipse since they are additions to a default installation. At first glance, these look like ones you need to add to the connectors Paths or JDK pages:
-ea da:com.bea... -da:javelin... -da:weblogic... -Dejbruntime.database=pointbase44 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dmedia.physical.path=C:\vykor\vykor/base/domain/mediastore -Drequire.ssl=false -Drules.home=C:\vykor\vykor/rules/deploySupplierMapping -Dvykor.home=C:\vykor\vykorAlso, on the main weblogic connector page, be sure you specify the Java security policy file to C:\bea\WEBLOG~1\server\lib\weblogic.policy as you’ve done above. And, you’ll likely need to add several additional jars to the classpath, since none of the portal jars will be included by default.
While we don’t specifically support the portal server, many users have gotten it working with additional configuration. You can search the forums for ‘Weblogic and Portal’ and find lots of links. Here are a few that seemed helpful:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-92-highlight-weblogic+portal.htmlAnother way to go would be to start WebLogic using the script, not the connector, and use our Remote Debugging Facility to connect to port 8453 and debug remotely. The debug capabilities are the same as if you started with our connector and it might be easier for you. You can find out about remote debugging in the quickstart here: http://myeclipseide.com/enterpriseworkbench/help/index.jsp?topic=/com.genuitec.myeclipse.doc/html/quickstarts/remotedebugging/index.html
July 6, 2005 at 4:31 pm #232424
jeffoMemberOk, I tried all the parameters and still had issues, so I am going to use the remote debugging method. Thanks for your help
-
AuthorPosts
