WLS issue
Hi,
Any advice to resolve this against Jdev 11.1.1.4?
d:\oracle\MIDDLE~1\JDK160~1\bin\java -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=D:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Djavax.net.ssl.trustStore=D:\oracle\Middleware11_1_1_4d\wlserver_10.3\server\lib\DemoTrust.jks -Dweblogic.nodemanager.ServiceEnabled=true -da -Dplatform.home=D:\oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\oracle\MIDDLE~1\WLSERV~1.3\server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=D:\oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\DOCUME~1\WONGPE~1.000\APPLIC~1\JDEVEL~1\SYSTEM~1.23\DEFAUL~1 -Djrockit.optfile=D:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\DOCUME~1\WONGPE~1.000\APPLIC~1\JDEVEL~1\SYSTEM~1.23\DEFAUL~1\config\FMWCON~1\servers\DefaultServer -Doracle.domain.config.dir=D:\DOCUME~1\WONGPE~1.000\APPLIC~1\JDEVEL~1\SYSTEM~1.23\DEFAUL~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\DOCUME~1\WONGPE~1.000\APPLIC~1\JDEVEL~1\SYSTEM~1.23\DEFAUL~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\DOCUME~1\WONGPE~1.000\APPLIC~1\JDEVEL~1\SYSTEM~1.23\DEFAUL~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\DOCUME~1\WONGPE~1.000\APPLIC~1\JDEVEL~1\SYSTEM~1.23\DEFAUL~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\DOCUME~1\WONGPE~1.000\APPLIC~1\JDEVEL~1\SYSTEM~1.23\DEFAUL~1\servers\DefaultServer\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=D:\DOCUME~1\WONGPE~1.000\APPLIC~1\JDEVEL~1\SYSTEM~1.23\DEFAUL~1\oracle\store\gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= weblogic.Server
java.lang.NoClassDefFoundError: weblogic/Server
Caused by: java.lang.ClassNotFoundException: weblogic.Server
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Could not find the main class: weblogic.Server. Program will exit.
Exception in thread "main" Process exited.
Hi,
Try setting JDEV_USER_DIR to a directory without space in the path before starting jdev and try (assuming you are getting this issue in the integrated server).
1. Invoke cmd prompt
2. cd to <JDev_Home>\jdeveloper\jdev\bin
3. set JDEV_USER_DIR=d:\myuserdir
4. jdev.exe
-Arun
Similar Messages
-
No Lock & Edit button in WLS 10 Console
I don't have the Lock & Edit button in the WLS 10 Console. I know that this could be turned on and off in previous versions of WebLogic in the config.xml file, but I didn't find this anywhere in the documentation anymore.
Can anybody tell me how to make the Lock & Edit buton visible again in WebLogic 10.3a?
Thanx
PeterHere is my config.xml ( I guess I cannot just attach it):
<?xml version='1.0' encoding='UTF-8'?>
<domain xsi:schemaLocation="http://www.bea.com/ns/weblogic/920/domain.xsd" xmlns="http://www.bea.com/ns/weblogic/920/domain" 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" xmlns:xacml="http://www.bea.com/ns/weblogic/90/security/xacml">
<name>IOP5</name>
<domain-version>10.3.0.0</domain-version>
<security-configuration>
<name>IOP5</name>
<realm>
<!--
IA(X509)
CSPrincipal
B1
Test
ATN(LDAP)
[RealmAdapter]
InternalIA
-->
<sec:auditor xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-auditorType">
<sec:name>CSRealmCSAuditor</sec:name>
<prov:audit-logger-name>@audit.WLSAuditChannel</prov:audit-logger-name>
<prov:use-wls-log-handler>false</prov:use-wls-log-handler>
<prov:providers-logs-enabled>false</prov:providers-logs-enabled>
</sec:auditor>
<sec:authentication-provider xsi:type="wls:saml-identity-asserter-v2Type">
<sec:name>SAMLIdentityAsserter</sec:name>
<wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="prov:cssaml-authenticatorType" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xmlns:dom="http://www.bea.com/ns/WebLogic/920/domain" xmlns:xsi1="xsi">
<sec:name>CS SAML Authenticator</sec:name>
<sec:control-flag>OPTIONAL</sec:control-flag>
</sec:authentication-provider>
<!-- IBIP Configuration start -->
<!-- IBIP Configuration end -->
<sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-identity-asserterType">
<sec:name>CS Identity Asserter</sec:name>
<prov:credentials-validators>X.509=com.csg.cs.security.wls.authentication.pki.ext.CSPKICredentialValidator</prov:credentials-validators>
</sec:authentication-provider>
<sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-principal-authenticatorType">
<sec:name>CS Principal Authenticator</sec:name>
<sec:control-flag>OPTIONAL</sec:control-flag>
<prov:credential-validator>com.csg.cs.security.wls.authentication.pki.ext.CSPrincipalCredentialValidator</prov:credential-validator>
</sec:authentication-provider>
<sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:csb1-authenticatorType">
<sec:name>CS B1 Authenticator</sec:name>
<sec:control-flag>OPTIONAL</sec:control-flag>
<!-- @B1_KEYSTORE -->
</sec:authentication-provider>
<sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authenticatorType">
<sec:name>CS Authentication Provider</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
<prov:log-in-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:log-in-module-class-name>
<prov:assertion-module-class-name>com.csg.cs.security.wls.authentication.ldap.LDAPAtnLoginModuleImpl</prov:assertion-module-class-name>
</sec:authentication-provider>
<sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-internal-identity-asserterType">
<sec:name>CS Internal Identity Asserter</sec:name>
</sec:authentication-provider>
<sec:authentication-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-data-layer-providerType">
<sec:name>CS Data Layer Security Provider</sec:name>
<sec:control-flag>OPTIONAL</sec:control-flag>
<prov:key-alias>SYSTEM</prov:key-alias>
<prov:key-store-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-store-pass-phrase-encrypted>
<prov:key-pass-phrase-encrypted>{3DES}aqglyJbnET5qUuwQ1cujHw==</prov:key-pass-phrase-encrypted>
</sec:authentication-provider>
<sec:role-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-role-mapperType">
<sec:name>CS Role Mapper</sec:name>
<sec:role-deployment-enabled>true</sec:role-deployment-enabled>
<prov:is-debug>false</prov:is-debug>
<prov:application-role-mapper-class-name></prov:application-role-mapper-class-name>
</sec:role-mapper>
<sec:authorizer xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-authorizerType">
<sec:name>CS Authorization Provider</sec:name>
</sec:authorizer>
<sec:credential-mapper xsi:type="sam:saml2-credential-mapperType" xmlns:sam="http://www.bea.com/ns/weblogic/90/security/saml2">
<sec:name>SAML2CredentialMapper</sec:name>
<sam:issuer-uri>http://www.credit-suisse.com</sam:issuer-uri>
<sam:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</sam:name-qualifier>
<sam:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAML2NameMapperImpl</sam:name-mapper-class-name>
</sec:credential-mapper>
<sec:credential-mapper xsi:type="wls:saml-credential-mapper-v2Type" xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers">
<sec:name>SAMLCredentialMapper</sec:name>
<wls:issuer-uri>http://www.credit-suisse.com</wls:issuer-uri>
<wls:name-qualifier>CS_SWISS_TEST_PROTECTIONDOMAIN</wls:name-qualifier>
<wls:name-mapper-class-name>com.csg.cs.security.wls.authentication.saml.SAMLNameMapperImpl</wls:name-mapper-class-name>
</sec:credential-mapper>
<sec:credential-mapper xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cs-credential-mapperType">
<sec:name>CSCredentialMapper</sec:name>
</sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-provider xmlns:prov="http://www.credit-suisse.com/ns/wls10/security/providers" xsi:type="prov:cert-path-providerType">
<sec:name>CS Certificate Path Provider</sec:name>
<prov:cert-path-validator-class-name>com.csg.cs.security.wls.authentication.cert.ext.CSPKICertPathValidator</prov:cert-path-validator-class-name>
</sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:deploy-role-ignored>true</sec:deploy-role-ignored>
<sec:deploy-policy-ignored>true</sec:deploy-policy-ignored>
<sec:deploy-credential-mapping-ignored>false</sec:deploy-credential-mapping-ignored>
<sec:fully-delegate-authorization>true</sec:fully-delegate-authorization>
<sec:security-dd-model>Advanced</sec:security-dd-model>
<sec:name>CSRealm</sec:name>
<sec:delegate-m-bean-authorization>true</sec:delegate-m-bean-authorization>
</realm>
<default-realm>CSRealm</default-realm>
<anonymous-admin-lookup-enabled>true</anonymous-admin-lookup-enabled>
<credential-encrypted>{3DES}Zk0PFQd/y2JbBwcVCkoTVA==</credential-encrypted>
<connection-filter>com.csg.cs.security.wls.net.ConnectionFilterImpl</connection-filter>
<connection-logger-enabled>true</connection-logger-enabled>
</security-configuration>
<server>
<name>IOPWLS5</name>
<reverse-dns-allowed>true</reverse-dns-allowed>
<ssl>
<use-java>true</use-java>
<enabled>true</enabled>
<!-- JAP00002101 -->
<ciphersuite>TLS_RSA_WITH_RC4_128_SHA</ciphersuite>
<ciphersuite>TLS_RSA_WITH_3DES_EDE_CBC_SHA</ciphersuite>
<cert-authenticator></cert-authenticator>
<hostname-verifier>com.csg.cs.security.wls.net.SSL.ext.CSPKIHostNameVerifier</hostname-verifier>
<hostname-verification-ignored>false</hostname-verification-ignored>
<export-key-lifespan>500</export-key-lifespan>
<client-certificate-enforced>false</client-certificate-enforced>
<listen-port>7002</listen-port>
<two-way-ssl-enabled>true</two-way-ssl-enabled>
<server-private-key-alias>tipd.csintra.net</server-private-key-alias>
<server-private-key-pass-phrase-encrypted>{3DES}mQrgg0qTDHAhuU+2FACgZQ==</server-private-key-pass-phrase-encrypted>
<ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
<inbound-certificate-validation>BuiltinSSLValidationAndCertPathValidators</inbound-certificate-validation>
<outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
</ssl>
<log>
<rotate-log-on-startup>true</rotate-log-on-startup>
<logger-severity>Notice</logger-severity>
<stdout-severity>Notice</stdout-severity>
<log-file-filter xsi:nil="true" />
<stdout-filter xsi:nil="true" />
<domain-log-broadcast-severity>Notice</domain-log-broadcast-severity>
<domain-log-broadcast-filter xsi:nil="true" />
<memory-buffer-filter xsi:nil="true" />
<redirect-stdout-to-server-log-enabled>true</redirect-stdout-to-server-log-enabled>
<redirect-stderr-to-server-log-enabled>true</redirect-stderr-to-server-log-enabled>
</log>
<machine xsi:nil="true"></machine>
<listen-port>7001</listen-port>
<listen-port-enabled>true</listen-port-enabled>
<cluster xsi:nil="true"></cluster>
<web-server>
<!-- Portal Configuration start -->
<!-- Portal Configuration end -->
<send-server-header-enabled>false</send-server-header-enabled>
</web-server>
<iiop-enabled>false</iiop-enabled>
<listen-address>127.0.0.1</listen-address>
<staging-directory-name>./stage</staging-directory-name>
<classpath-servlet-disabled>true</classpath-servlet-disabled>
<key-stores>CustomIdentityAndCommandLineTrust</key-stores>
<custom-identity-key-store-file-name>./keystores/identity.properties</custom-identity-key-store-file-name>
<custom-identity-key-store-type>CS_PKI</custom-identity-key-store-type>
<custom-identity-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-identity-key-store-pass-phrase-encrypted>
<custom-trust-key-store-file-name>./keystores/trustedca.properties</custom-trust-key-store-file-name>
<custom-trust-key-store-type>CS_PKI</custom-trust-key-store-type>
<custom-trust-key-store-pass-phrase-encrypted>{3DES}DbuNFX1jQ5s=</custom-trust-key-store-pass-phrase-encrypted>
</server>
<embedded-ldap>
<name>IOP5</name>
<credential-encrypted>{3DES}nQpvTCkYlf4h4+8bAEI7JH8pg2Zo4uqNrVEu9bfYSr8=</credential-encrypted>
</embedded-ldap>
<administration-port-enabled>true</administration-port-enabled>
<administration-port>9999</administration-port>
<configuration-version>10.3.0.0</configuration-version>
<app-deployment>
<name>IOPA_root</name>
<target>IOPWLS5</target>
<source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/root.ear</source-path>
<!-- if a deployment plan is available ... -->
<security-dd-model>Advanced</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>IOPD_prsysmgmt</name>
<target>IOPWLS5</target>
<source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPD/prsysmgmt.ear</source-path>
<!-- if a deployment plan is available ... -->
<security-dd-model>Advanced</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>IOPC_prhelp</name>
<target>IOPWLS5</target>
<source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPC/prhelp.ear</source-path>
<!-- if a deployment plan is available ... -->
<security-dd-model>Advanced</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>IOPA_prpc_j2ee14</name>
<target>IOPWLS5</target>
<source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPA/prpc_j2ee14.ear</source-path>
<!-- if a deployment plan is available ... -->
<security-dd-model>Advanced</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>IOPB_prdbutil</name>
<target>IOPWLS5</target>
<source-path>C:\Apps\Tip50/cs/appsrv/app/IOP5/IOPB/prdbutil.ear</source-path>
<!-- if a deployment plan is available ... -->
<security-dd-model>Advanced</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<!-- UNPT 1.0 Library for IBIP WebService Support start -->
<!-- UNPT 1.0 Library for IBIP for WebService Support end -->
<!-- SAML 1.0 and SAML 2.0 Libraries for WebService Support start -->
<library>
<name>CSWSPolicySAML11#[email protected]</name>
<target>IOPWLS5</target>
<source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\WSS11SAML1WSPolicy.jar</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>Advanced</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>CSWSPolicySAML20#[email protected]</name>
<target>IOPWLS5</target>
<source-path>C:\cs\appsrv\bin\wl10.3a\wlfw\lib\SAML2WSPolicy.jar</source-path>
<deployment-order>1</deployment-order>
<security-dd-model>Advanced</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<!-- SAML 1.0 and SAML 2.0 Libraries for WebService Support end -->
<!-- external Libraries e.g. Portal Support start -->
<!-- external Libraries e.g. Portal Support end -->
<!-- internal shared Libraries start -->
<!-- internal shared Libraries end -->
<!-- Portal Configuration start -->
<!-- >>> TRACE >>> portalType=$portalType -->
<jms-server>
<name>PRJMS_Server</name>
<target>IOPWLS5</target>
</jms-server>
<jmx>
<management-ejb-enabled>false</management-ejb-enabled>
</jmx>
<shutdown-class>
<name>CSServerLifeCycleShutdown</name>
<target>IOPWLS5</target>
<class-name>com.csg.cs.security.wls.CSServerLifeCycleShutdown</class-name>
</shutdown-class>
<startup-class>
<name>CSServerLifeCycle</name>
<target>IOPWLS5</target>
<class-name>com.csg.cs.security.wls.CSServerLifeCycle</class-name>
<failure-is-fatal>true</failure-is-fatal>
<load-before-app-deployments>true</load-before-app-deployments>
<load-before-app-activation>false</load-before-app-activation>
</startup-class>
<!-- Portal Configuration end -->
<jms-system-resource>
<name>PRJMS_Module</name>
<target>IOPWLS5</target>
<sub-deployment>
<name>PRJMS_Subdeployment</name>
<target>PRJMS_Server</target>
</sub-deployment>
<sub-deployment>
<name>PRJMS_Subdeployment_Topic</name>
<target>PRJMS_Server</target>
</sub-deployment>
<descriptor-file-name>jms/prjms_module-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>IOPWLS5</admin-server-name>
<jdbc-system-resource>
<name>pega-rules</name>
<target>IOPWLS5</target>
<descriptor-file-name>jdbc/pega-rules-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<!-- Portal Configuration start -->
<!-- >>> TRACE >>> portalType=$portalType -->
<!-- Portal Configuration end -->
<webservice-security>
<name>default_wss</name>
<webservice-token-handler>
<name>CSTokenHandler</name>
<class-name>com.csg.cs.security.wls.authentication.wsee.TokenHandler</class-name>
<token-type>ut</token-type>
<handling-order>0</handling-order>
</webservice-token-handler>
</webservice-security>
</domain>
Regards
Peter -
Using Saml token profile 1.1 with WLS 10.3
Hi All
I am a Student from IITB. I am trying use message-level authentication for webservices using SAML Token Profile 1.1 on weblogic 10.3. I have done the necessary configuration but I am getting an error
"Unable to add Security Token for Identity ". I Started the SamlCredMapper Debug flag on from the console and saw the logs and I saw that everything is going fine untill at one place it
gives this error
<Debug> <SecuritySAMLCredMap> ' *<1245866312123> <BEA-000000> *<SAMLCredentialMapperV2: getCredentialInternal(): InvalidParameterException while validating parameters: weblogic.security.service.InvalidParameterException: Unable to generate SAML Assertion: No partner ID or target resource>**
I do not know how to fix this problem. Please Tell me if anyone has any idea about it.
Thanks
regards,
Sanyam
//The Logs are as follows
<Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310425> <BEA-000000> <SAMLCredentialMapperV2: getCredentialInternal(): initiator = Subject: 1
Principal = class weblogic.security.principal.WLSUserImpl("ssouser")
>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310425> <BEA-000000> <SAMLCredentialMapperV2: getCredentialInternal(): resource = (null)>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310426> <BEA-000000> <SAMLRPConfigManager.findPartnerInTargetMap():Searching with key 'sender-vouches:http://usmumsanygoyal1:7001/SSOTryService/SSOTestHelloWorld'>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310426> <BEA-000000> <SAMLRPConfigManager.findPartnerInTargetMap():Found partner 'rp_00001'>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310436> <BEA-000000> <SAMLNameMapperCache.getNameMapper: Not found name mapper in the cache, try to create one>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310437> <BEA-000000> <SAMLNameMapperCache.getNameMapper: create SAMLNameMapperImpl name mapper>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310439> <BEA-000000> <SAMLNameMapperImpl: mapSubject: No valid WLSGroup pricipals found in Subject, continuing>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310439> <BEA-000000> <SAMLNameMapperImpl: mapSubject: Mapped subject: qualifier: null, name: ssouser, groups: []>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310440> <BEA-000000> <SAMLCreateAssertion: Mapped subject 'Subject: 1
Principal = class weblogic.security.principal.WLSUserImpl("ssouser")
' to: username='ssouser',qualifier='null',format='urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified'>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310442> <BEA-000000> <SAMLCreateAssertion: No context or subject attribute were mapped>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310442> <BEA-000000> <SAMLCreateAssertion: Groups attribute statement requested but name mapper returned no groups -- groups attribute statement will not be generated>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310445> <BEA-000000> <SAMLCreateAssertion: Creating sender-vouches assertion>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310445> <BEA-000000> <SAMLCreateAssertion: Assertion IS signed>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310445> <BEA-000000> <SAMLCreateAssertion: KeyInfo IS NOT supplied>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310445> <BEA-000000> <SAMLCreateAssertion: AttrStmtInfo IS NOT supplied>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310460> <BEA-000000> <SAMLCreateAssertion: Created SAMLSubject for 'ssouser'>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310460> <BEA-000000> <SAMLCreateAssertion: Created SAMLSubject>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310475> <BEA-000000> <SAMLCreateAssertion: SAMLCreateAssertion: Cloning SAMLSubject>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310476> <BEA-000000> <SAMLCreateAssertion: SAMLCreateAssertion: Created SAMLAuthenticationStatement>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310484> <BEA-000000> <SAMLCreateAssertion: SAMLCreateAssertion: Signing assertion, keyinfo is included>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLLib> <[ACTIVE] : '1' for queue: ' <1245866310508> <BEA-000000> <SAMLSignedObject.sign(): algorithm 'http://www.w3.org/2000/09/xmldsig#rsa-sha1'>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLLib> <[ACTIVE] : '1' for queue: ' <1245866310509> <BEA-000000> <SAMLSignedObject.sign(): reference '#b21cfea8d3c90fee97a3100a59b0005e'>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLLib> <[ACTIVE] : '1' for queue: ' <1245866310509> <BEA-000000> <SAMLSignedObject.sign(): InclusiveNamespaces '#default saml samlp ds dsig code kind rw typens'>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLLib> <[ACTIVE] : '1' for queue: ' <1245866310542> <BEA-000000> <SAMLSignedObject.sign(): adding certificates>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLLib> <[ACTIVE] : '1' for queue: ' <1245866310556> <BEA-000000> <SAMLSignedObject.sign(): signing object>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLLib> <[ACTIVE] : '1' for queue: ' <1245866310706> <BEA-000000> <SAMLSignedObject.sign(): completed>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310706> <BEA-000000> <SAMLCreateAssertion: SAMLCreateAssertion: Signed assertion>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310706> <BEA-000000> <SAMLCreateAssertion: SAMLCreateAssertion: Created SAMLAssertion>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310706> <BEA-000000> <SAMLCreateAssertion: Returning assertion>
####<Jun 24, 2009 11:28:30 PM IST> <Debug> <SecuritySAMLCredMap> <[ACTIVE] : '1' for queue: ' <1245866310706> <BEA-000000> <SAMLCredentialMapperV2: getCredentialInternal(): Returning non-null credential>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311896> <BEA-000000> <SAMLIdentityAsserter: assertIdentity() called>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311897> <BEA-000000> <SAMLIdentityAsserter: SAMLIdentityAsserter: tokenType is 'SAML.Assertion.DOM'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311903> <BEA-000000> <SAMLAssertion: Assertion passed basic validity check>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311905> <BEA-000000> <SAMLAssertion: Target for assertion is: 'http://usmumsanygoyal1:7001/SSOTryService/SSOTestHelloWorld'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311905> <BEA-000000> <SAMLAssertion: Assertion issuer is: 'http://usmumsanygoyal1:7001/'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311906> <BEA-000000> <SAMLAssertion: Assertion subject confirmation method is: 'urn:oasis:names:tc:SAML:1.0:cm:sender-vouches'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311907> <BEA-000000> <SAMLAPConfigManager.findPartnerInTargetMap():Searching with key 'sender-vouches:http://usmumsanygoyal1:7001/&http://usmumsanygoyal1:7001/SSOTryService/SSOTestHelloWorld'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311907> <BEA-000000> <SAMLAPConfigManager.findPartnerInTargetMap():Found partner 'ap_00001'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311907> <BEA-000000> <SAMLAssertion: Found asserting party 'ap_00001'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311907> <BEA-000000> <SAMLAssertion: Assertion is signed>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLLib> ' <1245866311908> <BEA-000000> <SAMLTrustManager: Looking for certificate alias 'testalias'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLLib> ' <1245866311930> <BEA-000000> <SAMLTrustManager: Certificate was found>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLLib> ' <1245866311937> <BEA-000000> <SAMLSignedObject.verify(): key supplied>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLLib> ' <1245866311963> <BEA-000000> <SAMLSignedObject.verify(): obtained signed info>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLLib> ' <1245866311963> <BEA-000000> <SAMLSignedObject.verify(): validating signature>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLLib> ' <1245866311970> <BEA-000000> <SAMLSignedObject.verify(): completed>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311970> <BEA-000000> <SAMLAssertion: Signature verified using trusted certificate>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311977> <BEA-000000> <Got signing certificate for signed object: CN=Unknown, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311977> <BEA-000000> <SAMLAssertion: Assertion subject confirmation method is: 'urn:oasis:names:tc:SAML:1.0:cm:sender-vouches'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311977> <BEA-000000> <SAMLAssertion: Verified subject confirmation method>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311978> <BEA-000000> <SAMLAssertion: Assertion issuer is 'http://usmumsanygoyal1:7001/'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311978> <BEA-000000> <SAMLAssertion: Assertion issuer verified>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311980> <BEA-000000> <SAMLAssertion: Assertion contains NotBefore condition>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311980> <BEA-000000> <SAMLAssertion: Assertion contains NotOnOrAfter condition>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311980> <BEA-000000> <SAMLAssertion: NotBefore condition satisfied>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311980> <BEA-000000> <SAMLAssertion: NotOnOrAfter condition satisfied>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311981> <BEA-000000> <SAMLAssertion: Assertion has AudienceRestrictionCondition>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311981> <BEA-000000> <SAMLAssertion: Found matching audience 'http://usmumsanygoyal1:7001/'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311981> <BEA-000000> <SAMLAssertion: AudienceRestriction condition satisfied (matching audience)>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311981> <BEA-000000> <SAMLAssertion: Assertion has DoNotCache condition>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311981> <BEA-000000> <SAMLAssertion: Assertion conditions verified>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311986> <BEA-000000> <SAMLAssertion: Found subject for name: 'ssouser'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311987> <BEA-000000> <SAMLNameMapperCache.getNameMapper: Not found name mapper in the cache, try to create one>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311987> <BEA-000000> <SAMLNameMapperCache.getNameMapper: create SAMLNameMapperImpl name mapper>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311987> <BEA-000000> <SAMLAssertion: Looking for AttributeName 'Groups'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311987> <BEA-000000> <SAMLAssertion: Looking for AttributeNamespace 'urn:bea:security:saml:groups'>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311987> <BEA-000000> <SAMLAssertion: ProcessGroups is true but did not find expected groups attribute statement>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311988> <BEA-000000> <SAMLNameMapperCache.getNameMapper: Found name mapper in the cache>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311988> <BEA-000000> <SAMLNameMapperImpl: mapNameInfo: returning name: ssouser>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311989> <BEA-000000> <SAMLNameMapperImpl: mapGroupInfo: returning groups: null>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311989> <BEA-000000> <SAMLIACallbackHandler: SAMLIACallbackHandler(true, ssouser, null)>
####<Jun 24, 2009 11:28:31 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866311996> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(ssouser)>
####<Jun 24, 2009 11:28:32 PM IST> <Debug> <SecuritySAMLAtn> ' <1245866312002> <BEA-000000> <SAMLIACallbackHandler: callback[0]: NameCallback: setName(ssouser)>
####<Jun 24, 2009 11:28:32 PM IST> <Debug> <SecuritySAMLCredMap> ' <1245866312122> <BEA-000000> <SAMLCredentialMapperV2: getCredentials: Subject initiator>
####<Jun 24, 2009 11:28:32 PM IST> <Debug> <SecuritySAMLCredMap> ' <1245866312122> <BEA-000000> <SAMLCredentialMapperV2: getCredentials(Subject): getCredentialInternal() called>
_####<Jun 24, 2009 11:28:32 PM IST> <Debug> <SecuritySAMLCredMap> ' *<1245866312123> <BEA-000000> **<SAMLCredentialMapperV2: getCredentialInternal(): InvalidParameterException while validating parameters: weblogic.security.service.InvalidParameterException: Unable to generate SAML Assertion: No partner ID or target resource>**_*Client Side
<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://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/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:credential-mapper xsi:type="wls:saml-credential-mapper-v2Type">
<sec:name>SAMLCredentialMapper</sec:name>
<wls:issuer-uri>www.bea.com/demoSAML</wls:issuer-uri>
<wls:name-qualifier>bea.com</wls:name-qualifier>
<wls:signing-key-alias>testalias</wls:signing-key-alias>
<wls:default-time-to-live-delta>-30</wls:default-time-to-live-delta>
<wls:signing-key-pass-phrase-encrypted>{3DES}dOC15C42IEzCnN/klGIdyQ==</wls:signing-key-pass-phrase-encrypted>
</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:key-store xsi:type="wls:default-key-storeType">
<sec:name>keystore</sec:name>
</sec:key-store>
<sec:name>myrealm</sec:name>
</realm>
Server side
<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:authentication-provider xsi:type="wls:saml-identity-asserter-v2Type">
<sec:name>SAMLIdentityAsserter</sec:name>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://www.bea.com/ns/weblogic/90/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://www.bea.com/ns/weblogic/90/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>
</realm>
Sanyam -
WLS 6.1 on NT4: Strange HTTP NPE
Hello,
WebLogic version: 6.1 SP2
OS version: NT4 SP6
JDK: 1.3.1
We are having some problems when we try to establish a connection to our WLS server
with the following code:
URL url = new URL(urlString);
URLConnection con = url.openConnection();
((HttpURLConnection) con).getResponseCode();
An exception is thrown when we try to get the response code from the server:
java.lang.NullPointerException
at sun.net.www.http.ChunkedInputStream.readChunkSize(ChunkedInputStream.java:194)
at sun.net.www.http.ChunkedInputStream.prefill(ChunkedInputStream.java:219)
at sun.net.www.http.ChunkedInputStream.<init>(ChunkedInputStream.java:121)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:774)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:633)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:531)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:260)
at <our program code>
The same piece of code works with other app servers, so we assume that this might
be a WLS issue. Have you guys seen this exception before?
Any help would be highly appreciated.
Thank you,
Kevin
Try to access your URL from a web browser to see if it can go through. If not,
the problem is most likely at the servlet/jsp. If yes, try to add con.setRequestProperty("Host","your_wl_host:your_wl_port");
sometime, you also need add "User-Agent" like con.setRequestProperty("User-Agent",
"Mozilla/4.0
(compatible;
MSIE 6.0; Windows NT 5.0)");
You can also use some Sniffer to check the data communicated between browser and
the server, and add the contents in HTTP header part to your code as above.
On the other hand, you need know if the server side (servlet/jsp) expects you
to connect with HTTP POST. If so, you need con.setDoOutput(true); and send your
request data via outputstream.
"Kevin Sit" <[email protected]> wrote:
>
>Hello,
>
>WebLogic version: 6.1 SP2
>OS version: NT4 SP6
>JDK: 1.3.1
>
>We are having some problems when we try to establish a connection to
>our WLS server
>with the following code:
>
>URL url = new URL(urlString);
>URLConnection con = url.openConnection();
>((HttpURLConnection) con).getResponseCode();
>
>An exception is thrown when we try to get the response code from the
>server:
>
>java.lang.NullPointerException
> at sun.net.www.http.ChunkedInputStream.readChunkSize(ChunkedInputStream.java:194)
> at sun.net.www.http.ChunkedInputStream.prefill(ChunkedInputStream.java:219)
> at sun.net.www.http.ChunkedInputStream.<init>(ChunkedInputStream.java:121)
> at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:774)
> at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:633)
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:531)
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:260)
> at <our program code>
>
>The same piece of code works with other app servers, so we assume that
>this might
>be a WLS issue. Have you guys seen this exception before?
>
>Any help would be highly appreciated.
>
>Thank you,
>Kevin
-
BIweb service proxy JAX-RPC 1.1 method is not supported in WLS 8.1 clients
Hello
I have an application in oracle Application server and I'm migrating to weblogic 11g .
I have used web service proxy for BIPublisher 10.1.3.4 , careated by jdeveloper web service proxy wizard , when I want using it in weblogic , In corresponding form that uses BI Publisher web service proxy , I encounter following error :
"JAX-RPC 1.1 method is not supported in WLS 8.1 clients , if you attempting to run oc4j 10.1.3 JAX-RPC client in WLS,please see Web service Migration Guide for Instructions"
What should I do?
Regards
MehdiSpoke to dev and there was a bug logged, it seems to be down to Weblogic's implementation.
+This is pure WLS issue. The root cause of this problem is that Weblogic's
SAAJ implementation. No codechange on BIP server side
WLS 10 ships with two SAAJ implementations. By default the buggy 9.x
implementation is used (which lives in the package
weblogic.webservice.core.soap), but there is a new implementation, which
supports SAAJ 1.3 (which lives in the package weblogic.xml.saaj). I also
checked in a debugging jsp page, which could help looking at the DEBUG
logging to see which SAAJ implementation is used.
JSP testpage xmlponline/wwwroot/wsclient/soapclient-wls-8270711.jsp
To use this new version, you have to make sure setting the
-Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl
in startWebLogic script. +
Please give the solution a try and let me know if it works.
Regards
tim -
Problem with authorization after logout (adfc issue?)
Hi,
I have an application with implemented ADF Security, and navigation case login.jspx -> home defined in adfc-config.xml ("home" is the name of view activity, page is home.jspx),
logout is done through redirecting to /adfAuthentication?logout=true&end_url=/faces/login.jspx.
If I do the login & loguot repeatedly, after 6-7 times (sometimes 2-3, sometimes >10 but definitely happens) after logging in I get authorization exception saying I am not authorized to view home.jspx.
Note that on adfc-config.xml home.jspx is registered as "home", and if I type "home" in URL instead of "home.jspx", I can access the page.
Anybody seen similar behavior?
Thanks,
PedjaHere is a workaround:
Login button executes this code for authenticating against WLS
public String login() throws LoginException, IOException {
String un = (getUsername() == null ? "" : getUsername());
String pw = (getPassword() == null ? "" : getPassword());
FacesContext ctx = FacesContext.getCurrentInstance();
HttpServletRequest request = (HttpServletRequest)ctx.getExternalContext().getRequest();
CallbackHandler handler = new SimpleCallbackHandler(un, pw.getBytes());
try {
ServletAuthentication.login(handler, request);
} catch (FailedLoginException fle) {
FacesMessage msg = new FacesMessage(FacesMessage.SEVERITY_ERROR, " ", "Login error!"));
ctx.addMessage(null, msg);
return null;
return "success";
}If I call response.redirect("/faces/home") instead of returning a navigation action, the error can no longer be reproduced.
So, is this ADFc or ADFSecurity issue (adfAuthentication servlet gets confused)?
By the way, I'm using WLS's Default Authenticator, but this behavior has reproduced on few other applications, some of them use SQLAuthenticator, so this is not a WLS issue.
Pedja -
Oracle JDBC 8.1.7 XA prepare bug
Both Oracle JDBC 8.1.7 XA thin and oci drivers have a bug related to
the prepare fase of 2PC.
In some circunstances when loosing connection, the prepare fase cannot
be completed
but Oracle driver returns a successfull status, so WLS issues second
phase of commit
when it shouldn't. This is a known bug on Oracle.
Josep Blazquez.http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
Btw: the Oracle homepage does have a search function which will find that page using "download jdbc driver" as the search criteria. -
Oracle XA driver and isolation level
We have an Entity EJB that has isolation level specified in its
deployment descriptor and everything works fine if we use the non-XA
Oracle 9i driver.
However when we use the Oracle 9i Release 2 XA driver we get the
following exception:
java.sql.SQLException: Due to vendor limitations, setting transaction
isolation for "Oracle 8.1.7 XA" JDBC XA driver is not supported.
at
weblogic.jdbc.jta.DataSource.setTxIsolationFromTxProp(DataSource.java:1126)
at
weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1109)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:145)
at weblogic.jdbc.jta.Connection.getAutoCommit(Connection.java:247)
at
weblogic.jdbc.rmi.internal.ConnectionImpl.getAutoCommit(ConnectionImpl.java:173)
at
weblogic.jdbc.rmi.SerialConnection.getAutoCommit(SerialConnection.java:164)
Note the 8.1.7 version that the container prints. The driver is
definitely 9i and not 8.1.7 and it's the very first thing in the classpath.
Is this a problem with the driver really or is it a WLS issue?
Thanks,
DejanHi,
I removed the transaction isolation level setting from the deployment
descriptor and it works now as expected.
But in the meanwhile I also ran a test by using the driver directly
without Weblogic and I was able to successfully set the transaction
isolation level on the XA connections so I believe it's a Weblogic problem.
Dejan
Deyan D. Bektchiev wrote:
Yes,
We know about this but we just try to set it to the default one
(READ_COMMITED) which is probably redundant for Oracle but might not
be the default one for another DB vendor.
Here is the part of the deployment descriptor:
<transaction-isolation>
<isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
<method>
<ejb-name>Event</ejb-name>
<method-name>*</method-name>
</method>
</transaction-isolation>
Dejan
Slava Imeshev wrote:
Deyan,
I'm not 100% sure, but AFAIR oracle doesn't support all isolation
levels.
Which level do you set? Could you show us this part of the deployment
descriptor?
Slava
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
Thanks for the reply Sree,
Yes the 9i driver is the very first thing in the classpath as otherwise
we wouldn't even be able to connect to the 9i database with the 8.1.7
driver (we were getting lots of other exceptions when we were still
using the 8.1.7 driver).
I'll try removing the setting of the isolation level and I'll post the
result to the newsgroup.
Dejan
Sree Bodapati wrote:
hi Deyan,
java.sql.SQLException: Due to vendor limitations, setting
transaction
isolation for "Oracle 8.1.7 XA" JDBC XA driver is not supported.
should not have showed up with wrong version of oracle. If you can
verifiy
that the thin driver is the first thing in the classpath and you are
indeed
using the thin driver, This is a bug.
But in this case it looks like you need to remove the
TransactionIsolation
level from the EJB descriptor to get this to work. can you try that? I
will
forward this to one of our EJB engineers and see if we can get some
help
for
you.
sree
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
Sree,
We already did but the only answer we got was that the Oracle 9i
Release
2 driver was not at all supported by Weblogic 7.0 SP1.
But the certification page says that it is even certified...
So which one is true: The Oracle 9i Release 2 driver is not
supported or
is supported?
--dejan
Sree Bodapati wrote:
Please file a support case for this at [email protected]
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
We have an Entity EJB that has isolation level specified in its
deployment descriptor and everything works fine if we use the
non-XA
Oracle 9i driver.
However when we use the Oracle 9i Release 2 XA driver we get the
following exception:
java.sql.SQLException: Due to vendor limitations, setting
transaction
isolation for "Oracle 8.1.7 XA" JDBC XA driver is not supported.
at
weblogic.jdbc.jta.DataSource.setTxIsolationFromTxProp(DataSource.java:1126
at
weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1109)
at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:145)
at
weblogic.jdbc.jta.Connection.getAutoCommit(Connection.java:247)
at
weblogic.jdbc.rmi.internal.ConnectionImpl.getAutoCommit(ConnectionImpl.jav
a
>
173)
at
weblogic.jdbc.rmi.SerialConnection.getAutoCommit(SerialConnection.java:164
Note the 8.1.7 version that the container prints. The driver is
definitely 9i and not 8.1.7 and it's the very first thing in the
classpath.
Is this a problem with the driver really or is it a WLS issue?
Thanks,
Dejan -
As many HTTP sessions as Internet Explorer windows ?
Hi,
My web-application is using HttpSession to identify users (with this well known getSession() applied to HttpServletRequest).
I have noticed that if I open two (or more) Internet Explorer windows and I connect to my web-application, all of them share the same HTTP session.
That is annoying because some parameters stored in the session are different between the windows.
When I'm using IE in one window and Firefox in another, there are two separate sessions.
How can I do to have as many different HTTP sessions as IE Windows ?
Is it a WLS parameter ?
I'm using WLS 9.1.
Thanks a lot.This is not WLS issue. This is caused by the fact that different browser instances share a same cookie.
-
Hide the default page (index.jsp) from the url
I have configured weblogic to make certain pages such as index.jsp to
be a default page so that I can type in www.mydomain.com and it takes
me to www.mydomain.com/index.jsp. However, I would like for this page
to be hidden like it is on other web servers so that when I type
www.mydomain.com I get www.mydomain.com without showing the
"index.jsp" appended to the URL, even though it takes me to that page.
Is this possible? Please advise.
Thanks.
It's because WLS issues a redirect instead of forward.
I have to admit that this behaviour is not consistent with other
webservers. You might want to report this issue to [email protected]
An ugly workaround is to have a frond-end proxy/webserver and specify
the DefaultFileName or else live with the current problem ;-)
Kumar
web servers.
Daniel Chance wrote:
> I have configured weblogic to make certain pages such as index.jsp to
> be a default page so that I can type in www.mydomain.com and it takes
> me to www.mydomain.com/index.jsp. However, I would like for this page
> to be hidden like it is on other web servers so that when I type
> www.mydomain.com I get www.mydomain.com without showing the
> "index.jsp" appended to the URL, even though it takes me to that page.
> Is this possible? Please advise.
>
> Thanks.
>
-
New InitialContext() raises a NullPointerException
Hello gentlemen,
I have my code that is working nice under Weblogic 8.1 SP 2 and Service Pack 1 (Windows 2000, jdk141_03).
I switched to Service Pack 5 (no change in my code) and from then I face a strange NullPointerException when I make a call to
new InitialContext(hashtable).
(I am creating a Context for making a lookup on an EJB).
If I revert to Service Pack 2, everything works fine.
I checked Service Pack 6 too (jdk142_11) and I got the same NullPointerException.
I am quite in troubles...
thank you for your help.
Edited by [email protected] at 01/18/2007 3:34 AMfranco lazzari wrote:
Here it is:
java.lang.NullPointerException
at weblogic.rjvm.RJVMManager.findExisting(RJVMManager.java:326)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:210)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:184)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:223Odd. The line of code in 81sp5 that supposedly throws an NPE (line 326)
can't do that in the code I'm looking at. I suggest you open an official
support case showing this full stacktrace. It presents as a core WLS
issue.
Joe
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:188)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:310)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:253)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at mnse.securityserver.utenti.GestoreUtentiCentrale.getToken(GestoreUten
tiCentrale.java:798)
at mnse.securityserver.utenti.GestoreUtentiCentrale.<init>(GestoreUtenti
Centrale.java:82)
at mnse.securityserver.utenti.GestoreUtentiCentrale.createGestoreUtenti(
GestoreUtentiCentrale.java:72)
at mnse.securityserver.utenti.GestoreUtentiCentrale.getGestoreUtenti(Ges
toreUtentiCentrale.java:51)
at mnse.securityserver.utenti.GestoreFontiCentrale.caricaFonteUtenti(Ges
toreFontiCentrale.java:216)
at mnse.securityserver.utenti.GestoreFontiCentrale.<init>(GestoreFontiCe
ntrale.java:89)
at mnse.securityserver.utenti.GestoreFontiCentrale.createGestoreFonti(Ge
storeFontiCentrale.java:62)
at mnse.securityserver.utenti.GestoreFontiCentrale.getGestoreFonti(Gesto
reFontiCentrale.java:46)
at mnse.util.avvio.SecurityLoader.load(SecurityLoader.java:392)
at mnse.util.avvio.SecurityLoader.getMinosseLogfile(SecurityLoader.java:
118)
at mnse.securityserver.logger.MinosseLogger.<init>(MinosseLogger.java:52
at mnse.securityserver.logger.MinosseLogger.createLogger(MinosseLogger.j
ava:95)
at mnse.securityserver.logger.MinosseLogger.getLogger(MinosseLogger.java
:82)
at mnse.util.avvio.TimeStamper.getLDAPServerURL(TimeStamper.java:58)
at mnse.admin.dao.RacsDAO.<init>(RacsDAO.java:59)
at mnse.admin.impl.AdministratorEJB.getOperatore(AdministratorEJB.java:5
1)
at mnse.admin.impl.Administrator_ocrjs3_EOImpl.getOperatore(Administrato
r_ocrjs3_EOImpl.java:316)
at mnse.admin.impl.Administrator_ocrjs3_EOImpl_CBV.getOperatore(Unknown
Source)
at mnse.console.AdministratorProxy.getOperatore(AdministratorProxy.java:
85)
at mnse.console.Controllore.getOperatore(Controllore.java:122)
at mnse.console.Controllore.esegui(Controllore.java:89)
at mnse.console.Short.doPost(Short.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1077)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:7047)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3902)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2773)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) -
Error "The current garbage collector has no nursery"
Has anybody any information on the error message "The current garbage collector has no nursery"? We received the following error message after starting the WLS in production mode:
<2006-jan-25 kl 17:57 CET> <Error> <Management> <BEA-140001> <An error occurred while getting attribute TotalNurserySize on MBean se-i-ld09:Location=se-i-ld09-c01-s01,Name=se-i-ld09-c01-s01,ServerRuntime=se-i-ld09-c01-s01,Type=JRockitRuntime. Method: public long weblogic.t3.srvr.JRockitRuntime.getTotalNurserySize(). Exception: com.bea.jvm.NotAvailableException: The current garbage collector has no nursery..
com.bea.jvm.NotAvailableException: The current garbage collector has no nursery.
at jrockit.management.jvm.GarbageCollectorImpl.getNurserySize()J(Unknown Source)
at weblogic.t3.srvr.JRockitRuntime.getTotalNurserySize()J(JRockitRuntime.java:112)
at jrockit.reflect.NativeMethodInvoker.invoke0(Ljava.lang.Object;ILjava.lang.Object;[Ljava.lang.Object&)Ljava.lang.Object;(Unknown Source)
at jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object&)Ljava.lang.Object;(Optimized Method)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object&)Ljava.lang.Object;(Optimized Method)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Optimized Method)
at weblogic.management.internal.DynamicMBeanImpl.getAttribute(Ljava.lang.String&)Ljava.lang.Object;(DynamicMBeanImpl.java:574)
at com.sun.management.jmx.MBeanServerImpl.getAttribute(Ljava.lang.Object;Ljava.lang.String&)Ljava.lang.Object;(MBeanServerImpl.java:1183)
at com.sun.management.jmx.MBeanServerImpl.getAttribute(Ljavax.management.ObjectName;Ljava.lang.String&)Ljava.lang.Object;(MBeanServerImpl.java:1153)
at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(Ljavax.management.ObjectName;Ljava.lang.String&)Ljava.lang.Object;(RemoteMBeanServerImpl.java:287)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(ILweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundResponse;Ljava.lang.Object&)Lweblogic.rmi.spi.OutboundResponse;(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundResponse&)V(BasicServerRef.java:477)
at weblogic.rmi.internal.BasicServerRef$1.run()Ljava.lang.Object;(BasicServerRef.java:420)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedExceptionAction&)Ljava.lang.Object;(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedExceptionAction&)Ljava.lang.Object;(SecurityManager.java:144)
at weblogic.rmi.internal.BasicServerRef.handleRequest(Lweblogic.rmi.spi.InboundRequest&)V(BasicServerRef.java:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(Lweblogic.kernel.ExecuteThread&)V(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest&)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread&)V(Unknown Source)>
Thanks in advance for your help - it is much appreciated!
Cheers, JonasThis exception is thrown by the JRockit Management API when querying the nursery size of a GC that has no nursery (single-generational GC). The logical place to catch the error would be in the weblogic.t3.srvr.JRockitRuntime.getTotalNurserySize() method, which implies that it is a WLS issue.
Maybe it has been fixed in a later WLS 8.1 service pack?
If you run with a generational GC, i.e. "-Xgc:gencon" the error will go away, but that has larger implications on the behavior of your app so it should not be used as a workaround. -
Oracle Access Manager login Problem
Hi All,
I am installed IDM 11g(11.5) in my local machine. All servers are up and running(SOA,IDM and OAM).
I am able to login IDM but the problem is I am unable to login OAM using below URLs"http://http://localhost:14100/oam/" or "http://http://localhost:14100/oamconsole"
I got below error Could you please help me on this.
Thanks in advance.
index.jsp:4:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://beehive.apache.org/netui/tags-template-1.0" prefix="netui-template"%>
^----^
at weblogic.servlet.jsp.JavelinxJSPStub.reportCompilationErrorIfNeccessary(JavelinxJSPStub.java:226)
at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:162)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:256)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:416)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:326)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:265)
at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:133)
at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:120)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Jul 28, 2012 11:35:47 AM GMT+05:30> <Notice> <Diagnostics> <mindview> <oam_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <80fd87e7b2933795:7c4c4c55:138cc2c328f:-8000-0000000000000079> <1343455547428> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'oam_server1' has triggered at Jul 28, 2012 11:35:47 AM GMT+05:30. Notification details:
WatchRuleType: Log
WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-101020') OR (MSGID = 'WL-101017') OR (MSGID = 'WL-000802') OR (MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
WatchData: DATE = Jul 28, 2012 11:35:47 AM GMT+05:30 SERVER = oam_server1 MESSAGE = [ServletContext@335684[app:oam_server module:oam path:/oam spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl@fab370[
GET /oam/index.jsp HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:9.0) Gecko/20100101 Firefox/9.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Connection: keep-alive
Cookie: oimjsessionid=GShlQTQG2mnJ3L2WpHlnm5QnJ0q2G94LzBBQdLRg7rGJhyTLvSlb!2089492751
]] Root cause of ServletException.
weblogic.servlet.jsp.CompilationException: Failed to compile JSP /index.jsp
index.jsp:2:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://beehive.apache.org/netui/tags-html-1.0" prefix="netui"%>
^----^
index.jsp:2:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://beehive.apache.org/netui/tags-html-1.0" prefix="netui"%>
^----^
index.jsp:3:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://beehive.apache.org/netui/tags-databinding-1.0" prefix="netui-data"%>
^----^
index.jsp:3:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://beehive.apache.org/netui/tags-databinding-1.0" prefix="netui-data"%>
^----^
index.jsp:4:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://beehive.apache.org/netui/tags-template-1.0" prefix="netui-template"%>
^----^
index.jsp:4:4: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file.
<%@taglib uri="http://beehive.apache.org/netui/tags-template-1.0" prefix="netui-template"%>
^----^
at weblogic.servlet.jsp.JavelinxJSPStub.reportCompilationErrorIfNeccessary(JavelinxJSPStub.java:226)
at weblogic.servlet.jsp.JavelinxJSPStub.compilePage(JavelinxJSPStub.java:162)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:256)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:216)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:243)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:416)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:326)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.am.agent.wls.filters.OAMServletAuthenticationFilter.doFilter(OAMServletAuthenticationFilter.java:265)
at oracle.security.am.agent.wls.filters.OAMValidationSystemFilter.doFilter(OAMValidationSystemFilter.java:133)
at oracle.security.wls.oamagent.OAMAgentWrapperFilter.doFilter(OAMAgentWrapperFilter.java:120)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101017 MACHINE = mindview TXID = CONTEXTID = 80fd87e7b2933795:7c4c4c55:138cc2c328f:-8000-0000000000000078 TIMESTAMP = 1343455547412
WatchAlarmType: AutomaticReset
WatchAlarmResetPeriod: 30000
>
####<Jul 28, 2012 11:35:52 AM GMT+05:30> <Alert> <Diagnostics> <mindview> <oam_server1> <oracle.dfw.impl.incident.DiagnosticsDataExtractorImpl - Incident Dump Executor (created: Sat Jul 28 11:35:49 GMT+05:30 2012)> <<WLS Kernel>> <> <80fd87e7b2933795:7c4c4c55:138cc2c328f:-8000-0000000000000087> <1343455552522> <BEA-320016> <Creating diagnostic image in c:\oracle\middleware\user_projects\domains\base_domain\servers\oam_server1\adr\diag\ofm\base_domain\oam_server1\incident\incdir_5 with a lockout minute period of 1.>
####<Jul 28, 2012 11:37:31 AM GMT+05:30> <Info> <Health> <mindview> <oam_server1> <weblogic.GCMonitor> <<anonymous>> <> <80fd87e7b2933795:7c4c4c55:138cc2c328f:-8000-0000000000000071> <1343455651787> <BEA-310002> <67% of the total memory in the server is free>
####<Jul 28, 2012 11:45:46 AM GMT+05:30> <Info> <JDBC> <mindview> <oam_server1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <80fd87e7b2933795:7c4c4c55:138cc2c328f:-8000-000000000000008a> <1343456146959> <BEA-001128> <Connection for pool "oamDS" closed.>
Thanks in Advance.
Regards,
Ravi.Hi Ravi,
this looks like a WLS issue.
1-You can try as a workaround to remove this validator configuration in taglib definition file: .tld and see the behavior.
2-Or you are missing something into url.
I hope this helps,
Thiago Leoncio. -
I have an 11G portal environment that has a portal app/server and several non-portal apps/servers in it. All the libraries are deployed to my admin server and my portal cluster. Some of my managed servers also have SOME libraries bound to them as well. What I have noticed is that sometimes I can deploy a non-portal app that has some libraries deployed to it and upon completion of the deployment some, most or all of the libraries are in a 'new' status. The only way to get the libraries back 'active' is to restart ALL of the managed servers that have ANY libraries bound to them, including the portal managed servers. Has anyone else seen this? Any fix suggestions?
It appears that these libraries status is heavily tied to their condition of the managed servers. Since this is relatively new in 11g I just want to know others experience on this. I would have (and may still) log this call to a portal forum but know it is still basically a WLS issue since librarie deployment shoudl be the same in both.
Thanks for help, I have points!The PS files are just 4 layers of text. Its the same text throughout but some are there and most aren't, so if the font was missing it shouldn't be anywhere.
Does FCP need the font though? I thought it would be embedded in the PS file. I never have had a font not show up.
And if its in the Library, how can I then relink the file? Do I have to move it outside of the Library?
Thanks -
We are having an issue with our WLP 10.3.2 environment where the admin takes a while to startup. It is installed as a Windows service and always started within a couple of minutes until recently. No known changes that would affect this. Look at the logging below....the server showed running at 8:12 am shortly after last log entry below. Notice the 3 minute gaps at 8:06 and 8:09am. I would assume this is where the delay is but not sure as we saw this same entries in the logs when it started quicker, however, there were not large gaps in time like there is now. Let me know if you have any ideas, thanks.
####<May 28, 2013 8:06:54 AM CDT> <Notice> <Security> <qaportal1> <AdminServer> <ConnSetupMgr ldaps://qaadmserver1.fcqa.com:636> <<anonymous>> <> <> <1369746414936> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<May 28, 2013 8:06:54 AM CDT> <Notice> <Security> <qaportal1> <AdminServer> <ConnSetupMgr ldaps://qaadmserver1.fcqa.com:636> <<anonymous>> <> <> <1369746414936> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<May 28, 2013 8:06:55 AM CDT> <Notice> <Security> <qaportal1> <AdminServer> <ConnSetupMgr ldaps://qaadmserver1.fcqa.com:636> <<anonymous>> <> <> <1369746415014> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
####<May 28, 2013 8:09:39 AM CDT> <Notice> <Security> <qaportal1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1369746579092> <BEA-090082> <Security initializing using security realm myrealm.>
####<May 28, 2013 8:12:13 AM CDT> <Notice> <WebLogicServer> <qaportal1> <AdminServer> <main> <<WLS Kernel>> <> <> <1369746733452> <BEA-000365> <Server state changed to STANDBY>
####<May 28, 2013 8:12:13 AM CDT> <Notice> <WebLogicServer> <qaportal1> <AdminServer> <main> <<WLS Kernel>> <> <> <1369746733452> <BEA-000365> <Server state changed to STARTING>No real changes, we added an ADAM server to the provider list but it didn't seem to be a fix when I removed it....thanks.
<security-configuration>
<name>QA11</name>
<realm>
<sec:authentication-provider xsi:type="wls:iplanet-authenticatorType">
<sec:name>ADAM</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
<wls:host>qaadmserver1.fcqa.com qaadmserver2.fcqa.com</wls:host>
<wls:port>636</wls:port>
<wls:user-object-class>user</wls:user-object-class>
<wls:ssl-enabled>true</wls:ssl-enabled>
<wls:user-name-attribute>cn</wls:user-name-attribute>
<wls:principal>cn=administrator,cn=users,dc=client,dc=fcqa,dc=com</wls:principal>
<wls:user-base-dn>cn=users,dc=client,dc=fcqa,dc=com</wls:user-base-dn>
<wls:credential-encrypted>bs</wls:credential-encrypted>
<wls:user-from-name-filter>(&(cn=%u)(objectclass=user))</wls:user-from-name-filter>
<wls:cache-size>64</wls:cache-size>
<wls:cache-ttl>30</wls:cache-ttl>
<wls:group-base-dn>cn=users,dc=client,dc=fcqa,dc=com</wls:group-base-dn>
<wls:group-from-name-filter>(&(cn=%g)(objectclass=group))</wls:group-from-name-filter>
<wls:static-group-object-class>group</wls:static-group-object-class>
<wls:parallel-connect-delay>10</wls:parallel-connect-delay>
<wls:connection-retry-limit>2</wls:connection-retry-limit>
<wls:static-member-dn-attribute>member</wls:static-member-dn-attribute>
<wls:connection-pool-size>100</wls:connection-pool-size>
<wls:static-group-dns-from-member-dn-filter>(&(member=%M)(objectclass=group))</wls:static-group-dns-from-member-dn-filter>
<wls:dynamic-group-object-class></wls:dynamic-group-object-class>
<wls:dynamic-group-name-attribute></wls:dynamic-group-name-attribute>
<wls:dynamic-member-url-attribute></wls:dynamic-member-url-attribute>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:active-directory-authenticatorType">
<sec:name>Active Directory</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
<wls:host>qaadserver1 qaadserver2</wls:host>
<wls:port>636</wls:port>
<wls:ssl-enabled>true</wls:ssl-enabled>
<wls:user-name-attribute>sAMAccountName</wls:user-name-attribute>
<wls:principal>cn=administrator,cn=users,dc=fcqa,dc=com</wls:principal>
<wls:user-base-dn>ou=HomeOfficeUsers,dc=FCQA,dc=COM</wls:user-base-dn>
<wls:credential-encrypted>bs</wls:credential-encrypted>
<wls:user-from-name-filter>(&(sAMAccountName=%u)(objectclass=user))</wls:user-from-name-filter>
<wls:group-base-dn>cn=Users,dc=FCQA,dc=COM</wls:group-base-dn>
<wls:parallel-connect-delay>5</wls:parallel-connect-delay>
<wls:connection-retry-limit>2</wls:connection-retry-limit>
<wls:connection-pool-size>15</wls:connection-pool-size>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:active-directory-authenticatorType">
<sec:name>FCHQA AD Realm</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
<wls:host>qafchadserver1 qafchadserver2</wls:host>
<wls:port>636</wls:port>
<wls:user-name-attribute>sAMAccountName</wls:user-name-attribute>
<wls:principal>cn=administrator,cn=users,dc=fchqa,dc=fcqa,dc=com</wls:principal>
<wls:user-base-dn>ou=HomeOfficeUsers,dc=FCHQA,dc=FCQA,dc=COM</wls:user-base-dn>
<wls:credential-encrypted>bs</wls:credential-encrypted>
<wls:user-from-name-filter>(&(sAMAccountName=%u)(objectclass=user))</wls:user-from-name-filter>
<wls:group-base-dn>cn=Users,dc=FCHQA,dc=FCQA,dc=COM</wls:group-base-dn>
<wls:parallel-connect-delay>5</wls:parallel-connect-delay>
<wls:connection-retry-limit>2</wls:connection-retry-limit>
<wls:connection-pool-size>15</wls:connection-pool-size>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:sql-authenticatorType">
<sec:control-flag>SUFFICIENT</sec:control-flag>
<wls:data-source-name>p13nDataSource</wls:data-source-name>
</sec:authentication-provider>
<sec:authentication-provider xmlns:wsrp="http://www.bea.com/ns/wlp/90/security/wsrp" xsi:type="wsrp:wsrp-identity-asserterType">
<sec:name>WSRPIdentityAsserter</sec:name>
<sec:active-type>WSRPPerimeterAtnToken</sec:active-type>
<sec:base64-decoding-required>false</sec:base64-decoding-required>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:name>DefaultIdentityAsserter</sec:name>
<sec:active-type>X.509</sec:active-type>
<sec:active-type>wsse:PasswordDigest</sec:active-type>
<wls:use-default-user-name-mapper>true</wls:use-default-user-name-mapper>
<wls:default-user-name-mapper-attribute-type>CN</wls:default-user-name-mapper-attribute-type>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:saml-identity-asserter-v2Type">
<sec:name>SAMLIdentityAsserter</sec:name>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:saml-authenticatorType">
<sec:name>SAMLAuthenticator</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-authenticatorType">
<sec:name>defaultauth</sec:name>
<sec:control-flag>OPTIONAL</sec:control-flag>
</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:credential-mapper xsi:type="wls:saml-credential-mapper-v2Type">
<sec:name>SAMLCredentialMapper</sec:name>
<wls:issuer-uri>http://www.bea.com/wsrp/saml</wls:issuer-uri>
<wls:name-qualifier>wsrpConsumer</wls:name-qualifier>
<wls:signing-key-alias>wsrpconsumerrsa</wls:signing-key-alias>
<wls:default-time-to-live>2700</wls:default-time-to-live>
<wls:default-time-to-live-delta>-900</wls:default-time-to-live-delta>
<wls:cred-cache-size>1000</wls:cred-cache-size>
<wls:cred-cache-min-viable-ttl>1800</wls:cred-cache-min-viable-ttl>
<wls:signing-key-pass-phrase-encrypted>bs</wls:signing-key-pass-phrase-encrypted>
</sec:credential-mapper>
<sec:credential-mapper xsi:type="wls:pki-credential-mapperType">
<sec:name>PKICredentialMapper</sec:name>
<wls:key-store-file-name>wsrpKeystore.jks</wls:key-store-file-name>
<wls:key-store-pass-phrase-encrypted>bs</wls:key-store-pass-phrase-encrypted>
</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:user-lockout-manager>
<sec:lockout-enabled>true</sec:lockout-enabled>
<sec:lockout-threshold>8</sec:lockout-threshold>
<sec:lockout-duration>30</sec:lockout-duration>
<sec:lockout-reset-duration>5</sec:lockout-reset-duration>
<sec:lockout-cache-size>5</sec:lockout-cache-size>
<sec:lockout-gc-threshold>400</sec:lockout-gc-threshold>
</sec:user-lockout-manager>
<sec:enable-web-logic-principal-validator-cache>true</sec:enable-web-logic-principal-validator-cache>
<sec:max-web-logic-principals-in-cache>500</sec:max-web-logic-principals-in-cache>
<sec:name>myrealm</sec:name>
<sec:rdbms-security-store>
<sec:username>BEA10</sec:username>
<sec:password-encrypted>bs</sec:password-encrypted>
<sec:connection-url>jdbc:oracle:thin:@QAOracleDB:1521:PORTQA</sec:connection-url>
<sec:driver-name>oracle.jdbc.OracleDriver</sec:driver-name>
<sec:connection-properties>user=BEA10</sec:connection-properties>
<sec:jms-topic>p13n.security.RDBMSSecurityStoreTopic</sec:jms-topic>
<sec:jms-topic-connection-factory>weblogic.jms.ConnectionFactory</sec:jms-topic-connection-factory>
<sec:jms-exception-reconnect-attempts>15</sec:jms-exception-reconnect-attempts>
<sec:notification-properties>java.naming.provider.url=t3://10.5.110.227:7011,java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory</sec:notification-properties>
<sec:name>p13nRDBMSSecurityStore</sec:name>
</sec:rdbms-security-store>
<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>
<anonymous-admin-lookup-enabled>false</anonymous-admin-lookup-enabled>
<credential-encrypted>bs</credential-encrypted>
<web-app-files-case-insensitive>false</web-app-files-case-insensitive>
<compatibility-connection-filters-enabled>false</compatibility-connection-filters-enabled>
<node-manager-username>beaadmin</node-manager-username>
<node-manager-password-encrypted>bs</node-manager-password-encrypted>
<principal-equals-case-insensitive>false</principal-equals-case-insensitive>
<principal-equals-compare-dn-and-guid>false</principal-equals-compare-dn-and-guid>
<downgrade-untrusted-principals>false</downgrade-untrusted-principals>
<enforce-strict-url-pattern>true</enforce-strict-url-pattern>
<cross-domain-security-enabled>false</cross-domain-security-enabled>
</security-configuration>
Maybe you are looking for
-
Continuous Error Message: Dell Support Center Has Stopped Working
I have Windows V8ista on an Inspiron530s. Through out any operation I continue to get the following massage: "Dell Support Center Has Stopped Working
-
Problem writing file ANSI to UTF-8. OPEN DATASET FOR OUTPUT IN TEXT MODE
Hello everybody, My report needs to create a file in ANSI so I am using this sentence: * "OPEN DATASET p_dir_a FOR OUTPUT IN TEXT MODE ENCODING DEFAULT."* almost all charters in the file are well generating excepting for this two: ( Á ) & ( Í ) bec
-
Help needed regarding the updation of "Relationships" in BP
Hello Guys, This is to request you to kindly help me regarding the following. We have a scenario where all the employees assigned to an Organizational unit (in PPOMA_CRM) are not showing in the "Relationships" ("Has Employee")in the BP transaction of
-
Will it be OK, install APPCS3 together with AP65 in one system ?
Dear readers, for some reason, I'd like to install AP65 too within my system which already had APPCS3. One of the reason is, APPCS3 won't export back my huffyuv avi footage generated by AE to huffyuv AVI file, while AP65 did even without recompressio
-
Deployment software windows update
HI, I created a deployment software windows update I sent it to the station -in the monitor ,It shows me that it has been installed But the station did not receive a warning of something installed, I looked in software center and there does not app