Weblogic Server 10.0 MP1 on RHEL5 StartUp Issues

I am a newbie to Weblogic on RHEL. Havin issues with Weblogic to start up. I tried installing with root or a non root user but still the same result.
Its get stuck at Initializing state and never move on from there.
<BEA-000365> <Server state changed to STARTING>
<BEA-002900> <Initializing self-tuning thread pool>
Please let me know how to resolve this. I dunno if its a permission issue or not cos with root too its the same case .
I tried to create a new domain with configure.sh, gave the user name and password too while startup but still it doesnt move from this line.
Kindly let me know how to trace where n why its stuck .. or pls help me with the correct procedure to install

Hi,
Specially in Linux Environments sometimes we face issue of Locked Threads while starting some new processes...It happens many times because of less Entropy...Please refer to : http://weblogic-wonders.com/weblogic/2010/07/29/issues-relating-to-urandomrandom-on-weblogic-server-in-linux-environment/ for more details ....
Above may be one of the reason.
Thanks
jay SenSharma
http://weblogic-wonders.com/ /(Wonders Are Here)

Similar Messages

WebLogic Server 10.0 MP1: Error in resource adapter deployment

When I try to deploy our (own implemented) resource adapter into WebLogic Server 10.0 MP1, I get the following error message:
An error occurred during activation of changes, please see the log for details.
weblogic.security.service.InvalidParameterException: weblogic.security.service.SecurityServiceException: [Security:090198]No appropriate constructor for java.util.logging.LoggingPermission
java.util.logging.LoggingPermission.(java.lang.String)
The same adapter works flawless with Oracle AS/OC4J, JBoss 4.2 and Glassfish V2.
In the security-permission-spec element of our ra.xml file we use (beside others) the following permissions:
permission javax.management.MBeanTrustPermission "register";
permission java.util.logging.LoggingPermission "control";
When I delete this two lines from the security-permission-spec element, I can deploy the adapter in WebLogic.
For me this seems to be a bug in WebLogic 10.0MP1.
Best,
Manfred

Re: Installation error: Weblogic Server 10.0 MP2

WebLogic Server 9.2 MP1

Hello,
I am trying to download/install WebLogic 9.2 MP1 (as it is required, and is a prerequestie). My OS is Solaris 10 x86 64-bit. On the Oracle download page, when I select my operating system corresponding to WebLogic Server 9.2 MP1, I am lead to a new page, on which the only choice for download I have is for SPARC 32-bit. My question is, if it leads me to SPARC download instead of x86, will it still work? If not, where can I get WebLogic 9.2 MP1 for my OS?
We tried installing SPARC 32-bit and are getting an 'invalid argument' error everytime we try running the .bat file...
Any suggestions? Your help is greatly appreciated!!!
Svetlana

Hi,
Can you post the output of below commands from your OS?
uname -a
getconf LONG_BIT
Do you want to download and install 64-bit WLS 9.2 on your OS?
- - Tarun

Weblogic Server 10.0 MP1 while starting: Client VM not supported

Dear All,
Installation of Weblogic serever completed successfully but, while starting the weblogic server I am getting the following error/message: Client VM not supported.
Please provide suggestion or an idea on what to do. The details are provided below.
Processor: Intel Quad core 64bit
OS: windows server 2008 R2 64 bit
Java: JDK 1.5 update 21 64 bit
Weblogic: Server 10.0 MP1 64 bit for windows
Regards,
Edited by: user4198347 on Feb 5, 2011 11:48 PM

Re: Installation error: Weblogic Server 10.0 MP2

WebLogic Server Times OUT during DEBUG mode startup

Hi,
I am having a issue where my WebLogic Server 10.3 times out when I try to run it in debug mode in my workshop. Below is the error I get.
"Timeout waiting for Oracle WebLogic Server v10.3 at localhost to start. Server did not start after 480s. "
Do anyone have any idea why this is happening? I have reinstalled workshop but still same error.
Thanks

I have also seen this error when the debug mode does not start.
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
C:\bea103\JDK160~1\bin\java -client -Debug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms1200m -Xmx1200m -XX:CompileThreshold=8000 -XX:PermSize=192m -XX:MaxPermSize=192m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\bea103\WLSERV~1.3 -Dwls.home=C:\bea103\WLSERV~1.3\server -Dweblogic.home=C:\bea103\WLSERV~1.3\server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=true -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -DKS_URL=rmi://10.87.40.196:1188/KS -Dweblogic.ext.dirs=C:\bea103\patch_wlw1030\profiles\default\sysext_manifest_classpath;C:\bea103\patch_wls1030\profiles\default\sysext_manifest_classpath;C:\bea103\patch_wlp1030\profiles\default\sysext_manifest_classpath;C:\bea103\patch_cie670\profiles\default\sysext_manifest_classpath;C:\bea103\wlportal_10.3\p13n\lib\system;C:\bea103\wlportal_10.3\light-portal\lib\system;C:\bea103\wlportal_10.3\portal\lib\system;C:\bea103\wlportal_10.3\info-mgmt\lib\system;C:\bea103\wlportal_10.3\analytics\lib\system;C:\bea103\wlportal_10.3\apps\lib\system;C:\bea103\wlportal_10.3\info-mgmt\deprecated\lib\system;C:\bea103\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=C:\bea103\wlportal_10.3\portal\lib\security -Dweblogic.Name=AdminServer -Djava.security.policy=C:\bea103\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]

Weblogic Server 10.3.0 and LDAP authentication Issue

Hi - I have configured my WebLogic Server 10.3.0 for LDAP authentication (OID = 10.1.4.3.0) and so far the authentication works fine but I am having issue in terms of authorization.
I am not able to access the default web logic administrator console app using any of the LDAP user, getting Forbiden message.
It appears to me that the Weblogic Server is not pulling out the proper groups from the LDAP where user belongs too.
Can anyone please point me towards the right direction to get this resolved.
Thanks,
STEPS
Here are my steps I have followed:
- Created a group called Administrators in OID.
- Created a test user call uid=myadmin in the OID and assigned the above group to this user.
- Added a new Authentication Provider to the Weblogic and configured it what is required to communicate with OID (the config.xml file snipet is below)
<sec:authentication-provider xsi:type="wls:ldap-authenticatorType">
<sec:name>OIDAuthentication</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
<wls:propagate-cause-for-login-exception>false</wls:propagate-cause-for-login-exception>
<wls:host>pmpdeva-idm.ncr.pwgsc.gc.ca</wls:host>
<wls:port>1389</wls:port>
<wls:principal>cn=orcladmin</wls:principal>
<wls:user-base-dn>ou=AppAdmins, o=gc, c=ca</wls:user-base-dn>
<wls:credential-encrypted>removed from here</wls:credential-encrypted>
<wls:group-base-dn>ou=IDM, ou=ServiceAccounts, o=gc, c=ca</wls:group-base-dn>
</sec:authentication-provider>
- Marked the default authentication provider as sufficient as well.
- Re-ordered the authentication provide such that the OIDauthentication is first in the list and default one is the last.
- Looking at the log file I see there are no groups returned for this user and that is the problem in my opinion.
<LDAP Atn Login username: myadmin>
<getConnection return conn:LDAPConnection {ldaps://pmpdeva-idm.ncr.pwgsc.gc.ca:1389 ldapVersion:3 bindDN:"cn=orcladmin"}>
<authenticate user:myadmin>
<getDNForUser search("ou=AppAdmins, o=gc, c=ca", "(&(uid=myadmin)(objectclass=person))", base DN & below)>
<DN for user myadmin: uid=myadmin,ou=AppAdmins,o=gc,c=ca>
<authenticate user:myadmin with DN:uid=myadmin,ou=AppAdmins,o=gc,c=ca>
<authentication succeeded>
<returnConnection conn:LDAPConnection {ldaps://pmpdeva-idm.ncr.pwgsc.gc.ca:1389 ldapVersion:3 bindDN:"cn=orcladmin"}>
<LDAP Atn Authenticated User myadmin>
<List groups that member: myadmin belongs to>
<getConnection return conn:LDAPConnection {ldaps://pmpdeva-idm.ncr.pwgsc.gc.ca:1389 ldapVersion:3 bindDN:"cn=orcladmin"}>
<getDNForUser search("ou=AppAdmins, o=gc, c=ca", "(&(uid=myadmin)(objectclass=person))", base DN & below)>
<DN for user myadmin: uid=myadmin,ou=AppAdmins,o=gc,c=ca>
*<search("ou=IDM, ou=ServiceAccounts, o=gc, c=ca", "(&(uniquemember=uid=myadmin,ou=AppAdmins,o=gc,c=ca)(objectclass=groupofuniquenames))", base DN & below)>*
*<Result has more elements: false>*
<returnConnection conn:LDAPConnection {ldaps://pmpdeva-idm.ncr.pwgsc.gc.ca:1389 ldapVersion:3 bindDN:"cn=orcladmin"}>
<login succeeded for username myadmin>
- I see the XACML RoleMapper getRoles() only returning the Anonymous role as oppose to Admin (because the OID user is a part of Administrators group in OID then it should be returning Admin as fars I can tell. Here is the log entry that shows that:
<XACML RoleMapper getRoles(): returning roles Anonymous>
- I did a ldap search and I found no issues in getting the results back:
C:\>ldapsearch -h localhost -p 1389 -b"ou=IDM, ou=ServiceAccounts, o=gc, c=ca" -D cn=orcladmin -w "removed from here" (uniquemember=uid=myadmin,ou=AppAdmins,o=gc,c=ca)(objectclass=groupOfUniqueNames)
cn=Administrators,ou=IDM,ou=ServiceAccounts,o=gc,c=ca
objectclass=groupOfUniqueNames
objectclass=orclGroup
objectclass=top
END
Here are the log entries:
<1291668685624> <BEA-000000> <LDAP ATN LoginModule initialized>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize delegated>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.login>
<1291668685624> <BEA-000000> <LDAP Atn Login>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[0] will be delegated>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[0] will use NameCallback to retrieve name>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[1] will be delegated>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle will delegate all callbacks>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle delegated callbacks>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle got username from callbacks[0], UserName=myadmin>
<1291668685624> <BEA-000000> <LDAP Atn Login username: myadmin>
<1291668685624> <BEA-000000> <getConnection return conn:LDAPConnection { ldapVersion:2 bindDN:""}>
<1291668685624> <BEA-000000> <authenticate user:myadmin>
<1291668685624> <BEA-000000> <getDNForUser search("ou=people,ou=myrealm,dc=MBR_Domain", "(&(uid=myadmin)(objectclass=person))", base DN & below)>
<1291668685624> <BEA-000000> <getDNForUser search("ou=people,ou=myrealm,dc=MBR_Domain", "(&(uid=myadmin)(objectclass=person))", base DN & below)>
<1291668685624> <BEA-000000> <returnConnection conn:LDAPConnection { ldapVersion:2 bindDN:""}>
<1291668685624> <BEA-000000> <[Security:090302]Authentication Failed: User myadmin denied>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize LoginModuleClassName=weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize ClassLoader=java.net.URLClassLoader@facf0b>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize created delegate login module>
<1291668685624> <BEA-000000> <LDAP ATN LoginModule initialized>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize delegated>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.login>
<1291668685624> <BEA-000000> <LDAP Atn Login>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[0] will be delegated>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[1] will be delegated>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle will delegate all callbacks>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle delegated callbacks>
<1291668685624> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle did not get username from a callback>
<1291668685624> <BEA-000000> <LDAP Atn Login username: myadmin>
<1291668685624> <BEA-000000> <getConnection return conn:LDAPConnection {ldaps://pmpdeva-idm.ncr.pwgsc.gc.ca:1389 ldapVersion:3 bindDN:"cn=orcladmin"}>
<1291668685624> <BEA-000000> <authenticate user:myadmin>
<1291668685624> <BEA-000000> <getDNForUser search("ou=AppAdmins, o=gc, c=ca", "(&(uid=myadmin)(objectclass=person))", base DN & below)>
<1291668685671> <BEA-000000> <DN for user myadmin: uid=myadmin,ou=AppAdmins,o=gc,c=ca>
<1291668685671> <BEA-000000> <authenticate user:myadmin with DN:uid=myadmin,ou=AppAdmins,o=gc,c=ca>
<1291668685671> <BEA-000000> <authentication succeeded>
<1291668685686> <BEA-000000> <returnConnection conn:LDAPConnection {ldaps://pmpdeva-idm.ncr.pwgsc.gc.ca:1389 ldapVersion:3 bindDN:"cn=orcladmin"}>
<1291668685686> <BEA-000000> <LDAP Atn Authenticated User myadmin>
<1291668685686> <BEA-000000> <List groups that member: myadmin belongs to>
<1291668685686> <BEA-000000> <getConnection return conn:LDAPConnection {ldaps://pmpdeva-idm.ncr.pwgsc.gc.ca:1389 ldapVersion:3 bindDN:"cn=orcladmin"}>
<1291668685686> <BEA-000000> <getDNForUser search("ou=AppAdmins, o=gc, c=ca", "(&(uid=myadmin)(objectclass=person))", base DN & below)>
<1291668685686> <BEA-000000> <DN for user myadmin: uid=myadmin,ou=AppAdmins,o=gc,c=ca>
<1291668685686> <BEA-000000> <search("ou=IDM, ou=ServiceAccounts, o=gc, c=ca", "(&(uniquemember=uid=myadmin,ou=AppAdmins,o=gc,c=ca)(objectclass=groupofuniquenames))", base DN & below)>
<1291668685686> <BEA-000000> <Result has more elements: false>
<1291668685686> <BEA-000000> <returnConnection conn:LDAPConnection {ldaps://pmpdeva-idm.ncr.pwgsc.gc.ca:1389 ldapVersion:3 bindDN:"cn=orcladmin"}>
<1291668685686> <BEA-000000> <login succeeded for username myadmin>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.login delegated, returning true>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.commit>
<1291668685686> <BEA-000000> <LDAP Atn Commit>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.commit delegated, returning false>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.commit>
<1291668685686> <BEA-000000> <LDAP Atn Commit>
<1291668685686> <BEA-000000> <LDAP Atn Principals Added>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.commit delegated, returning true>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.JAASLoginServiceImpl.login logged in>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.JAASLoginServiceImpl.login subject=Subject:
     Principal: myadmin
>
<1291668685686> <BEA-000000> <weblogic.security.service.internal.WLSIdentityServiceImpl.getIdentityFromSubject Subject: 1
     Principal = class weblogic.security.principal.WLSUserImpl("myadmin")
>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.sign(Principals)>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.sign(Principal) Principal=myadmin>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.sign(Principal) PrincipalClassName=weblogic.security.principal.WLSUserImpl>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.sign(Principal) trying PrincipalValidator for interface weblogic.security.principal.WLSPrincipal>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.sign(Principal) PrincipalValidator handles this PrincipalClass>
<1291668685686> <BEA-000000> <Signed WLS principal myadmin>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.sign(Principal) PrincipalValidator signed the principal>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.sign(Principal) All required PrincipalValidators signed this PrincipalClass, returning true>
<1291668685686> <BEA-000000> <com.bea.common.security.internal.service.JAASLoginServiceImpl.login identity=Subject: 1
     Principal = class weblogic.security.principal.WLSUserImpl("myadmin")
>
<1291668685686> <BEA-000000> <weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.authenticate authenticate succeeded for user myadmin, Identity=Subject: 1
     Principal = class weblogic.security.principal.WLSUserImpl("myadmin")
>
<1291668685686> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.isLocked(myadmin)>
<1291668685686> <BEA-000000> <weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.authenticate login succeeded and myadmin was not previously locked out>
<1291668685702> <BEA-000000> <Using Common RoleMappingService>
<1291668685702> <BEA-000000> <PrincipalAuthenticator.validateIdentity>
<1291668685702> <BEA-000000> <PrincipalAuthenticator.validateIdentity will use common security service>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.validate(Principals)>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.validate(Principal) Principal=myadmin>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.validate(Principal) PrincipalClassName=weblogic.security.principal.WLSUserImpl>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.validate(Principal) trying PrincipalValidator for interface weblogic.security.principal.WLSPrincipal>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.validate(Principal) PrincipalValidator handles this PrincipalClass>
<1291668685702> <BEA-000000> <Validate WLS principal myadmin returns true>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.validate(Principal) PrincipalValidator said the principal is valid>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.validate(Principal) One or more PrincipalValidators handled this PrincipalClass, returning true>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.PrincipalValidationServiceImpl.validate(Principals) validated all principals>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.RoleMappingServiceImpl.getRoles Identity=Subject: 1
     Principal = class weblogic.security.principal.WLSUserImpl("myadmin")
>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.RoleMappingServiceImpl.getRoles Resource=type=<url>, application=consoleapp, contextPath=/console, uri=/index.jsp, httpMethod=GET>
<1291668685702> <BEA-000000> <XACML RoleMapper getRoles(): input arguments:>
<1291668685702> <BEA-000000> <     Subject: 1
     Principal = weblogic.security.principal.WLSUserImpl("myadmin")
>
<1291668685702> <BEA-000000> <     Resource: type=<url>, application=consoleapp, contextPath=/console, uri=/index.jsp, httpMethod=GET>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console, uri=/index.jsp>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console, uri=/index.jsp/*, httpMethod=GET>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console, uri=/index.jsp/*>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console, uri=/*, httpMethod=GET>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console, uri=/*>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console, uri=*.jsp, httpMethod=GET>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console, uri=*.jsp>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console, uri=/, httpMethod=GET>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console, uri=/>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp, contextPath=/console>
<1291668685702> <BEA-000000> <     Parent: type=<url>, application=consoleapp>
<1291668685702> <BEA-000000> <     Parent: type=<app>, application=consoleapp>
<1291668685702> <BEA-000000> <     Parent: type=<url>>
<1291668685702> <BEA-000000> <     Parent: null>
<1291668685702> <BEA-000000> <     Context Handler: >
<1291668685702> <BEA-000000> <Accessed Subject: Id=urn:oasis:names:tc:xacml:2.0:subject:group, Value=[everyone,users]>
<1291668685702> <BEA-000000> <Evaluate urn:oasis:names:tc:xacml:1.0:function:string-is-in(AdminChannelUsers,[everyone,users]) -> false>
<1291668685702> <BEA-000000> <primary-rule evaluates to NotApplicable because of Condition>
<1291668685702> <BEA-000000> <urn:bea:xacml:2.0:entitlement:role:AdminChannelUser:, 1.0 evaluates to Deny>
<1291668685702> <BEA-000000> <XACML RoleMapper: accessing role AdminChannelUser: DENIED>
<1291668685702> <BEA-000000> <Accessed Subject: Id=urn:oasis:names:tc:xacml:2.0:subject:group, Value=[everyone,users]>
<1291668685702> <BEA-000000> <Evaluate urn:oasis:names:tc:xacml:1.0:function:string-is-in(AppTesters,[everyone,users]) -> false>
<1291668685702> <BEA-000000> <primary-rule evaluates to NotApplicable because of Condition>
<1291668685702> <BEA-000000> <urn:bea:xacml:2.0:entitlement:role:AppTester:, 1.0 evaluates to Deny>
<1291668685702> <BEA-000000> <XACML RoleMapper: accessing role AppTester: DENIED>
<1291668685702> <BEA-000000> <Accessed Subject: Id=urn:oasis:names:tc:xacml:2.0:subject:group, Value=[everyone,users]>
<1291668685702> <BEA-000000> <Evaluate urn:oasis:names:tc:xacml:1.0:function:string-is-in(everyone,[everyone,users]) -> true>
<1291668685702> <BEA-000000> <primary-rule evaluates to Permit>
<1291668685702> <BEA-000000> <urn:bea:xacml:2.0:entitlement:role:Anonymous:, 1.0 evaluates to Permit>
<1291668685702> <BEA-000000> <XACML RoleMapper: accessing role Anonymous: GRANTED>
<1291668685702> <BEA-000000> <Accessed Subject: Id=urn:oasis:names:tc:xacml:2.0:subject:group, Value=[everyone,users]>
<1291668685702> <BEA-000000> <Evaluate urn:oasis:names:tc:xacml:1.0:function:string-is-in(Monitors,[everyone,users]) -> false>
<1291668685702> <BEA-000000> <primary-rule evaluates to NotApplicable because of Condition>
<1291668685702> <BEA-000000> <urn:bea:xacml:2.0:entitlement:role:Monitor:, 1.0 evaluates to Deny>
<1291668685702> <BEA-000000> <XACML RoleMapper: accessing role Monitor: DENIED>
<1291668685702> <BEA-000000> <Accessed Subject: Id=urn:oasis:names:tc:xacml:2.0:subject:group, Value=[everyone,users]>
<1291668685702> <BEA-000000> <Evaluate urn:oasis:names:tc:xacml:1.0:function:string-is-in(Operators,[everyone,users]) -> false>
<1291668685702> <BEA-000000> <primary-rule evaluates to NotApplicable because of Condition>
<1291668685702> <BEA-000000> <urn:bea:xacml:2.0:entitlement:role:Operator:, 1.0 evaluates to Deny>
<1291668685702> <BEA-000000> <XACML RoleMapper: accessing role Operator: DENIED>
<1291668685702> <BEA-000000> <Accessed Subject: Id=urn:oasis:names:tc:xacml:2.0:subject:group, Value=[everyone,users]>
<1291668685702> <BEA-000000> <Evaluate urn:oasis:names:tc:xacml:1.0:function:string-is-in(CrossDomainConnectors,[everyone,users]) -> false>
<1291668685702> <BEA-000000> <primary-rule evaluates to NotApplicable because of Condition>
<1291668685702> <BEA-000000> <urn:bea:xacml:2.0:entitlement:role:CrossDomainConnector:, 1.0 evaluates to Deny>
<1291668685702> <BEA-000000> <XACML RoleMapper: accessing role CrossDomainConnector: DENIED>
<1291668685702> <BEA-000000> <Accessed Subject: Id=urn:oasis:names:tc:xacml:2.0:subject:group, Value=[everyone,users]>
<1291668685702> <BEA-000000> <Evaluate urn:oasis:names:tc:xacml:1.0:function:string-is-in(Deployers,[everyone,users]) -> false>
<1291668685702> <BEA-000000> <primary-rule evaluates to NotApplicable because of Condition>
<1291668685702> <BEA-000000> <urn:bea:xacml:2.0:entitlement:role:Deployer:, 1.0 evaluates to Deny>
<1291668685702> <BEA-000000> <XACML RoleMapper: accessing role Deployer: DENIED>
<1291668685702> <BEA-000000> <Accessed Subject: Id=urn:oasis:names:tc:xacml:2.0:subject:group, SC=null, Value=[everyone,users]>
<1291668685702> <BEA-000000> <Evaluate urn:oasis:names:tc:xacml:1.0:function:string-is-in(Administrators,[everyone,users]) -> false>
<1291668685702> <BEA-000000> <primary-rule evaluates to NotApplicable because of Condition>
<1291668685702> <BEA-000000> <urn:bea:xacml:2.0:entitlement:role:Admin:, 1.0 evaluates to Deny>
<1291668685702> <BEA-000000> <XACML RoleMapper: accessing role Admin: DENIED>
<1291668685702> <BEA-000000> <XACML RoleMapper getRoles(): returning roles Anonymous>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.RoleMappingServiceImpl.getRoles returning [ "Anonymous" ]>
<1291668685702> <BEA-000000> <AuthorizationManager will use common security for ATZ>
<1291668685702> <BEA-000000> <weblogic.security.service.WLSAuthorizationServiceWrapper.isAccessAllowed>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed Identity=Subject: 1
     Principal = class weblogic.security.principal.WLSUserImpl("myadmin")
>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed Roles=[ "Anonymous" ]>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed Resource=type=<url>, application=consoleapp, contextPath=/console, uri=/index.jsp, httpMethod=GET>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed Direction=ONCE>
<1291668685702> <BEA-000000> <XACML Authorization isAccessAllowed(): input arguments:>
<1291668685702> <BEA-000000> <     Subject: 1
     Principal = weblogic.security.principal.WLSUserImpl("myadmin")
>
<1291668685702> <BEA-000000> <     Roles:Anonymous>
<1291668685702> <BEA-000000> <     Resource: type=<url>, application=consoleapp, contextPath=/console, uri=/index.jsp, httpMethod=GET>
<1291668685702> <BEA-000000> <     Direction: ONCE>
<1291668685702> <BEA-000000> <     Context Handler: >
<1291668685702> <BEA-000000> <Accessed Subject: Id=urn:oasis:names:tc:xacml:2.0:subject:role, SC=null, Value=Anonymous>
<1291668685702> <BEA-000000> <Evaluate urn:oasis:names:tc:xacml:1.0:function:string-at-least-one-member-of([Admin,Operator,Deployer,Monitor],Anonymous) -> false>
<1291668685702> <BEA-000000> <primary-rule evaluates to NotApplicable because of Condition>
<1291668685702> <BEA-000000> <urn:bea:xacml:2.0:entitlement:resource:type@E@Furl@G@M@Oapplication@Econsoleapp@M@OcontextPath@E@Uconsole@M@Ouri@E@U, 1.0 evaluates to Deny>
<1291668685702> <BEA-000000> <XACML Authorization isAccessAllowed(): returning DENY>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed AccessDecision returned DENY>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.AdjudicationServiceImpl.adjudicate Results=[ DENY ]>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.AdjudicationServiceImpl.adjudicate Resource=type=<url>, application=consoleapp, contextPath=/console, uri=/index.jsp, httpMethod=GET>
<1291668685702> <BEA-000000> <DefaultAdjudicatorImpl.adjudicate results: DENY >
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.AdjudicationServiceImpl.adjudicate Adjudictor returned false, returning that value>
<1291668685702> <BEA-000000> <com.bea.common.security.internal.service.AuthorizationServiceImpl.isAccessAllowed returning adjudicated: false>

Okay Finally the issue is resolved. Here is the findings to help others in case they ran into the same issue.
The OID version that we are using is not returning the groups the way Weblogic is building the ldapsearch command. We captured the ldap traffic to go deeper and noticed the filters and attributes list that wls was asking. For example, the filter was like:
"(&(uniquemember=uid=myadmin,ou=AppAdmins,o=gc,c=ca)(objectclass=groupofuniquenames))" cn
its was the "cn" attribute that was causing the result set to be empty.
from a command line we tried
"(&(uniquemember=uid=myadmin,ou=AppAdmins,o=gc,c=ca)(objectclass=groupofuniquenames))" uniquemember
and got the results back.
Then we start looking into OID configuration and one of my coworker pointed me towards the orclinmemfiltprocess attributes in cn=dsaconfig entry and told me that they had lot of issues in the past in relation to this attribute.
So as a test we removed the groupofuniquenames objectclass from the orclinmemfiltprocess attribute list and bingo it worked!
Since we needed the groupofuniquenames in this list for performance/other reasons and decided to use a different objectclass for our groups instead i.e. orclGroup.
Thanks everyone for showing interest on the problem and providing suggestions.

WebLogic Server 10.3 - iPlanet 6.0 Plugin issue

Hello,
I have WebLogic Server 10.3 installed on Solaris 9, working fine in all respects.
I have iPlanet Web Server 6.0 installed and running fine with WebLogic 7.0 - plugin works perfectly fine on a separate unix box with solaris 9.
When I try to make the plugin work for iPlanet 6.0 - WLS 10.3 I am getting errors. I have followed two steps for the plugin
1) I have added following line in magnus.conf
Init fn="load-modules" shlib="/apps/bea/wlserver_10.3/server/plugin/solaris/sparc/libproxy_61.so" funcs="wl_proxy,wl_init"
Init fn="wl_init"
bash-2.05$ ls -lt /apps/bea/wlserver_10.3/server/plugin/solaris/sparc/libproxy_61.so
-rwxr-xr-x 1 admweb www 1378764 Jun 30 08:53 /apps/bea/wlserver_10.3/server/plugin/solaris/sparc/libproxy_61.so
2) I have added following entry in obj.conf as follows
<Object name="weblogic" ppath="*/servlet/*">
Service fn="wl_proxy" WebLogicHost="WLS_HOSTNAME" WebLogicPort="9092" ConnectTimeoutSecs="300" Debug="OFF" WLLogFile="/apps/iplanet/https-rcte/logs/abc/Weblogic10Plugins.log" PathPrepend="abc"
</Object>
When I restart the iPlanet it does not start and get the following errors:
[30/Jun/2009:14:19:18] failure (23978): Configuration initialization failed: Error running init function load-modules: dlopen of /apps/iplanet/plugins/libproxy_61.so failed (ld.so.1: ns-httpd: fatal: relocation error: file /apps/iplanet/plugins/libproxy_61.so: symbol __1cG__CrunIex_alloc6FI_pv_: referenced symbol not found)
SunOS 5.9 Generic_118558-11 sun4u sparc SUNW,Sun-Fire-V240
Can someone help what is causing this error?

Hello All,
Thanks for the responses till now.
There is no such file as libproxy.so
bash-2.05$ cd /apps/bea/wlserver_10.3/server/plugin/solaris/sparc/
bash-2.05$ ls -lt
total 5442
drwxr-sr-x 2 admweb www 512 Jun 25 06:27 largefile
-rw-r--r-- 1 admweb www 1378796 Jun 25 06:27 libproxy128_61.so
-rw-r--r-- 1 admweb www 1378764 Jun 25 06:27 libproxy_61.so
/apps/bea/wlserver_10.3/server/lib does not contain any plugin files, it contains ONLY jar files.
One question: is iPlanet 6.0 supported by WLS 10.3?, I doubt.
Please help me confirm.
Regards,
Rajesh.

Weblogic server is not getting started.

Hi
We are getting problem in starting weblogic server 10.2 .
We have two machine they switch each other by cluster.
On one machine , Weblogic server does not start when cluster switch to this machine.
When server starts , it hangs. We get following eroor:
s*tarting weblogic with Java version:*
The Autonomy executable IDOLserver/DiSH/AutonomyDiSH.exe is not executable. Cannot start the search engine.
ERROR: transport error 202: bind failed: Address already in use ["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)
Starting WLS with line:
*/home/bea/bea102/jdk150_11/bin/java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx2048m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=256m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/home/bea/bea102/wlserver_10.0 -Dwls.home=/home/bea/bea102/wlserver_10.0/server -Dweblogic.home=/home/bea/bea102/wlserver_10.0/server -Dwli.home=/home/bea/bea102/wlserver_10.0/integration -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/home/bea/bea102/patch_wss110/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wlw1020/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wls1001/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wlp1020/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_cie640/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=/home/bea/bea102/wlserver_10.0/server/lib/weblogic.policy weblogic.Server*
ERROR: transport error 202: bind failed: Address already in use ["transport.c",L41]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)
This issue is in our production environment. So plaese help me considering it URGENT.
Thanks

Nice to help me.
We observe the server start up log. We did all that you suggested.
Still I am not able to start the production server. As we get very lesser chance to RND on production server.
The new problem is now , when we start the server, its hangs, and did not start.
I am posting the sever startup log:
J*AVA Memory arguments: -Xms256m -Xmx2048m -XX:MaxPermSize=256m*
WLS Start Mode=Production
CLASSPATH=""
PATH=""
** 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:
The Autonomy executable IDOLserver/DiSH/AutonomyDiSH.exe is not executable. Cannot start the search engine.
java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) Server VM (build 1.5.0_11-b03, mixed mode)
Starting WLS with line:
*/home/bea/bea102/jdk150_11/bin/java -server -Xms256m -Xmx2048m -XX:MaxPermSize=256m -da -Dplatform.home=/home/bea/bea102/wlserver_10.0 -Dwls.home=/home/bea/bea102/wlserver_10.0/server -Dweblogic.home=/home/bea/bea102/wlserver_10.0/server -Dwli.home=/home/bea/bea102/wlserver_10.0/integration -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/home/bea/bea102/patch_wss110/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wlw1020/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wls1001/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_wlp1020/profiles/default/sysext_manifest_classpath:/home/bea/bea102/patch_cie640/profiles/default/sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.policy=/home/bea/bea102/wlserver_10.0/server/lib/weblogic.policy weblogic.Server*
*<Sep 1, 2009 1:14:12 AM LKT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:*
*/home/bea/bea102/wlserver_10.0/platform/lib/cm/content_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/p13n/p13n-schemas.jar:/home/bea/bea102/wlserver_10.0/platform/lib/p13n/p13n_common.jar:/home/bea/bea102/wlserver_10.0/platform/lib/p13n/p13n_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/p13n/wlp_services.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/analytics_sys.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/commerce_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/groupspace_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/netuix_common.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/netuix_schemas.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/netuix_system-full.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/netuix_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/nf-jspcmods.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/nf-system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wlp-schemas.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wlp_content_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wps_system.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wsrp-client.jar:/home/bea/bea102/wlserver_10.0/platform/lib/wlp/wsrp-common.jar>*
*<Sep 1, 2009 1:14:12 AM LKT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_11-b03 from Sun Microsystems Inc.>*
*<Sep 1, 2009 1:14:13 AM LKT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR348244 Fri Oct 19 11:57:37 PDT 2007*
WebLogic Server Temporary Patch for CR346064 Fri Oct 19 13:27:18 PDT 2007
WebLogic Server Temporary Patch for CR346063 Fri Oct 05 14:48:13 PDT 2007
WebLogic Server Temporary Patch for Cr346061 Thu Oct 18 15:38:04 PDT 2007
WebLogic Server Temporary Patch for Cr346061 Thu Oct 18 15:38:04 PDT 2007
WebLogic Server Temporary Patch for CR346060 Thu Oct 18 15:28:01 PDT 2007
WebLogic Server Temporary Patch for CR350528 Fri Nov 02 16:19:36 PDT 2007
WebLogic Server Temporary Patch for CR354048 Thu Dec 06 13:52:09 IST 2007
WebLogic Server Temporary Patch for CR348229 Wed Oct 24 13:49:07 PDT 2007
WebLogic Server Temporary Patch for CR356295 Wed Dec 19 15:37:45 EST 2007
WebLogic Server 10.0 MP1 Thu Oct 18 20:17:44 EDT 2007 1005184 >
*<Sep 1, 2009 1:14:15 AM LKT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /home/bea/bea102/license.bea>*
*<Sep 1, 2009 1:14:15 AM LKT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>*
*<Sep 1, 2009 1:14:15 AM LKT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>*
*<Sep 1, 2009 1:14:15 AM LKT> <Notice> <Log Management> <BEA-170019> <The server log file /home/bea/bea102/user_projects/domains/tmpasldomain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>*
Sever hangs on the line
*/home/bea/bea102/user_projects/domains/tmpasldomain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>*
please give some more suggestion.
Thnaks

Regarding datasource in weblogic server

Hi All,
while creating datasource i am getting the following error
An error occurred during activation of changes, please see the log for details.
weblogic.application.ModuleException:
weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: invalid arguments in call
i am connecting to oracle server and i am giving all The
details eventhough i am getting exception
i am using weblogic 10.0 version
please help me as soon as possible
thanks in advance'
tirumal

I am getting the same error as he is getting with Weblogic Server 10.0 MP1. We are going from Version 7.0 to 10 :
I am configuring an Oracle Data Source from the console.
I selected Other for Oracle driver
I specify the following driver: oracle.jdbc.driver.OracleDriver.
I test the new jdbc configuration and I get a successful Connection test.
When I then assign it to my AdminServer and activate the changes is when I get the same error:
weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: invalid arguments in call.
I go to the \pending\jdbc\CtTxDataSource-3770-jdbc.xml
Below is what the JDBC Datasource Configuration built:
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<name>CtTxDataSource</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@oims-npe-dev1:1521:oimsdev1</url>
<driver-name>oracle.jdbc.driver.OracleDriver</driver-name>
<password-encrypted>{3DES}oKK0HLMQ9oRN05wfBXY7sQ==</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<test-table-name>SELECT * FROM APP</test-table-name>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>CtTxDataSource</jndi-name>
<global-transactions-protocol>EmulateTwoPhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>
It didn't put in the <property> defining user logon and the database which I provided when I ran thru the configuration steps. Is this a bug on the 10.0 mp1 version of Weblogic? I had to manually add the property values to make it work. The same occurred when I configured a DB2 for ZOS.
Thanks.

Weblogic server 10.0

Hi,
I want Weblogic server 10.0 mp1. can any one tell me how to download it. I am getting servers from 10.3 only.
Regards,
Haranadh

You can use the advanced section of the Logging tab of your Server. Here you find an attribute called 'Date Format Pattern'. By default this is set to MMM d, yyyy h:mm:ss a z.
It uses a DateFormatPattern string which conforms to the specification of the java.text.SimpleDateFormat class. So you can use a 'S' for milliseconds. (also see the javadocs http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html)

How to delete the deployed composite in weblogic server 11g

Can someone tell me how to delete the deployed composite in weblogic server 11g ?I'm facing an issue where the weblogic server is getting started and immediately after sometime the server changes to "Force shutdown"..When i checked the logs,there is an error in one of the composite i deployed..So now i wanted to delete the deployed composite?Please help ....
Thanks

Hi
1. Deleting a domain will not hold any references. But make sure that under your user_projects/applications also remove the folder that matches with your domain. Basically under user_projects folder you will see 2 folders named applications and domains. When you create a domain say mySoaDomain, it will crate a folder with the same name under applications folder also with few files like em.ear. If you do this, then you can crate a new soa domain and use the same old name.
2. NOW comes the most important thing. If you create a new SOADomain, at one point, you had to give details for soainfra and mds schemas. If you give your current existing db details (that was used for your old deleted domain), then you may still have the issues. Because the soainfra db may still have the instances for your old process.
3. If you really want to have a full clean soa domain, here is what you do:
a) Run rcu and drop the existing schemas for soainfra and mds.
b) Run rcu again and create above schemas again.
c) Now create SOADomain using config wizard and refer above clean rcu db and you are all set.
3. Under your domain root folder, just searh for files named with your workflow and you should see the .jar location.
Thanks
Ravi Jegga

OEPE 1.6 - Oracle WebLogic Server 11gR1 PatchSet 3 requres WLS 10.3.4

Hi!
Anyone knowing when Weblogic Server 10.3.4 is planed GA
Borre

Borre,
See the recent OTN post from 20110115 detailing the latest release of Oracle WebLogic Server and some retesting of the previous issues related to JSR-317 JPA 2.0 support below.
Re: Deploy Hibernate based EAR file on Weblogic 10.3.3?
The latest release of Oracle WebLogic Server has been available on OTN at the following location since 20110115.
http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
This release provides support for JSR-317 JPA 2.0 container managed applications using the QWG8 patch or a manual prepending classpath change.
In 10.3.3.0 you were required to use the FilteringClassLoader via the *<wls:prefer-application-packages>* addition to your application managed persistence unit - this workaround as well as the persistence.xml renaming one is now fully deprecated and not required in 10.3.4.0 for both application and container managed persistence contexts.
As of 20110115 the 5 outstanding issues below look to be fixed by applying the http://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309 patch for QWG8 or manually prepending to the WebLogic 10.3.4.0 server classpath.
commEnv.cmd: line 67
@rem Set BEA Home
set BEA_HOME=C:\opt\wls1034r20110115
@rem Enable JPA 2.0 functionality on WebLogic Server 10.3.4 with the following patch line for commEnv.cmd:67
set PRE_CLASSPATH=%BEA_HOME%\modules\javax.persistence_1.0.0.0_2-0-0.jar;%BEA_HOME%\modules\com.oracle.jpa2support_1.0.0.0_2-0.jar
A JPA 2.0 EE application using EclipseLink as the JPA2 persistence provider on WebLogic is detailed in the analysis section below1) JPA 2.0 XSD parsing - verified
2) New JPA 2.0 schema elements like <shared-cache-mode>NONE</shared-cache-mode> - verified
3) JPA 2.0 runtime API like a entityManager.getMetamodel(); call on the Servlet or Stateless session bean - verified
4) JPA 2.0 weaving/instrumentation - this will require a more detailed lazy model and more debugging to fully verify
5) Dependency Injection of a container managed JPA 2.0 entityManager on a EJB component like a stateless session bean - verified
http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
OTN downloadhttp://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-main-097127.html
Patching
http://download.oracle.com/docs/cd/E18476_01/doc.220/e18480/weblogicchap.htm
Documentationhttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13852/toc.htm
Supported Oracle WebLogic Server Versionshttp://download.oracle.com/docs/cd/E15315_06/help/oracle.eclipse.tools.weblogic.doc/html/SupportedServerVersions.html
TopLink JPA 2.0 Specific documentation/patchinghttp://download.oracle.com/docs/cd/E17904_01/web.1111/e13720/using_toplink.htm#EJBAD1309
EclipseLink Wiki: JPA 2.0 using EclipseLink on WebLogic analysis (XSD, Weaving, DI of @PersistenceContext)http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#Enabling_JPA2_support
thank you
/Michael O'Brien
http://www.eclipselink.org

WebLogic 10.3.2.0 hanging at startup after "The server log file is opened."

Hi,
A WebLogic 10.3.2.0 server is hanging at startup. There are no error messages. The last command in the startup window is:
"The server log file <log file dest> is opened. All server side log events will be written to this file."
I think the next line should be:
"Security initializing using security realm realm."
Any ideas on what could be the issue? For instance what resources should be accessed at that point of time? There is sufficient space left on the (virtual machine) disk. The VM configured with 8GB memory. Could it be performance related still?
Following is written to the log file:
####<12.aug.2010 kl 09.47 CEST> <Info> <WebLogicServer> <oim> <> <Main Thread> <> <> <> <1281599254656> <BEA-000214> <WebLogic Server "AdminServer" version:
WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.> ####<12.aug.2010 kl 09.47 CEST> <Notice> <Log Management> <oim> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1281599255312> <BEA-170019> <The server log file ....logs\AdminServer.log is opened. All server side log events will be written to this file.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Log Management> <oim> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1281599255390> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Diagnostics> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599255671> <BEA-320001> <The ServerDebug service initialized successfully.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Store> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599256515> <BEA-280050> <Persistent store "WLS_DIAGNOSTICS" opened: directory="....s\domains\oim\servers\AdminServer\data\store\diagnostics" writePolicy="Disabled" blockSize=512 directIO=false driver="wlfileio2"> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "t3" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "t3s" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "http" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "https" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "iiop" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "iiops" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "ldap" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "ldaps" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257187> <BEA-002622> <The protocol "cluster" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257187> <BEA-002622> <The protocol "clusters" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002622> <The protocol "snmp" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002622> <The protocol "admin" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002624> <The administration protocol is "t3s" and is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <RJVM> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257468> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address          :7001
Public Address          N/A
Http Enabled          true
Tunneling Enabled     false
Outbound Enabled     false
Admin Traffic Enabled     true>
####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257687> <BEA-002609> <Channel Service initialized.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258000> <BEA-000406> <NTSocketMuxer was built on Jan 13 2005 17:47:03
####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258078> <BEA-000436> <Allocating 3 reader threads.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258078> <BEA-000446> <Native IO Enabled.> ####<12.aug.2010 kl 09.47 CEST> <Info> <IIOP> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599259500> <BEA-002014> <IIOP subsystem enabled.>
Thanks!!

tried both of these, still having same error as below:
<Sep 8, 2010 1:32:37 PM IST> <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.>
<Sep 8, 2010 1:32:37 PM IST> <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:959)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic2 javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic2 denied
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:250)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<Sep 8, 2010 1:32:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 8, 2010 1:32:37 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 8, 2010 1:32:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Pls help me out ASAP...

How to specify the webLogic server startup script to use different config.xml file ??

Hi,
I have 2 weblogic startup scripts (startWebLogic.sh and
startWebLogic_recovery.sh) for the same domain.
startWebLogic.sh uses config.xml file.
I would like to use config_recovery.xml as the configuration file for startWebLogic_recovery.sh
How would I do this ?
I am using WebLogic Server 6.1 on SunOS 5.8 / HP-UX 11.0.
Appreciate any help.
Regards
Gunaseelan Venkateswaran

I guess you're using Weblogic 6.1 with WLCS 3.5. I think you're supposed to work with one config.xml for the same domain, and not have a different config.xml.
To start up different applications or EJBs, use the "target" property to control which applications to start up for the particular instance.
YY

Error when I startup the Weblogic server.

Hi
Look I chance my proxy configuration 'Cause before I have a free LAN to navigate on internet. Since then, when I want to startup the weblogic service the following error :
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<14-sep-2010 20H08' PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<14-sep-2010 20H08' PET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<14-sep-2010 20H08' PET> <Notice> <Log Management> <BEA-170019> <The server log file /u01/oracle/user_projects/domains/CoreNevadoDomain/servers/CoreNevadoAdminServer/logs/CoreNevadoAdminServer.log is opened. All server side log events will be written to this file.>
<14-sep-2010 20H08' PET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<14-sep-2010 20H08' PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<14-sep-2010 20H08' PET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
*<14-sep-2010 20H14' PET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application '01-eng-CoreNevadoEngine' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(engine-CoreNevadoEngine.jar)*
*[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:*
*ParseError at [row,col]:[5,148]*
Message: Tried all: '2' addresses, but could not connect over HTTP to server: 'www.oracle.com', port: '80'..
weblogic.application.ModuleException: Exception preparing module: EJBModule(engine-CoreNevadoEngine.jar)
[EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
ParseError at [row,col]:[5,148]
Message: Tried all: '2' addresses, but could not connect over HTTP to server: 'www.oracle.com', port: '80'.
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
Truncated. see log file for complete stacktrace
javax.xml.stream.XMLStreamException: ParseError at [row,col]:[5,148]
Message: Tried all: '2' addresses, but could not connect over HTTP to server: 'www.oracle.com', port: '80'
at com.sun.xml.stream.XMLReaderImpl.next(XMLReaderImpl.java:560)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.isDTDBased(EjbDescriptorReaderImpl.java:451)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.parseWLDD(EjbDescriptorReaderImpl.java:525)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWeblogicEjbJarXML(EjbDescriptorReaderImpl.java:388)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:196)
Truncated. see log file for complete stacktrace
>
14-sep-2010 20:14:48 com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
14-sep-2010 20:14:48 com.sun.faces.config.ConfigureListener contextInitialized
INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
********* Oracle® BPM - WorkSpace Administrator (Version 10.3.1.0.0 Service Pack 1 Build #94375) is starting *********
Checking Java Runtime Enviroment ...Ok
Initializing enviroment...Ok
Loading Plugins for Workspace Administrator ...Ok
log4j:WARN No appenders could be found for logger (com.sun.faces.config.ConfigureListener).
log4j:WARN Please initialize the log4j system properly.
OpenLog: verbosity level = 2
OpenLog: Registered application name: OpenControls.srvapptest
OpenControls.srvapptest
help me,plz.
Thanks

Hi,
You can write it inside your ManagedServers Start Script or even you can write it in your "setDomainEnv.sh"(if u are in UNIX OS) or in "setDomainEnv.cmd (if it is WINDOWS)"as described in the below Image:
http://weblogic-wonders.com/weblogic/wp-content/uploads/2010/09/setting_JAVA_JOME_In_script.jpg
The Only difference will be....in the JAVA_OPTION as below:
Unix OS case below
*JAVA_OPTIONS=${JAVA_OPTIONS} -Dhttp.proxyHost=YourProxyHostName -Dhttp.proxyPort=yourProxyPort*
Windows OS Case below
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dhttp.proxyHost=YourProxyHostName -Dhttp.proxyPort=yourProxyPort
Thanks
Jay SenSharma

Weblogic Server 10.0 MP1 on RHEL5 StartUp Issues

Similar Messages

Maybe you are looking for