Authentication problem in starting WLS 6.1 in JBuilder 4

Hi,
When i start weblogic server in JBuilder4, without
-Dweblogic.management.password option or the option set to some arbitrary value,
the server fails to start (as expected) but it does not stop for me to enter the
password.
The same command (with java in place of javaw) runs okay in command prompt.
Is there anything i'm missing here?
C:\JBuilder4\jdk1.3\bin\javaw -classic -classpath "C:\p4\tarkeshwar\product\code\java;C:\bea\wlserver6.1\lib\weblogic.jar;C:\JBuilder4\jdk1.3\demo\jfc\Java2D\Java2Demo.jar;C:\JBuilder4\jdk1.3\jre\lib\i18n.jar;C:\JBuilder4\jdk1.3\jre\lib\jaws.jar;C:\JBuilder4\jdk1.3\jre\lib\rt.jar;C:\JBuilder4\jdk1.3\jre\lib\sunrsasign.jar;C:\JBuilder4\jdk1.3\lib\dt.jar;C:\JBuilder4\jdk1.3\lib\tools.jar"
-Dweblogic.Domain=tavantdomain -Dbea.home=c:/bea -Dweblogic.Name=myserver -Dweblogic.RootDirectory=C:/
weblogic.Server
<Oct 30, 2001 3:36:10 PM PST> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
<Oct 30, 2001 3:36:12 PM PST> <Notice> <Management> <Loading configuration file
C:\config\tavantdomain\config.xml ...>
<Oct 30, 2001 3:36:17 PM PST> <Info> <Logging> <FileLogger Opened.>
<Oct 30, 2001 3:36:22 PM PST> <Emergency> <Security> <Authentication failure -
reenter password to boot weblogic server:>
<Oct 30, 2001 3:36:22 PM PST> <Emergency> <Security> <Authentication failure -
reenter password to boot weblogic server:>
<Oct 30, 2001 3:36:22 PM PST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system denied
java.lang.SecurityException: Authentication for user system denied
 at weblogic.security.SecurityService.initializeSuid(SecurityService.java:375)
 at weblogic.security.SecurityService.initialize(SecurityService.java:118)
 at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
 at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.SecurityException: Authentication for user system
denied
java.lang.SecurityException: Authentication for user system denied
 at weblogic.security.SecurityService.initializeSuid(SecurityService.java:375)
 at weblogic.security.SecurityService.initialize(SecurityService.java:118)
 at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
 at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
-Tarkeshwar

Similar Messages

Problem with start WLS

Peace!
I'm developing servlets that invoke ejb object under WLE.
I include in classpath for starting WLS 4 jar in udataobj of WLE.
When I try to start server there are problem and it doesn't start.
What do I include to run a client of EJB?
PS: I think that there are conflict problem between WLE classes and WLS
classes.
Thanks.

Giuseppe -
Are you using WLE 5.1? If no, I'd recommend you upgrade.
WLE 5.1 includes examples of how to access EJBs on the T-Engine from the
J-Engine, or WLS, and addresses some issues you may be encountering.
Will
Giuseppe Villanova wrote:
Peace!
I'm developing servlets that invoke ejb object under WLE.
I include in classpath for starting WLS 4 jar in udataobj of WLE.
When I try to start server there are problem and it doesn't start.
What do I include to run a client of EJB?
PS: I think that there are conflict problem between WLE classes and WLS
classes.
Thanks.

Authentication errors upon starting WLS 8.1 Admin server...

Please excuse my ignorance as I am far from a WL Admin. I have been working on a problem that has been preventing my admin server from starting for the past couple of days now and haven't a clue as to what could be causing it. The admin server fails to start and when I check the error logs this is all that I see: 
The WebLogic Server did not start up properly.
Reason: weblogic.security.SecurityInitializationException: Authentication for user system denied 
Frustrating because it does not say what the problem is and when I spoke with the actual WL admin that set it up he did not seem to know either. He doesn't have a lot of time to spend looking into the problem right now because he is in the middle of another project and this is not a production issue because it is on a development server but it's where I have to do my testing so I have to get it back up. I did not configure it but do have complete access to whatever files I need to change I just don't know what I am supposed to do. He tells me that I need to do some research on the problem so here I am. If anyone has any suggestions on what I can do to even begin fixing the problem it would be much appreciated. Thanks, 
Jon

It does tell you why the server won't start:
"Authentication for user system denied"
Thus, your boot identity (which is "system") can't be authenticated for some reason. It could be a bad password, improper configuration such that it can't find that user, or a missing user account.
The other post talks about these things.
An easy test for eliminating improper configuration is to copy config.xml to a safe place and then copy (or simply rename) config.xml.booted to config.xml. Then try to start the server.
If it still won't start you have one of the other two problems. Likewise, if it does start, you have a configuration problem.
Mike
Weblogic/J2EE Security Blog: http://monduke.com

Taglib parsing problems when starting WLS 5.1 with user and region properties set to Turkish

Hi,
We are building an application for the Turkish market and we developed
custom tags to translate static text on JSP pages.
When WLS 5.1 is started with -Duser.region=TR and -Duser.language=tr, the
compilation of the pages doesn't work.
In fact, WL try to access a class called weblogic.servlet.jsp.stdtag.0nfo
which can't be found.
Turkish language has two kinds of 'i' letter and I have the impression that
weblogic is convering the I of info into another caracter and that it tries
to load the class with that specail caracter.
Does anyone has seen this already and what could we do to fix this problem ?
Thanks

Hi,
We are building an application for the Turkish market and we developed
custom tags to translate static text on JSP pages.
When WLS 5.1 is started with -Duser.region=TR and -Duser.language=tr, the
compilation of the pages doesn't work.
In fact, WL try to access a class called weblogic.servlet.jsp.stdtag.0nfo
which can't be found.
Turkish language has two kinds of 'i' letter and I have the impression that
weblogic is convering the I of info into another caracter and that it tries
to load the class with that specail caracter.
Does anyone has seen this already and what could we do to fix this problem ?
Thanks

Problem in starting WLS [Security:090300]

Having sold the previous issue Unable to start WebLogic Server 12.1.3.0.0 I still can't startup WLS.
the log is:
SOA Platform is running and accepting requests
2015-03-03T21:37:46.686+04:00] [AdminServer] [NOTIFICATION] [] [oracle.soa.mediator.dispatch.db] [tid: DaemonWorkThread: '4' of WorkManager: 'wm/SOAWorkManager'] [userId: <anonymous>] [ecid: af825e85-00cc-4170-92b6-15c5c888edef-00000003,0:1968] [APP: soa-infra] waiting for delay period to get over2015-03-03 21:37:46.686 Server start time was 2015-03-03 21:34:46.532 delay was 60000 current difference=180154
[2015-03-03T21:37:46.687+04:00] [AdminServer] [NOTIFICATION] [] [oracle.soa.mediator.dispatch.db] [tid: DaemonWorkThread: '4' of WorkManager: 'wm/SOAWorkManager'] [userId: <anonymous>] [ecid: af825e85-00cc-4170-92b6-15c5c888edef-00000003,0:1968] [APP: soa-infra] firstCleanupAttempt set to false
[2015-03-03T21:38:29.826+04:00] [AdminServer] [ERROR] [WSM-02353] [oracle.wsm.resources.policymanager] [tid: [ACTIVE].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: af825e85-00cc-4170-92b6-15c5c888edef-0000006c,0] [APP: wsm-pm] Unable to get the Action Executor due to "javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User OracleSystemUser javax.security.auth.login.LoginException: [Security:090300]Identity Assertion Failed: User OracleSystemUser does not exist".
I've already tried to stop the server and write in boot.properties username/password as a plain text but it doesn't help.
Any suggestions?
Thanks in advance!

Hello,
Please check the existence of user 'OracleSystemUser' in your WL security provider.
From admin console > security realms > my realm > users and groups > users .. then check if the user exists. If not, try manually creating it.
I remember facing a similar issue with SOA before .. I don't remember if further steps is needed, but lets start by creating the user.
Regards,
Mohab

Authentication problem by external ldap server for WLS 7.0

Hi all,
I have configured iPlanet directory Server to serve as authentication security
provider for WLS 7.0.While doing so I have created a Test security realm and made
it as default.I have also configured the other default settings for the remaining
security providers for the realm.
Now, while I start the WLS with the default username and password, boot-error
comes as given below. As a matter of fact I have also created groups with relevant
username and pwd in the ldap server as specified bu the Bea documentation.
I have tried to remove the problem since last 4 days but all in fiasco.
If anybody has any pointer to the problem - it will be a great help.
The error :
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
D:\bea\weblogic700\samples\server\config\petstore>"D:\bea\jdk131_03\bin\java"
-h
otspot -Xms32m -Xmx200m -Dpet.mode= - Dweblogic.management.discover=false -Dweblo
gic.Name=petstoreServer -Dbea.home="D:\bea" -Dweblogic.management.username=weblo
gic -Dweblogic.management.password=weblogic -Dweblogic.ProductionModeEnabled=tru
e -Djava.security.manager -Djava.security.policy=="D:\bea\weblogic700\server\lib
\weblogic.policy" weblogic.Server
Starting WebLogic Server...
<Nov 19, 2002 10:08:04 AM IST> <Notice> <Management> <140005> <Loading configura
tion D:\bea\weblogic700\samples\server\config\petstore\.\config.xml>
<Nov 19, 2002 10:08:21 AM IST> <Notice> <Security> <090082> <Security initializi
ng using realm RitTestRealm.>
<Nov 19, 2002 10:08:22 AM IST> <Critical> <WebLogicServer> <000364> <Server fail
ed during initialization. Exception:java.lang.SecurityException: User weblogic
i
s not permitted to boot the server
java.lang.SecurityException: User weblogic is not permitted to boot the server
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1076)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
Regards,
Ritwik

Thanks Vijay - it has worked by creating the Administrator group in LDAP but Weblogic
documentation also states the creation of any group in Ldap server with the boot
username and pwd and then adding the group in the admin role of WLS7.0 - but this
did not work.
If there is any info regarding the same - pl. do let me know
Regards,
Ritwik
"Vijay" <[email protected]> wrote:
>
Ritwik,
I think WebLogic 7 requires a group called "Administrators" in the LDAP
server
and requires an user to be added to that group. I have this working in
one of
my projects. The group really doesnt need to be an LDAP administrative
group.
Can you provide any additional information. I might be able to help since
I got
this working only a coupla days back.
Vijay
"Ritwik Batabyal" <[email protected]> wrote:
Hi all,
I have configured iPlanet directory Server to serve as authentication
security
provider for WLS 7.0.While doing so I have created a Test security realm
and made
it as default.I have also configured the other default settings forthe
remaining
security providers for the realm.
Now, while I start the WLS with the default username and password, boot-error
comes as given below. As a matter of fact I have also created groups
with relevant
username and pwd in the ldap server as specified bu the Bea documentation.
I have tried to remove the problem since last 4 days but all in fiasco.
If anybody has any pointer to the problem - it will be a great help.
The error :
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
D:\bea\weblogic700\samples\server\config\petstore>"D:\bea\jdk131_03\bin\java"
-h
otspot -Xms32m -Xmx200m -Dpet.mode= - Dweblogic.management.discover=false
-Dweblo
gic.Name=petstoreServer -Dbea.home="D:\bea" -Dweblogic.management.username=weblo
gic -Dweblogic.management.password=weblogic -Dweblogic.ProductionModeEnabled=tru
e -Djava.security.manager -Djava.security.policy=="D:\bea\weblogic700\server\lib
\weblogic.policy" weblogic.Server
Starting WebLogic Server...
<Nov 19, 2002 10:08:04 AM IST> <Notice> <Management> <140005> <Loading
configura
tion D:\bea\weblogic700\samples\server\config\petstore\.\config.xml>
<Nov 19, 2002 10:08:21 AM IST> <Notice> <Security> <090082> <Security
initializi
ng using realm RitTestRealm.>
<Nov 19, 2002 10:08:22 AM IST> <Critical> <WebLogicServer> <000364><Server
fail
ed during initialization. Exception:java.lang.SecurityException: User
weblogic
i
s not permitted to boot the server
java.lang.SecurityException: User weblogic is not permitted to bootthe
server
at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
SecurityServiceManager.java:1076)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1116)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
at weblogic.Server.main(Server.java:31)
>
Regards,
Ritwik

Problems starting WLS on XP - Unable to bind to port

Hi
I recently changed my development environment from W2000 to XP.
Apparently everything works as before.
However, when I start WLS again shortly after stopping it (either by console or
CTRL^C) I get the following error
<01-10-2003 14:48:40 CEST> <Emergency> <WebLogicServer> <BEA-000351> <Unable to
create a server socket on Channel Default for port: 28041. j
ava.net.BindException: Address in use Perhaps another process is using port 28041.>
<01-10-2003 14:48:40 CEST> <Emergency> <Security> <BEA-090085> <Server failed
to bind to the configured port. The port may already be used b
y another process.>
<01-10-2003 14:48:40 CEST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to
initialize the server: Server failed to bind to the requeste
d port. See preceeding log message for details.>
This situation times out after an unpredictable delay (5-20 min) - and I can restart
my WLS.
Does anybody know how to resolve this problem.
Regards
Peter

Hi Werner,
SYSLOG is UDP port 514. Normally this means that some other program is running and using port 514.
Some of the TFTP servers are also SYSLOG servers and will "listen" on this port.
You can see if port 514 is listening with Fabric Manager not running.
To find out what is using port 514:
(a) Open a command prompt window. From Start / Run enter: cmd
(b) From the command prompt enter: netstat -ano
(c) Note the PID (process identifier) associated with the ports you are concerned about. (Also note the Local Address, Foreign Address, Protocol and State.)
(d) Then do ctrl-alt-del to bring up the Windows Task Manager.
(e) In Windows Task Manager, select the Processes tab.
(f) Look for the PID you noted when you did the netstat in step (c). Look to left to the image name and that tells you which process has that PID.
- If you dont see a PID column, click on View / Select Columns. Make sure PID is selected. Click OK.
- Make sure Show processes from all users is selected.
Now you can see what process is using port 514. FM would be listed as javaw.exe ( java exec without a console window ).
Best regards,
Jim

Problem Starting WLS 5.1 from windows 2000 program group

Hi
I couldn't able to start Weblogic server 5.1 from windows 2000 program
group(start > Programs > Weblogic 5.10 > Weblogic Server). I can start WLS
without any problem from the console . I've check every configuration and
environment setting, the problem still come out. Whenever I start WLS from
program group , a window dialog with error messages will come out , here's
the error messages :
wlserver.exe - Application Error
The instruction at "0x04d5d0d6" referenced memory at
"0x00000000". The memory could not be "written".
Click on OK to terminate the program
Click on CANCEL to debug the program
Any suggestions/solution will be appreciated .
Thanks
Chew Leong
[email protected]

look for weblogic.system.password property in your weblogic.properties
file and see what's in there.
Shailesh Mungikar wrote:
I am trying to install WLS 5.1 SP12 on my Windows 2000 machine.
I have WLS 6.1 already installed my PC.
When I try to install, at the very end when
"System" password required
dialog pops up, I get another dialog box saying
WLPASS~1.exe Application Error
The exception Floating point division by zero (0xc000008e) occured in
the application at location 0x50147c14
When I press OK, it kill the "System password" dialog.
The installation seems to be complete.
If I go ahead and try to start weblogic, I get Exceptio
java.security.AccessControlException: access denied
(java.lang.RuntimePermission createSecurityManager)
Any solution/workaround?
thanks,
_shailesh

Problem using integrated WLS in jDeveloper 11.1.2.1.0

Hey there,
I got a problem using the integrated WLS from the jDeveloper 11.1.2.1.0.
After trying to deploy an ADF Web Application on the integrated WLS, I get the following log message:
LOG
+[Waiting for the domain to finish building...]+
+[11:26:04 AM] Creating Integrated Weblogic domain...+
+[11:28:13 AM] Extending Integrated Weblogic domain...+
+[11:30:06 AM] Integrated Weblogic domain processing completed successfully.+
*** Using HTTP port 7101 ***
*** Using SSL port 7102 ***
+/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/bin/startWebLogic.sh+
+[waiting for the server to complete its initialization...]+
+.+
+.+
JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
+.+
WLS Start Mode=Development
+.+
CLASSPATH=/home/robin/bin/wls/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/home/robin/bin/wls/patch_wls1211/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/patch_oepe100/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/jdk160_29/lib/tools.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic_sp.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic.jar:/home/robin/bin/wls/modules/features/weblogic.server.modules_12.1.1.0.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/webservices.jar:/home/robin/bin/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/robin/bin/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/robin/bin/wls/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/home/robin/bin/wls/wlserver_12.1/common/derby/lib/derbyclient.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/xqrl.jar
+.+
PATH=/home/robin/bin/wls/wlserver_12.1/server/bin:/home/robin/bin/wls/modules/org.apache.ant_1.7.1/bin:/home/robin/bin/wls/jdk160_29/jre/bin:/home/robin/bin/wls/jdk160_29/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3:/usr/games/bin
+.+
+* To start WebLogic Server, use a username and *+
+* password assigned to an admin-level user. For *+
+* server administration, use the WebLogic Server *+
+* console at http://hostname:port/console *+
starting weblogic with Java version:
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) Client VM (build 20.4-b02, mixed mode)
Starting WLS with line:
+/home/robin/bin/wls/jdk160_29/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic.policy -Djavax.net.ssl.trustStore=/tmp/trustStore7618453572230021232.jks -Dhttp.proxyHost=emea-proxy.uk.oracle.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|localhost.localdomain|127.0.0.1|::1|MUELLER-BADY-GENTOO|MUELLER-BADY-GENTOO -Dhttps.proxyHost=emea-proxy.uk.oracle.com -Dhttps.proxyPort=80 -Doracle.jdeveloper.adrs=true -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -Djava.endorsed.dirs=/home/robin/bin/wls/jdk160_29/jre/lib/endorsed:/home/robin/bin/wls/wlserver_12.1/endorsed -da -Dplatform.home=/home/robin/bin/wls/wlserver_12.1 -Dwls.home=/home/robin/bin/wls/wlserver_12.1/server -Dweblogic.home=/home/robin/bin/wls/wlserver_12.1/server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=/home/robin/bin/wls/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain -Djrockit.optfile=/home/robin/bin/wls/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/servers/DefaultServer -Doracle.domain.config.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig -Digf.arisidbeans.carmlloc=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/carml -Digf.arisidstack.home=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/servers/DefaultServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/home/robin/bin/wls/oracle_common/modules/oracle.ossoiap_11.1.1,/home/robin/bin/wls/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/oracle/store/gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/robin/bin/wls/patch_wls1211/profiles/default/sysext_manifest_classpath:/home/robin/bin/wls/patch_oepe100/profiles/default/sysext_manifest_classpath:/home/robin/bin/wls/patch_ocp371/profiles/default/sysext_manifest_classpath weblogic.Server+
+<Feb 10, 2012 11:30:09 AM CET> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>+
+<Feb 10, 2012 11:30:10 AM CET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>+
+<Feb 10, 2012 11:30:11 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 20.4-b02 from Sun Microsystems Inc..>+
+<Feb 10, 2012 11:30:12 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.1.1.0 Wed Dec 7 08:40:57 PST 2011 1445491 >+
+<Feb 10, 2012 11:30:15 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>+
+<Feb 10, 2012 11:30:15 AM CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>+
+<Feb 10, 2012 11:30:15 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file /home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/servers/DefaultServer/logs/DefaultServer.log is opened. All server side log events will be written to this file.>+
Feb 10, 2012 11:30:24 AM oracle.security.jps.internal.keystore.file.FileKeyStoreManager saveKeyStore
WARNING: Failed to save farm keystore. Reason {0}
Feb 10, 2012 11:30:24 AM oracle.security.jps.internal.keystore.file.FileKeyStoreManager createKeyStore
WARNING: Failed to save farm keystore. Reason {0}
oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06513: Failed to save farm keystore. Reason
+ at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.createKeyStore(FileKeyStoreManager.java:309)+
+ at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:95)+
+ at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:73)+
+ at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:63)+
+ at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)+
+ at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:64)+
+ at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)+
+ at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)+
+ at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)+
+ at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)+
+ at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)+
+ at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:850)+
+ at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)+
+ at java.security.AccessController.doPrivileged(Native Method)+
+ at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
+ at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
+ at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
+ at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
+ at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
+ at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
+ at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)+
+ at java.lang.reflect.Constructor.newInstance(Constructor.java:513)+
+ at java.lang.Class.newInstance0(Class.java:355)+
+ at java.lang.Class.newInstance(Class.java:308)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1343)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)+
+ at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)+
+ at weblogic.security.SecurityService.start(SecurityService.java:148)+
+ at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
+ at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)+
+ at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)+
+<Feb 10, 2012 11:30:24 AM CET> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider>+
+<Feb 10, 2012 11:30:24 AM CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
+weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)+
+ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)+
+ at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)+
+ at weblogic.security.SecurityService.start(SecurityService.java:148)+
+ at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
+ Truncated. see log file for complete stacktrace+
+Caused By: oracle.security.jps.JpsRuntimeException: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
+ at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:293)+
+ at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
+ at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
+ at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
+ at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
+ Truncated. see log file for complete stacktrace+
+Caused By: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
+ at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:899)+
+ at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
+ at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
+ at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
+ at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
+ Truncated. see log file for complete stacktrace+
+Caused By: java.security.PrivilegedActionException: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!+
+ at java.security.AccessController.doPrivileged(Native Method)+
+ at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
+ at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
+ at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
+ at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
+ Truncated. see log file for complete stacktrace+
+Caused By: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!+
+ at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:860)+
+ at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)+
+ at java.security.AccessController.doPrivileged(Native Method)+
+ at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
+ at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
+ Truncated. see log file for complete stacktrace+
Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06513: Failed to save farm keystore. Reason
+ at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.createKeyStore(FileKeyStoreManager.java:309)+
+ at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:95)+
+ at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:73)+
+ at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:63)+
+ at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)+
+ Truncated. see log file for complete stacktrace+
+>+
+<Feb 10, 2012 11:30:24 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>+
+<Feb 10, 2012 11:30:24 AM CET> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>+
+<Feb 10, 2012 11:30:24 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>+
Process exited.
*/LOG*
After that, I tried setting permissions for the cwallet.sso file to ugo+rwx, but this leads to the same problems as mentioned above.
My second try was to setup an external WLS 12c, but it seems to be not yet possible to connect to a WLS 12c from within jDeveloper.
Do you have any ideas ?
Thank you in advance for your help.
Regards,
Robin

After debugging the WLS Initialisation with jdb, I recognized that there was some trouble with dependent libraries.
In the end, I solved my problem by using another OS (Ubuntu 11.10) for development. There, the WLS works out of the box, even with 64-Bit libraries.
Thank you for your help.
Regards,
Robin

802.1x re authentication problem

Hello,
I have problem with 802.1x authentication on switch ports which are configured in "Multi Session" mode. In Single host mode and Multiple Host mode it works just fine.
The problem is following, when PC is first connected on switch port it authenticates successfully. After about 1-2 minutes windows 7 NIC notifies that its going to authenticate again, and after couple of minutes NIC status is changed to “Authentication Failed”. On ACS I only see first authentication request which is successful. If I unplug PC from port and plug it again. It authenticates successfully and then starts again with same problems.
I was doing packet sniffing on PC, and it seems that after pc first authentication completes successful, switch starting to sent EAP Identity/Request packets to host, for that host is sending EAP Identity/Response to switch, but switch don’t continues authentication process and starts again with new EAP Identity/Request packets.
On Windows 7 host Event viewer I see following log messages:
                Reason: 0x70004
                Reason Text: The network stopped answering authentication requests
                Error Code: 0x0
The ACS version is 5.3. Authentication method is PEAP. Supplicant OS is Windows 7 I also trued with Windows XP, with same result. The Authentication switch is ESW 520 with latest firmware. I also trued with 2960/3560 switches and it works perfectly. On ESW 520 switch if port mode is other than “Multi Session" if works without any issue.
Do you have any Idea how can i fix this ?

Hi ngtransge,
Thanks for rating the replies. You need to select "User Authentication". I am pasting some screenshots which might help you out.

Problem in starting weblogic server as proxy

I am using weblogic server as Proxy to forward the requests to weblogic cluster.
When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
I am Pasting my complete logs below.
Setting JVM memory params for server IRISProxy
Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
WLS Production Mode=true
./startWebLogic.sh[68]: B: not found.
maxfiles=8192
CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.4.1.05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
Starting WLS with line:
/home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
Bad level value for property: com.iplanet.services.debug.level
Bad level value for property: com.sun.identity.agents.logging.level
Bad level value for property: com.sun.am.policy.amFilter.audit.level
<Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
<Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
<Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
 at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
 at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
 at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
 at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
Can someone help me in solving this problem
Thanks
Kris

I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
WebLogic Temporary Patch for CR211812
WebLogic Temporary Patch for CR235145
Once i commented the above patches in the CLASSPATH.
The issue is resolved.

Problem in starting the weblogic server

HI friends,
I have a problem running the weblogic server, i am getting error as follows:
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
Starting WLS with line:
C:\bea\JDK142~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -
XX:PermSize=32m -XX:MaxPermSize=128m -Djrockit.codegen.optpriority=1 -Xverify:
none -Xverify:none -da -Dplatform.home=D:\bea\WEBLOG~1 -Dwls.home=D:\bea\WEBLOG
~1\server -Dwli.home=D:\bea\WEBLOG~1\integration -Dweblogic.management.discover
=true -Dweblogic.ProductionModeEnabled= -Dwlw.iterativeDev= -Dwlw.testConsole=
-Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\bea\patch_weblogic901\profiles\
default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.po
licy=D:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
The WebLogic Server encountered a critical failure
Exception in thread "main" java.lang.NoClassDefFoundError
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:174)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:372)
at weblogic.Server.main(Server.java:66)
So plz suggest me.
Regrads
Abhi007

Hi,
NoClassDefFoundError signifies that there is a classpath problem.
May be you are missing some critical jars in your classpath
for ex. weblogic.jar, jdk's rt.jar or something else.
You need to find this out.
HTH
VJ

Error while starting WLS server

Hi,
Am getting the below error
starting weblogic with Java version:
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_2\bin\java -client -Xms256m -Xmx512m -XX:CompileThr
eshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Dweblogic.Name=myserver -Dja
<Jun 14, 2012 5:26:19 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Jun 14, 2012 5:26:19 PM IST> <Critical> <WebLogicServer> <BEA-000362>
<Server f ailed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.IllegalArgumentException: The provider Provider already exists>
<Jun 14, 2012 5:26:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FAILED>
<Jun 14, 2012 5:26:19 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 14, 2012 5:26:19 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to FORCE_SHUTTING_DOWN>
This is very urgent and I need help to solve this.
Please reply back soon

this is the config.xml
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>mydomain</name>
<domain-version>10.3.6.0</domain-version>
<security-configuration>
<name>mydomain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}DO7UStBZljQz8xV6biUOFJqdK5gsj1D1riTUGbO7Il4FWYqlhurBQqPIDqAINVjswiUuNnqW6Fgh0Q5w4DUkQRmdVVHObsY/RXP7geTmt3Ps3eW3s/ucrlxdMYGzv8Y/</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}+mvIGJfWsqWkZekqkwYV6gc9tsY7DPmRWa/avipt80U=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>myserver</name>
<listen-address></listen-address>
</server>
<embedded-ldap>
<name>mydomain</name>
<credential-encrypted>{AES}yVDi5dwjQzQyCxCHXqjB4h3brKgkcLEgHP/3nu0yf81UC/t27TfkQuFjKl8cxm7r</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.6.0</configuration-version>
<app-deployment>
<name>demantra_new2</name>
<target>myserver</target>
<module-type>war</module-type>
<source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\demantra_new2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>demantra_JUNE14</name>
<target>myserver</target>
<module-type>war</module-type>
<source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\demantra_JUNE14.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<library>
<name>api</name>
<target>myserver</target>
<module-type xsi:nil="true"></module-type>
<source-path>C:\Oracle\Middlewareforweblogic\wlserver_10.3\server\lib\api.jar</source-path>
<deployment-principal-name>api</deployment-principal-name>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>javax.servlet.jsp.jstl#[email protected]</name>
<target>myserver</target>
<module-type xsi:nil="true"></module-type>
<source-path>D:\Oracle_Demantra_Spectrum_122\Collaborator\Tomcat\lib\jstl-1.2.jar</source-path>
<deployment-principal-name>jstl</deployment-principal-name>
<security-dd-model>DDOnly</security-dd-model>
</library>
<library>
<name>jstl#[email protected]</name>
<target>myserver</target>
<module-type>war</module-type>
<source-path>C:\Oracle\Middlewareforweblogic\wlserver_10.3\common\deployable-libraries\jstl-1.2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
</library>
<admin-server-name>myserver</admin-server-name>
<jdbc-system-resource>
<name>JDBC Data Source-0</name>
<target>myserver</target>
<descriptor-file-name>jdbc/JDBC_Data_Source-0-3407-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>
Edited by: Manikanda Prabhu on Jun 14, 2012 5:03 AM

Problem while starting Weblogic 7.0..please help

Hi,
Im facing this problem while starting the weblogic.
Below is the error i get...
<Nov 3, 2006 6:11:29 PM IST> <Alert> <WebLogicServer> <000297> <Inconsistent security configuration, java.lang.Exception: Certificate expired or not yet valid:
fingerprint = a48264011b8f3aeb13f64147821dc941, not before = Sat Nov 02 01:32:23 IST 2002, not after = Mon Oct 16 01:32:23 IST 2006, holder = C=US SP=California
L=San Francisco O=BEA WebLogic CN=weblogic.bea.com [email protected] , issuer = C=US SP=California L=San Francisco O=BEA WebLogic OU=Security CN=Demo Certi
ficate Authority Constraints [email protected] , key = modulus length=65, exponent length=3>
java.lang.Exception: Certificate expired or not yet valid: fingerprint = a48264011b8f3aeb13f64147821dc941, not before = Sat Nov 02 01:32:23 IST 2002, not after
= Mon Oct 16 01:32:23 IST 2006, holder = C=US SP=California L=San Francisco O=BEA WebLogic CN=weblogic.bea.com [email protected] , issuer = C=US SP=California L=San Francisco O=BEA WebLogic OU=Security CN=Demo Certificate Authority Constraints [email protected] , key = modulus length=65, exponent length=3 at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:219)
at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:122)
at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:1556)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:891)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)
<Nov 3, 2006 6:11:29 PM IST> <Emergency> <Security> <090034> <Not listening for SSL, java.io.IOException: Inconsistent security configuration, Certificate expir
ed or not yet valid: fingerprint = a48264011b8f3aeb13f64147821dc941, not before
= Sat Nov 02 01:32:23 IST 2002, not after = Mon Oct 16 01:32:23 IST 2006, holder = C=US SP=California L=San Francisco O=BEA WebLogic CN=weblogic.bea.com Email=s
[email protected] , issuer = C=US SP=California L=San Francisco O=BEA WebLogic OU=Security CN=Demo Certificate Authority Constraints [email protected] , key =
modulus length=65, exponent length=3.>
I have updated my license.bea file also. the date of expiration="2006-12-02" ..
Please suggest as to how to proceed
Thanks and Regards
SmitaUdupa

Your server certificate expired. You need to update your identity keystore with a new certificate.
The expired certificate was issued by the demo BEA certificate authority (CA). These certs are not adequate for production but if you want to take this approach for your new cert you'll have to use the BEA CertGen utility. Have a look at http://edocs.bea.com/wls/docs70/secmanage/ssl.html for more details.
Your other option is to use Java's keytool utility to create a private key. You'd then generate a certificate signing request (CSR) that you'd send to a CA such as Verisign. You might even have a CA in-house. The CA will then send you a signed certificate that you load in your keystore. Assuming you've configured WebLogic to use this keystore you should be back in business with SSL.
Mike
Weblogic/J2EE Security Blog: http://monduke.com

Authentication problem - solved, but maybe a bug in Mac OS X?

Hi,
I've a rather small installation with only a handful of users configured on a Mac mini (Mac OS X Server, 10.6.8). All of them use the mail, calendar and addressbook server on the Mac, nothing more. They use it with Mac, iPhone and iPad. Everything worked fine for months but suddenly all of them were faced authentication problems: it was not possible to login on the imap server, the calendar server, the addressbook server. It was possible to login using the admin account on the server directly. Moreover, all users disappeared from the workgroup manager, however they still were available on the servers LDAP server and findable using ldapsearch.
First, I used to completely restart the server to solve the problem, but it reappeared after only few hours again.
Second, after understanding more about the authentication process, I found the "killall DirectoryService" was sufficient to solve the problem, but it still reappeared after few hours.
Then I found the, once the problem occured, there was nearly no more communication to the local LDAP server on port 389 on localhost. When everything was working fine, the was a lot of such communication, including queries for usernames, when a login attempt was made. I started a "tcpdump -n -i lo0 port 389" and waited for the problem again. After the problem occured, I found in the pcap files that there were a few final query attempts, actually attempts the open a port 389 TCP connection to the slapd running on localhost, which were answered with a TCP RST. Then, no more attempts were made until l restarted the DirectoryService. Using the logfile of the slapd I found that this happened exactly at the time the slapd was stopped and restarted. And - surprisingly for me - stopping and restarting the slapd happened exactly once an hour.
I then found that it happened exactly at the time the time machine backup process was started and indeed it was possible to trigger the event of restarting the slapd by manually starting a time machine backup.
(Indeed, I switched my backup strategy from SuperDuper to time machine the other day and maybe that was the time the problem occured for the first time. I know that time machine is not considered as the best backup strategy for a server but I wanted to try on my own.)
Google helped my to find a hint that time machine will actually stop and restart slapd - which is a generally a good idea, since otherwise a backup from some open database files would be made, which could work but may fail. So, I thing, someone of the developers thought about that problem too and has considered time machine for backups of a server.
However, a not running slapd can not answer queries from a DirectoryService and a stopping or starting process might indeed end up with TCP SYNs answered with TCP RST.
My solution was to disable time machine again and from that time the problem does not occur again.
I'm wondering why the DirectoryService process isn't starting to query the slapd again after a failed connection. Isn't this a bug? After this experience I consider time machine as not only the not preferred backup solution for a server but as completely incompatible with Mac OS X server - although, as I said, it seems that someone thought about backing up the LDAP database using time machine.
(On a Lion server this problem does not occur, the slapd will not be stopped and restarted when time machine is running. Moreover, I saw a com.apple.slapd.start notification in the slapd.log ... maybe this tells DirectoryService to try again.)
Cheers,
Wolfgang

Another problem I found with the MacOS X key bindings: the 6 key doesn't work!
In the config that ships with SQL Developer, I found this:
<Item class="oracle.javatools.util.Pair">
<first class="java.lang.String">DOCUMENT_6_CMD_ID</first>
<second class="oracle.ide.keyboard.KeyStrokes">
<data>
<Item class="javax.swing.KeyStroke">6</Item>
</data>
</second>
</Item>
which should be:
<Item class="oracle.javatools.util.Pair">
<first class="java.lang.String">DOCUMENT_6_CMD_ID</first>
<second class="oracle.ide.keyboard.KeyStrokes">
<data>
<Item class="javax.swing.KeyStroke">meta 6</Item>
</data>
</second>
</Item>

Authentication problem in starting WLS 6.1 in JBuilder 4

Similar Messages

Maybe you are looking for