SAML SSO: SAMLServlet samlits Partner Not found - weblogic.developer.interest.webservices.databinding(Archived)

I'm using Vikrant Sawant's "Configuring Single Sign-On using SAML in Weblogic Server 9.2" sample to prototype our SAML-SSO test between WL92<->WL92.
I believe I follwed every step the sample says and I checked, re-sheck everything.
Still, I'm not able to complete the single login in and getting the following error::O
<SAMLServlet (samlits): Initializing SAML samlits service>
<SAMLServlet (samlits): Getting source site helper instance>
<SAMLSourceSite: init(): Assertion store is version 2, will verify destination sites>
<SAMLServlet (samlits): Got source site helper instance>
<SAMLServlet (samlits): SAML samlits service initialized>
<SAMLServlet (samlits): doGet(): Request URI is '/samlits_ba/its'>
<SAMLServlet (samlits): doGet(): Servlet URI is '/its'>
<SAMLServlet (samlits): doGet(): Partner not found, returning FORBIDDEN>
I wish somwone can help me out!
Thanks a lot!
James 

Hello,
I am also experiencng some problems with this example. Have solved your problem? 

Hi,
I'm not using that profile/scenario, but I am having a similar problem with the sender-vouches profile. See:
http://forums.bea.com/bea/thread.jspa?threadID=300000485&tstart=0&mod=1182109740419
Has anyone figured this out?
Jim

Related

getting WsdlException while deploying application

Hi
Have been trying to use remote portlet, but even after repeatedly checking the configuration file, unable to locate the cause of the below error while deploying the PortalWeb.war application.
<May 25, 2011 4:38:14 PM IST> <Warning> <com.bea.wlw.netui.pageflow.internal.WebLogicURLTemplateFactory> <BEA-000000> <In webapp <OCOEPortalWeb>, the url template <http://{url:domain}:{url:port}/{url:path}?{url:queryString}> uses the {url:port} token. The system may not pick up the correct ports if you are using a proxy server. Consider hardcoding the ports in a production environment.>
weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '127.0.0.1', port: '7101'
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)
at weblogic.wsee.wsdl.internal.WsdlDefinitionsImpl.parse(WsdlDefinitionsImpl.java:432)
at weblogic.wsee.wsdl.internal.WsdlDefinitionsImpl.parse(WsdlDefinitionsImpl.java:417)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:81)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:108)
at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:41)
at com.bea.wsrp.wsdl.FixupWsdlParser.parse(FixupWsdlParser.java:75)
at com.bea.wsrp.wsdl.WsdlInfoImpl.<init>(WsdlInfoImpl.java:216)
at com.bea.wsrp.wsdl.GlobalWsdlPool.getWsdlInfo(GlobalWsdlPool.java:53)
at com.bea.wsrp.config.ProducerInfo.isPortletManagementSupported(ProducerInfo.java:574)
at com.bea.wsrp.consumer.management.portlet.ProxyPortletRemoveListener$ProxyPortletRemover.run(ProxyPortletRemoveListener.java:348)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wsrp.consumer.management.portlet.ProxyPortletRemoveListener.handleNotification(ProxyPortletRemoveListener.java:199)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:257)
at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:322)
at javax.management.NotificationBroadcasterSupport$1.execute(NotificationBroadcasterSupport.java:307)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:229)
at javax.management.timer.Timer.sendNotification(Timer.java:1237)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1206)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1289)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '127.0.0.1', port: '7101'
at weblogic.net.http.HttpClient.openServer(HttpClient.java:321)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:411)
at weblogic.net.http.HttpClient.New(HttpClient.java:241)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:176)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:361)
at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:36)
at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:106)
at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
... 22 more
Please find the entry of the "wsrp-producer-registry.xml"
<?xml version="1.0" encoding="UTF-8"?>
<wsrp-producer-registry
xmlns="http://www.bea.com/servers/weblogic/wsrp-producer-registry/9.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/servers/weblogic/wsrp-producer-registry/9.0 wsrp-producer-registry.xsd"
offer-extensions="true">
<!-- The offer-extensions attribute above indicates whether the consumer can send messges to WLP-extended Web
Service ports -->
<!-- Upload limit (in bytes) -->
<upload-read-limit>1048576</upload-read-limit>
<!-- Some producers may not be able to handle attachments sent as a single part. If this is the case, set
this to true -->
<send-upload-as-several-parts>false</send-upload-as-several-parts>
<!-- Timeout value for establishing a connection -->
<connection-establishment-timeout-msecs>-1</connection-establishment-timeout-msecs>
<!-- Connection (read) timeout (in milli seconds) -->
<connection-timeout-msecs>120000</connection-timeout-msecs>
<!-- Enable/disable local proxy -->
<enable-local-proxy>false</enable-local-proxy>
<!-- Release sessions upon session expiry on the consumer -->
<explicitly-release-sessions>true</explicitly-release-sessions>
<!-- Add wsrp-producer elements here -->
<!-- URL templates for producer writing of URLs -->
<url-templates>
<url-template-ref type="default" name="wsrp-default"/>
<url-template-ref type="blockingAction" name="wsrp-blockingAction"/>
<url-template-ref type="secureBlockingAction" name="wsrp-secureBlockingAction"/>
<url-template-ref type="resource" name="wsrp-resource"/>
<url-template-ref type="secureResource" name="wsrp-secureResource"/>
<url-template-ref type="render" name="wsrp-render"/>
<url-template-ref type="secureRender" name="wsrp-secureRender"/>
<url-template-ref type="resource" name="wsrp-resource"/>
<url-template-ref type="secureResource" name="wsrp-secureResource"/>
<url-template-ref type="standalone" name="wsrp-default"/>
<url-template-ref type="secureStandalone" name="wsrp-secureDefault"/>
<url-template-ref type="secureDefault" name="wsrp-secureDefault"/>
</url-templates>
<rewrite-mime-types>
<mime-type>text/*</mime-type>
<mime-type>application/x-javascript</mime-type>
<mime-type>application/xml+xhtml</mime-type>
<mime-type>application/xml</mime-type>
<mime-type>application/javascript</mime-type>
<mime-type>application/ecmascript</mime-type>
<mime-type>application/json</mime-type>
<mime-type>application/x-www-form-urlencoded</mime-type>
</rewrite-mime-types>
</wsrp-producer-registry>
Any suggestions how to resolve the given error by correcting any entry in any configuration file will be very help ful.
Ashok 
Hello Ashok,
The exception you are getting seems to indicate that the WSDL document cannot be retrieved from the WSDL URL. This could be because the WSRP producer is not running or the WSDL URL is incorrect.
Kevin 
Thanks kevin you are right but thing is i want remove all the reference to given WSDL path, do you have some idea where this wsdl reference is present and how i can remove them.
Please help me with this issue i have tried to search in all file in my project to remove them still cant find the reference. 
Hello Ashok,
Are you using a streaming portal? If you can't find the WSDL URL being used in any of the configuration files, perhaps it was set up as a WSRP producer using the administration tools, which would store the producer information in the database. If this is the case, you should be able to use the administration console to remove the producer and eliminate this error.
Kevin 
Hi Kevin,
Yes i m using streaming portal, i hv created remote portlet and registered the WSDL URL to create the proxy portlets. but now i m getting the exception when deployed on dev server, Can u specify like how we can remove this remote portlet reference using the Admin console. 
thnks kevin 
Hello Ashok,
I believe if you look under "Portal Resources", then "Library", you'll see a "Portlet Producers" option in the tree on the left-hand side of the portal administration console. You should be able to click on "Portlet Producers" to get options on deleting a previously-configured producer.
Kevin

Configuring SAML-based Single Sign-on

I was developing a webcenter application. need to use Single Sign-on.
     
I step by step in accordance with the document webcenter configuration SAML based on the Single Sign-on,
after Configuring the SAML Identity Assertion Provider, restart weblogic server of the error is as follows:
<2009-7-21 10:00:46 CST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'bea_wls_internal' due to error weblogic.application.ModuleException: Failed to load webapp: 'bea_wls_internal.war'.weblogic.application.ModuleException: Failed to load webapp: 'bea_wls_internal.w
ar '
at weblogic.servlet.internal.WebAppModule.prepare (WebAppModule.java: 368)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare (ScopedM
oduleDriver.java: 176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare (Modu
leListenerInvoker.java: 93)
at weblogic.application.internal.flow.DeploymentCallbackFlow $ 1.next (Depl
oymentCallbackFlow.java: 387)
at weblogic.application.utils.StateMachineDriver.nextState (StateMachineD
river.java: 37)
Truncated. See log file for complete stacktrace
javax.servlet.ServletException: [Security: 090820] The internal variable ServletIn
foSpi is null and it should not be.
at weblogic.security.providers.saml.SAMLServletAuthenticationFilter.init
(SAMLServletAuthenticationFilter.java: 52)
at weblogic.security.service.internal.ServletAuthenticationFilterService
Impl $ ServiceImpl.getServletAuthenticationFilters (ServletAuthenticationFilterServ
iceImpl.java: 104)
at weblogic.security.service.PrincipalAuthenticator.getServletAuthentica
tionFilters (PrincipalAuthenticator.java: 608)
at weblogic.servlet.security.internal.WebAppSecurity. <init> (WebAppSecuri
ty.java: 80)
at weblogic.servlet.security.internal.WebAppSecurityWLS. <init> (WebAppSec
urityWLS.java: 65)
I wolud like to do ? who tell my?
Thank. 
i don't understand your question, but i'm guessing you want the webcenter forum, not webcenter interaction. 
I got the same error (Security: 090820 The internal variable ServletInfoSpi is null and it should not be) when I misconfigured the keystore. The Admin server would start, but the Managed Server wouldn't start up, apparently because it couldn't talk to the AS. I had to manually edit the config.xml file to undo the keystore change. 
Hi, could you please tell me what changes did you have to make in config.xml?
Thanks,
-Shruti 
Hi, could you please tell me what changes did you have to make in config.xml?
Thanks,
-Shruti

weblogic web service invoke error

I am new in WL and trying to invoking a web-service using client code written in java.
When I see in my service in web logic console it is looking fine same as other ready sample service which I am able to invoke using client code. I am using that sample client to invoke my web service after doing changes for my service. Client class is also compiled.
I am using weblogic 8.1 and I am getting below error.
------------------------------------------------------------------------------------------
cu dmwls(558)$ java Client http://localhost:61069/kuldeep/MyFirstService?WSDL
*<Feb 19, 2010 11:12:37 AM GMT> <Info> <WebService> <BEA-220094> <An IOException was thrown trying to access the WSDL at the given URL.>*
<Feb 19, 2010 11:12:37 AM GMT> <Info> <WebService> <BEA-220034> <A stack trace associated with message 220094 follows:
java.io.FileNotFoundException: http://localhost:61069/kuldeep/MyFirstService?WSDL
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:798)
at weblogic.webservice.tools.wsdlp.DefinitionFactory.createDefinition(DefinitionFactory.java:113)
at weblogic.webservice.tools.wsdlp.WSDLParser.<init>(WSDLParser.java:76)
at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:108)
at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:91)
at clientpkg.MyFirstService_Impl.<init>(MyFirstService_Impl.java:22)
at Client.main(Client.java:28)
>
Exception in thread "main" weblogic.webservice.tools.wsdlp.WSDLParseException: Failed to retrieve WSDL from http://localhost:61069/kuldeep/MyFirstService?WSDL. Please check the URL and make sure that it is a valid XML file [java.io.FileNotFoundException: http://localhost:61069/kuldeep/MyFirstService?WSDL]
at weblogic.webservice.tools.wsdlp.DefinitionFactory.createDefinition(DefinitionFactory.java:153)
at weblogic.webservice.tools.wsdlp.WSDLParser.<init>(WSDLParser.java:76)
at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:108)
at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:91)
at clientpkg.MyFirstService_Impl.<init>(MyFirstService_Impl.java:22)
at Client.main(Client.java:28)
------------------------------------------------------------------------------------------
While trying to access web-service, I am getting
Error 404--Not Found*
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:*
+10.4.5 404 Not Found+
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
Edited by: kuldeep.singhrawat75#gmail.com on Feb 19, 2010 4:56 PM 
Hi Kuldeep,
In your servicegen task you have defined
serviceURI="/${service.name}"
Please remove the preceeding forward slash from there like serviceURI="${service.name}"
Now deploy your service and then try to hit the WSDL like by opening a Browser:
http://ffstestmisws02.nat.bt.com:61069/${contextURI}/${service.name}?WSDL
Note : Just replace the values of ${service.name} and ${contextURI} with the actual values .... which you have specified in your ANT Task...
Still if you are not able to hit the WSDL then Just try to Access The Test Client Page from admin Console and access the WebService ...Let us know if u are able to invoke webservice method from TestClient Page of AdminConsole.
If not it means the Service is not deployed Successfully...Please check the Log after deploying the WebService and In case of any Error/Warning just paste the Trace here.
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com/webservices/ (WebLoigc Wonders Are here) 
Hi Jay,
During my on going testing on our DR site, across all the issues which kind of fixed and working now – I have come across 1 which I am a little amazed with
While trying to run the ping and buffer on REN SERVER
ERROR 404 Page not found. Everything is set up perfectly to what I understand.
Env. – HR to portal .
Request goes to RPS passes the firewall goes to LB and to REN and so on along with that.
Initially the Setup was incorrect which is corrected now. Then LB was listening to desired port – which was not activated while RPS was brought up – we have fixed that. so for now LB listens to port.
We have bounced app/prcs and cleared cache. But when tried to ping test – 404 (page not found error )
I have checked config.xml / struts-config.xml and web.xml – jus to verify the document root and context is alrite. Looks Good.
Checked logs - No specific error.
HR – Websphere … RPS apache...
Portal – Weblogic
Tools - 8.49.18
App - 9.0 (HR)
RENQ is up and running.
REN Server Cluster ID: RENCLSTR_0002
*StateFlag Active
*REN Server Cluster URL: https://psportal:8065
*REN Server Browser URL: https://psportal.dowjones.net:8065
Authentication Domain: dowjones.net
request your help pls

Unable to access https WSDL from browser IE 7  getting 405 error

Hi am trying to generate clinet jar and stubs for third party secured webservice.When I typed the url in browser (IE 7) am getting error saying
405 GET not supported, this is a SOAP service, please use POST.
I am using weblogic 8.1 and Eclipse SDK Version: 3.4.1, ant home - ant plug in frm eclispe folder org.apache.ant_1.7.0
the wsdl url is in this format ---- https://thirdparty.com/services/Soap/class/Ws_QSA?WSDL
Am generating the client gen using below line sin build.xml
<antcall target="generateClient" inheritAll="true" inheritRefs="true" />
<target name="generateClient" >
<clientgen wsdl="C:\Ws_QSA.wsdl"
packageName="com.services.webservice.client"
clientJar="C:\webservices\Client.jar"
classpathref="ws.clientgen.class.path"/>
</target>
and my java class i am trying to call the method by getting port as below.
private static WS_SOAP_Service service= new Ws_QSAService_Impl("https://thirdparty.com/services/Soap/class/Ws_QSA?WSD");
private static WS_ port =service.getWs_QSAPortType();
WS_port.getDetails();
<Jul 19, 2010 8:39:17 AM MDT> <Info> <WebService> <BEA-220094> <An IOException was thrown trying to access the WSDL at the given URL.>
<Jul 19, 2010 8:39:17 AM MDT> <Info> <WebService> <BEA-220034> (WSDLParser.java:76)
at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:108)
at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:91)
at com.services.webservice.Ws_QSAService_Impl.<init>(Ws_QSAService_Impl.java:22)
ERROR <clinit>, Problem accessing properties file for QSA service avalability webservice Url.
Failed to retrieve WSDL from https://thirdparty.com/services/Soap/class/Ws_QSA?WSDL. Please check the URL and make sure that it is a valid XML file [javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.]
weblogic.webservice.tools.wsdlp.WSDLParseException: Failed to retrieve WSDL from https://thirdparty.com/services/Soap/class/Ws_QSA?WSDL. Please check the URL and make sure that it is a valid XML file [javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.]
at weblogic.webservice.tools.wsdlp.DefinitionFactory.createDefinition(DefinitionFactory.java:169)
at weblogic.webservice.tools.wsdlp.WSDLParser.<init>(WSDLParser.java:76)
at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactory.java:108)
at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:91)
at weblogic.webservice.core.rpc.ServiceImpl.<init>(ServiceImpl.java:91)
at com.services.webservice.Ws_QSAService_Impl.<init>(Ws_QSAService_Impl.java:22)
Any body please help me what should I install for this SSL exception.I am struggling for three days i couldnt able to resolve.
If I got certificate from thirdparty what is the procedure should I follow .to access in Browser and from java client class .
**I posted this under answered thread so thought of just posting new one.** 
Hi
1. Here is the root cause of this Excpetion:
Failed to retrieve WSDL from https://thirdparty.com/services/Soap/class/Ws_QSA?WSDL. Please check the URL and make sure that it is a valid XML file [javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.]
2. What this means is the WebService exposed or https needs some sort of Security Certificates. Do this simple test. Invoke the WSDL Url using https directly in the browser. And check the WSDL carefully. Look if it has any Security Tag with security details that needs for https etc. This means when you access this WebService through any client you need to provide security certificate details also.
I remember seeing the provision to configure the certificates during the process of generating the Client JARs for the WSDLs exposed over https. If I could find that link, I will post here. But yes, there is an option to configure the proper certificates/security for this https webservices and then generate client jars.
Thanks
Ravi Jegga 
Thanks for the Reply Ravi.
I got the certificate from third party i imported in IE (While importing it didnt prompt me for any pwd too) and MMC ,used the below command
keytool -importcert -alias myprivateroot -keystore C:\bea\weblogic81\server\lib\cacerts -file C:\thirdparty-client.cer.
and imported in weblogic server too.and I dont see any security settings in the WSDL.has only sessionId.
I am little doubtful about the keytool import command for importing client certificate to cacerts.Am I missing something .
Thanks
Jetti.

Error on verifying message against security policy Error code:3603

Hello,We are migrating our WebServices from WL10.3 to WL12.1.2 and we haven't been able to invoke them as we did on 10.3. On their WSDL is specified a ws security policy like this:<wsp:Policy  xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"  xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702">  <sp:SymmetricBinding>    <wsp:Policy>      <sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">        <wsp:Policy>          <sp:HashPassword/>          <sp:WssUsernameToken10/>        </wsp:Policy>      </sp:UsernameToken>    </wsp:Policy>  </sp:SymmetricBinding>   <sp:SignedSupportingTokens>    <wsp:Policy>      <sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">        <wsp:Policy>          <sp:HashPassword/>          <sp:WssUsernameToken10/>        </wsp:Policy>      </sp:UsernameToken>    </wsp:Policy>  </sp:SignedSupportingTokens></wsp:Policy>When we try to use this webservice from the new WebLogic 12.1.2 domain we receive the following SoapFault      <env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">         <faultcode>wsse:InvalidSecurity</faultcode>         <faultstring>Error on verifying message against security policy Error code:3603</faultstring>      </env:Fault> Anyone can help us with this issue? We don't know what are we missing or if there is some additional configuration needed or incompatibility.For additional information, these guidelines has been considered:Use a password digest in SOAP messagesConfigure Authentication and Identity Assertion providersCreate a Web service security configurationThank you in advance and kind regards,Ruben
Finally I found out what was going on.This error is produced by a NullPointerException on class weblogic.wsee.security.wss.plan.SecurityMessageInspector line 535 when calling the getDigestMethod().getAlgorithm()ref = this.svalidator.getReference(st, this.blueprint.getXmlSignatureFactory().newDigestMethod(signingPolicy.getDigestMethod().getAlgorithm(), (DigestMethodParameterSpec)null), new ArrayList(), token.isIncludeInMessage()); Which differs from the 10.3 version, where a default digest method is providedlocalObject1 = this.svalidator.getReference(localSecurityToken, this.blueprint.getXmlSignatureFactory().newDigestMethod("http://www.w3.org/2000/09/xmldsig#sha1", (DigestMethodParameterSpec)null), new ArrayList(), paramSecurityToken.isIncludeInMessage()); Trying to understand the WS Policy file I resolved that if we are using a SignedSupportingTokens we also need to configure how tokens has to be signed otherwise use the SupportingTokens instead, which is what I did. So finally, if the policy was not properly defined, I don't understand why in this new version a NPE is raised (wrapped in an 3603 error code). Maybe it's a bug?Cheers,Rubén

Categories

Resources