Serialization Proxy
I'm currently using BlazeDS for remote objects in my application and Red5 for RTMP streaming. The problem is, our Java objects need to be serializable between client-to-server for both Red5 and BlazeDS and Red5 uses the org.red5.io.amf3.IExternalizable interface and BlazeDS uses the java.io.Externalizable interface. I can't just implement the Externalizable interface because I don't want server-to-server serialization to use the custom serialization logic.
Is there a way to define custom serialization methods only for BlazeDS so I don't have to define the java.io.Externalizable interface? Or is there a serialization proxy I can use similar to the flex.messaging.io.PropertyProxyRegistry that let's me proxy the readExternal/writeExternal methods to custom ones? I see there is a flex.messaging.io.SerializationProxy (http://livedocs.adobe.com/blazeds/1/javadoc/) but I'm not sure how to use it.
Has anyone does this before? Thanks.
Hi,
Try setting the Quality of Service(QOS) as Exactly Once In Order(EOIO).
Regards,
Chen
Similar Messages
-
Serialize ---- Proxy to Idoc scenario
Hi Folks,
I m using Proxy to Idoc scenario and am trigerring proxy messages one after other from my function module on the outbound side. However sometimes idoc2 gets posted before idoc1.
My requirement is that idoc2 to be processed only after idoc1 is successfully posted. Where and how do I serialize the idoc processing?
--- AKJHi,
This issue is basically at ur receiver IDoc side, when its getting processed.
To ensure, ur IDoc 2 gets processed only after IDoc 1, changes can be done during message mapping.
During mapping, inside control records of target IDoc, there is an 'serial' field. Fill this 'serial' field with a new unique number which increases with each and every new IDoc creation.
This serial field with increasing number will be used during processing of IDocs in a sequence.
Refer SAP Note - 752194 & 152239 for more details..
Please let me know if still there are any issues.
Thanks,
Anoop -
Trying to understand the Serialization interface
Im trying to understand the Serialization of objects?
As an example, I create a Library class that implements Serializable, that stores a collection of Book objects
If I am only looking at saving a Library object to file, does the Book class require Serialization also or just the Library?
I have read the API on serialization, no answer there, if it is it's not easy to understand or read into the API...There are some really important things to know about when doing serialization. For example one important thing to know about that not is mentioned here is that your serializable classes must define its own private static final long serialVersionUID because if you not do that will you not be able to deserialize (read in) the data you have saved later if you change anything in your serializable class. It is a bit tricky to manage files to which you have serialized different versions of your class, that is versions where you have added more serializable members to the class after you have serialized files. Well, it is not a problem if you don´t care if you have to type in all your saved data again every time you change anything instead of deserialize it (read it) from your file of course :)
Situations like this may be handled if you define your own (private) writeObject(ObjectOutputStream) and your own readObject(ObjectInputStream) methods in your serializable class but there is a better a lot smarter way to handle this. Use of a serialization proxy! how to use that is described in the excellent book Effective Java 2nd ed. With a serialzation proxy for every serializable version of your class (where a version corresponds to a version of your class with differences in its number of serializable members) may your class deserialize data written from elder versions of your class also. Actually is it first since I read the last chapter of Effective Java that I think I have myself begin to understand serialization well enough and I recommend you to do the same to learn how to use serialization in practice. -
Ipf: trying to understand the syntax
HI!
I would like to configure my ipf and tryimg to understand its syntax.
For example:
pass in quick proto tcp from 129.97.0.0/16 to any port = 22 keep state and
pass in quick on bge0 proto tcp from any to 0/32 port = 22 flags S keep state group 100 (# group 100 - inbound rules)
Both syntaxes are made to allow ssh, but what is the meaning of[i] o 0/32 port or 129.97.0.0/16 and of flags S keep state
Thanks.There are some really important things to know about when doing serialization. For example one important thing to know about that not is mentioned here is that your serializable classes must define its own private static final long serialVersionUID because if you not do that will you not be able to deserialize (read in) the data you have saved later if you change anything in your serializable class. It is a bit tricky to manage files to which you have serialized different versions of your class, that is versions where you have added more serializable members to the class after you have serialized files. Well, it is not a problem if you don´t care if you have to type in all your saved data again every time you change anything instead of deserialize it (read it) from your file of course :)
Situations like this may be handled if you define your own (private) writeObject(ObjectOutputStream) and your own readObject(ObjectInputStream) methods in your serializable class but there is a better a lot smarter way to handle this. Use of a serialization proxy! how to use that is described in the excellent book Effective Java 2nd ed. With a serialzation proxy for every serializable version of your class (where a version corresponds to a version of your class with differences in its number of serializable members) may your class deserialize data written from elder versions of your class also. Actually is it first since I read the last chapter of Effective Java that I think I have myself begin to understand serialization well enough and I recommend you to do the same to learn how to use serialization in practice. -
Inbound proxy message serialization
hi, i have an inbound proxy on SAP (ECC) which receives batch data. i need to serialize this i/b flow of data on SAP which come here through XI from one legacy system. appreatiate earliest response.
best regards
neerajYeah, thats fine, but what is the format in which the validation system sending data to XI ?. You might have configured a sender adapter in XI for that system to send the data to XI right ? So in the Sender communication channel, you specify EOIO as quality of service and give a queue name ( can be any anything )
example
Validation system-->Sender CC>XI(IE)---->ECC
( with EOIO n queue name QUEUE1)
Once you do this, the same queue will be used to transfer data from XI to ECC as well thus ensuring that data is received in the same order as it was sent.
I hope this helps you.
regards,
Advait -
Serialization of data in Inbound Proxy
Hi Experts
We have a scenario
SOAP--->XI---->Inbound Proxy(R/3)
The probelm which we are facing is that we have maintained QOS in sender as EOIO and also in XI EOIO
but when the messages goes to target R/3 system the QOS is not maintained and it gives Short Dump.
We have performed Queue Priortiziation on XI
I have few questions in regards with the above:
1)Is Que Priortiziation on R/3 system possible. If yes could someone provide me some doc on help on the same?
2) How to maintain QOS in Inbound Proxy.
3) If QOS is maintained in source system and XI why it is not getting maintained in Target system
Regards
Abhishek MahajanHi Abhishek,
Please have a look at the following links and see if it helps you.
Re: Queue Prioritization in R3/ECC
and
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0179632-5f59-2a10-babe-ae4838435226
Best Regards -
RMI exception calling web service from proxy class
I am getting the following error attempting to call a web service from a proxy. It appears to relate to the type of objects I am trying to send vs the type that is expected. Following the exception I am adding a copy of the control where calling the web service is sucessful, a copy of the proxy class that I am using to make this unsucessful call, and the controller.jpf that has the formBean where I am creating my objects
Caught Exception Calling the Web Service from the Proxy. The Exception is the f
ollowing: java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SO
APException: failed to serialize class org.openuri.www.CreateAccountCheckingReq
uestweblogic.xml.schema.binding.SerializationException: type mapping lookup fail
ure on class=class controls.CheckingService$anyType TypeMapping=TYPEMAPPING SIZE
=5
ENTRY 1:
class: org.openuri.www.CreateAccountCheckingResponse
xsd_type: ['http://www.openuri.org/']:lcl0:CreateAccountCheckingResponse
ser: org.openuri.www.CreateAccountCheckingResponseCodec@c0f4da
deser: org.openuri.www.CreateAccountCheckingResponseCodec@b1dd4
ENTRY 2:
class: org.openuri.www.FundingInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:FundingInfoAnonType
ser: org.openuri.www.FundingInfoAnonTypeCodec@1d36711
deser: org.openuri.www.FundingInfoAnonTypeCodec@13a59e
ENTRY 3:
class: org.openuri.www.AccountInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:AccountInfoAnonType
ser: org.openuri.www.AccountInfoAnonTypeCodec@1de5959
deser: org.openuri.www.AccountInfoAnonTypeCodec@bbf788
ENTRY 4:
class: org.openuri.www.CustomerInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:CustomerInfoAnonType
ser: org.openuri.www.CustomerInfoAnonTypeCodec@7824f9
deser: org.openuri.www.CustomerInfoAnonTypeCodec@1c35fe1
ENTRY 5:
class: org.openuri.www.CreateAccountCheckingRequest
xsd_type: ['http://www.openuri.org/']:lcl0:CreateAccountCheckingRequest
ser: org.openuri.www.CreateAccountCheckingRequestCodec@1cbcd7b
deser: org.openuri.www.CreateAccountCheckingRequestCodec@11f60ce
; nested exception is:
javax.xml.soap.SOAPException: failed to serialize class org.openuri.www
.CreateAccountCheckingRequestweblogic.xml.schema.binding.SerializationException:
type mapping lookup failure on class=class controls.CheckingService$anyType Typ
eMapping=TYPEMAPPING SIZE=5
ENTRY 1:
class: org.openuri.www.CreateAccountCheckingResponse
xsd_type: ['http://www.openuri.org/']:lcl0:CreateAccountCheckingResponse
ser: org.openuri.www.CreateAccountCheckingResponseCodec@c0f4da
deser: org.openuri.www.CreateAccountCheckingResponseCodec@b1dd4
ENTRY 2:
class: org.openuri.www.FundingInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:FundingInfoAnonType
ser: org.openuri.www.FundingInfoAnonTypeCodec@1d36711
deser: org.openuri.www.FundingInfoAnonTypeCodec@13a59e
ENTRY 3:
class: org.openuri.www.AccountInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:AccountInfoAnonType
ser: org.openuri.www.AccountInfoAnonTypeCodec@1de5959
deser: org.openuri.www.AccountInfoAnonTypeCodec@bbf788
ENTRY 4:
class: org.openuri.www.CustomerInfoAnonType
xsd_type: ['http://www.openuri.org/']:lcl0:CustomerInfoAnonType
ser: org.openuri.www.CustomerInfoAnonTypeCodec@7824f9
deser: org.openuri.www.CustomerInfoAnonTypeCodec@1c35fe1
ENTRY 5:
class: org.openuri.www.CreateAccountCheckingRequest
xsd_type: ['http://www.openuri.org/']:lcl0:CreateAccountCheckingRequest
ser: org.openuri.www.CreateAccountCheckingRequestCodec@1cbcd7b
deser: org.openuri.www.CreateAccountCheckingRequestCodec@11f60ce
Java Control for the web service:
package controls;
import weblogic.webservice.context.WebServiceContext;
* @jc:location http-url="http://localhost:7001/Checking.jws"
* @jc:wsdl file="#CheckingWsdl"
* @jc:handler callback="MessageHandler" operation="MessageHandler"
public interface CheckingService extends com.bea.control.ControlExtension, com.bea.control.ServiceControl
public static class CustomerInfo
implements java.io.Serializable
public java.lang.String FirstName;
public java.lang.String LastName;
public java.lang.String MiddleName;
public int SSN;
public int CustomerNumber;
public java.util.Calendar CreationDate;
public java.util.Calendar LastModifiedDate;
public static class FundingInfo
implements java.io.Serializable
public float Amount;
public java.util.Calendar CurrentDate;
public int AccountNumber;
public static class anyType
implements java.io.Serializable
public com.bea.xml.XmlObject[] t;
public static class AccountInfo
implements java.io.Serializable
public int AccountNumber;
public float Balance;
public int CustomerNumber;
public java.util.Calendar LastModifiedDate;
public WebServiceContext context = CheckingService.context;
* @jc:protocol form-post="false" form-get="false"
public AccountInfo CreateAccountChecking (CustomerInfo CustomerInfo, FundingInfo FundingInfo, anyType CommonHeader);
static final long serialVersionUID = 1L;
/** @common:define name="CheckingWsdl" value::
<?xml version="1.0" encoding="utf-8"?>
<!-- @editor-info:link autogen="false" source="" -->
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.openuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.openuri.org/">
<types>
<s:schema targetNamespace="http://www.openuri.org/" xmlns:s="http://www.w3.org/2001/XMLSchema">
<s:element name="CreateAccountCheckingRequest">
<s:complexType>
<s:sequence>
<s:element name="CustomerInfo">
<s:complexType>
<s:sequence>
<s:element name="FirstName" type="s:string" nillable="false"/>
<s:element name="LastName" type="s:string" nillable="false"/>
<s:element name="MiddleName" type="s:string" nillable="true"/>
<s:element name="SSN" type="s:int"/>
<s:element name="CustomerNumber" type="s:int"/>
<s:element name="CreationDate" type="s:dateTime"/>
<s:element name="LastModifiedDate" type="s:dateTime"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="FundingInfo">
<s:complexType>
<s:sequence>
<s:element name="Amount" type="s:float"/>
<s:element name="CurrentDate" type="s:dateTime"/>
<s:element name="AccountNumber" type="s:int"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="CommonHeader" type="s:anyType"/>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="CreateAccountCheckingResponse">
<s:complexType>
<s:sequence>
<s:element name="AccountInfo">
<s:complexType>
<s:sequence>
<s:element name="AccountNumber" type="s:int"/>
<s:element name="Balance" type="s:float"/>
<s:element name="CustomerNumber" type="s:int"/>
<s:element name="LastModifiedDate" type="s:dateTime"/>
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="string" nillable="true" type="s:string"/>
</s:schema>
</types>
<message name="CreateAccountCheckingSoapIn">
<part name="parameters" element="s0:CreateAccountCheckingRequest"/>
</message>
<message name="CreateAccountCheckingSoapOut">
<part name="parameters" element="s0:CreateAccountCheckingResponse"/>
</message>
<portType name="CheckingSoap">
<operation name="CreateAccountChecking">
<input message="s0:CreateAccountCheckingSoapIn"/>
<output message="s0:CreateAccountCheckingSoapOut"/>
</operation>
</portType>
<binding name="CheckingSoap" type="s0:CheckingSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<operation name="CreateAccountChecking">
<soap:operation soapAction="http://www.openuri.org/CreateAccountChecking" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="Checking">
<port name="CheckingSoap" binding="s0:CheckingSoap">
<soap:address location="http://localhost:7001/Checking.jws"/>
</port>
</service>
</definitions>
FOLLOWING IS THE PROXY CLASS THAT IS UNSUCCESSFUL
import controls.CheckingService.anyType;
import java.util.ArrayList;
import java.util.List;
import javax.xml.namespace.QName;
import javax.xml.rpc.handler.HandlerInfo;
import javax.xml.rpc.handler.HandlerRegistry;
import org.openuri.CreateAccountCheckingResponseDocument.CreateAccountCheckingResponse;
import org.openuri.www.CustomerInfoAnonType;
import org.openuri.www.FundingInfoAnonType;
import weblogic.jws.proxies.*;
import weblogic.webservice.context.WebServiceContext;
import weblogic.webservice.context.WebServiceSession;
import weblogic.webservice.core.handler.WSSEClientHandler;
import weblogic.webservice.tools.pagegen.result;
import weblogic.xml.security.UserInfo;
import weblogic.xml.security.wsse.Security;
import weblogic.xml.security.wsse.SecurityElementFactory;
//import weblogic.jws.proxies.WebServiceB;
//import weblogic.jws.proxies.WebServiceB_Impl;
//import weblogic.jws.proxies.WebServiceBSoap;
public class CheckingWSProxy
public static void CallWS(Controller.CreateAccountCheckingForm form)
String user;
String pass;
try{
* Instantiate the main proxy class. The proxy class has the same name as the
* web service, with "_Impl" appended.
Checking myservice = new Checking_Impl("http://localhost:7001/ConsumerAccountApp/schemas/CheckingService.wsdl");
WebServiceContext context = myservice.context();
WebServiceSession session = context.getSession();
* Registers a handler for the SOAP message traffic.
HandlerRegistry registry = myservice.getHandlerRegistry();
List list = new ArrayList();
list.add(new HandlerInfo(WSSEClientHandler.class, null, null));
registry.setHandlerChain(new QName("Checking"), list);
* Set the username and password token for SOAP message sent from the client, through
* the proxy, to the web service.
user = form.getUsername();
pass = form.getPassword();
UserInfo ui = new UserInfo(user, pass);
session.setAttribute(WSSEClientHandler.REQUEST_USERINFO, ui);
* Adds the username / password token to the SOAP header.
SecurityElementFactory factory = SecurityElementFactory.getDefaultFactory();
Security security = factory.createSecurity(null);
security.addToken(ui);
session.setAttribute(WSSEClientHandler.REQUEST_SECURITY, security);
* Get the protocol-specific proxy class.
CheckingSoap msg=myservice.getCheckingSoap();
* Invoke the web service method
msg.createAccountChecking((CustomerInfoAnonType)form.getProxyCustomerInfo(), (FundingInfoAnonType)form.getProxyFundingInfo(), (Object)form.get_CommonHeader());
catch (Exception ex)
System.out.println("Caught Exception Calling the Web Service from the Proxy. The Exception is the following: " + ex.toString());
FOLLOWING IS THE FORMBEAN IN THE CONTROLLER.JPF FILE
* FormData get and set methods may be overwritten by the Form Bean editor.
public static class CreateAccountCheckingForm extends FormData
private anyType _CommonHeader;
private controls.CheckingService.FundingInfo _FundingInfo;
private controls.CheckingService.CustomerInfo _CustomerInfo;
private java.util.Date dOut;
private java.util.Calendar cOut;
private CustomerInfo proxyCustomerInfo;
private FundingInfo proxyFundingInfo;
private String stringDate;
private String currentDate;
private String lastModifiedDate;
private String creationDate;
private String systemMessage;
private String username;
private String password;
private String accountType;
private String trashTransferAccount;
private String trashAccountNumber;
private boolean secureFlag;
public void set_CustomerInfo(controls.CheckingService.CustomerInfo _CustomerInfo)
_CustomerInfo.CreationDate = parseDate(getCreationDate());
_CustomerInfo.LastModifiedDate = parseDate(getLastModifiedDate());
this._CustomerInfo = _CustomerInfo;
public controls.CheckingService.CustomerInfo get_CustomerInfo()
if(this._CustomerInfo == null)
this._CustomerInfo = new controls.CheckingService.CustomerInfo();
_CustomerInfo.CreationDate = dateNow();
_CustomerInfo.LastModifiedDate = dateNow();
return this._CustomerInfo;
public CustomerInfo getProxyCustomerInfo()
this.proxyCustomerInfo = (CustomerInfo)this._CustomerInfo;
return this.proxyCustomerInfo;
public void set_FundingInfo(controls.CheckingService.FundingInfo _FundingInfo)
_FundingInfo.CurrentDate = parseDate(getCurrentDate());
this._FundingInfo = _FundingInfo;
public controls.CheckingService.FundingInfo get_FundingInfo()
if(this._FundingInfo == null)
this._FundingInfo = new controls.CheckingService.FundingInfo();
_FundingInfo.CurrentDate = dateNow();
return this._FundingInfo;
public FundingInfo getProxyFundingInfo()
this.proxyFundingInfo = (FundingInfo)this._FundingInfo;
return this.proxyFundingInfo;
public void set_CommonHeader(anyType _CommonHeader)
this._CommonHeader = _CommonHeader;
public anyType get_CommonHeader()
if(this._CommonHeader == null)
this._CommonHeader = new anyType();
return this._CommonHeader;
public java.util.Calendar dateNow()
this.dOut = new Date();
Calendar cOut = this.cOut.getInstance();
cOut.setTime(this.dOut);
this.cOut = cOut;
return this.cOut;
public java.util.Calendar parseDate( String strDate )
SimpleDateFormat df4 = new SimpleDateFormat( "MM/dd/yyyy" );
Calendar cOut = this.cOut;
df4.setLenient( false );
try
this.dOut = df4.parse( strDate );
} catch ( ParseException e )
cOut.getInstance();
cOut.setTime(dOut);
this.cOut = cOut;
return this.cOut;
public void setStringDate( String stringDate )
this.stringDate = stringDate;
public String getStringDate()
return this.stringDate;
public void setCurrentDate( String currentDate )
this.currentDate = currentDate;
public String getCurrentDate()
SimpleDateFormat df4 = new SimpleDateFormat( "MM/dd/yyyy" );
this.currentDate = df4.format(_FundingInfo.CurrentDate.getTime());
return this.currentDate;
public void setLastModifiedDate( String lastModifiedDate )
this.lastModifiedDate = lastModifiedDate;
public String getLastModifiedDate()
SimpleDateFormat df4 = new SimpleDateFormat( "MM/dd/yyyy" );
this.lastModifiedDate = df4.format(_CustomerInfo.LastModifiedDate.getTime());
return this.lastModifiedDate;
public void setCreationDate( String creationDate )
this.creationDate = creationDate;
public String getCreationDate()
SimpleDateFormat df4 = new SimpleDateFormat( "MM/dd/yyyy" );
this.creationDate = df4.format(_CustomerInfo.CreationDate.getTime());
return this.creationDate;
public void setUsername( String username )
this.username = username;
public String getUsername()
return this.username;
public void setPassword( String password )
this.password = password;
public String getPassword()
return this.password;
public void setAccountType( String accountType )
this.accountType = accountType;
public String getAccountType()
return this.accountType;
public void setTrashTransferAccount( String trashTransferAccount )
this.trashTransferAccount = trashTransferAccount;
public String getTrashTransferAccount()
return this.trashTransferAccount;
public void setTrashAccountNumber( String trashAccountNumber )
this.trashAccountNumber = trashAccountNumber;
public String getTrashAccountNumber()
return this.trashAccountNumber;
public void setSystemMessage( String systemMessage )
this.systemMessage = systemMessage;
public String getSystemMessage()
return this.systemMessage;
public void setSecureFlag( boolean secureFlag )
this.secureFlag = secureFlag;
public boolean getSecureFlag()
return this.secureFlag;
}This exception means that xml namespaces are different.
Etc. soap has xml element which doesn't belong to namespace of parent xml element and namespace is set without prefix.
I had such problem.
Try to set namespace prefix for this element.
Example:
<el1>
<el2 xmlns="http://..."/>
</el1>
Should be
<el1>
<q:el2 xmlns:q="http://..."/>
</el1> -
Problem in starting weblogic server as proxy
I am using weblogic server as Proxy to forward the requests to weblogic cluster.
When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
I am Pasting my complete logs below.
Setting JVM memory params for server IRISProxy
Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
WLS Production Mode=true
./startWebLogic.sh[68]: B: not found.
maxfiles=8192
CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
java version "1.4.1.05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
Starting WLS with line:
/home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
Bad level value for property: com.iplanet.services.debug.level
Bad level value for property: com.sun.identity.agents.logging.level
Bad level value for property: com.sun.am.policy.amFilter.audit.level
<Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
<Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
<Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
<Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
<Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
<Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
>
<Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
<Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
Can someone help me in solving this problem
Thanks
KrisI solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
WebLogic Temporary Patch for CR211812
WebLogic Temporary Patch for CR235145
Once i commented the above patches in the CLASSPATH.
The issue is resolved. -
Hi All,
Am getting an error when running my interface from SPROXY (its an outbound interface).
The error says " Runtime (Serialize) 866 (execute) (serialize)". This error is coming after the complete execution of the interface.
I am passing the values to a structure of an outbound proxy from my inbound proxy. When I executed the outbound proxy separately, its working fine.
The values are getting passed properly. One guess was this proxy was in inactive stage when i opened recently and I activated the same. The structure remains the same.
Regards
RKHi Manish,
Thanks for your response. I did re-generated it and activated it .. initially after seeing that its inactive and everything looked fine..
The interesting part is I am able to see the output properly in the Response tab but the same isn't sent to PI ..
Pls advice
Regards
RK -
SPROXY error testing outbound proxy interface
Hi,
I am trying to test an outbound proxy interface using SPROXY but am getting the following error:
Apart from the above messages there is no more help available. When I try testing the generated XSLT program using SXSLT_TEST it gives an error "No valid XSLT program supplied". I have checked and the auto generated XSLT program does exist.
Any help appreciated.
Thanks
CheHi Che Eky,
Check out below helpful thread & doc:
SERIALIZE_APPLICATION_DATA Conversion error ABAP => XML: Request Message
Serialization issue in abap proxy
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a89312f8-0b01-0010-86b3-fdd7178e0534?QuickLink=index&…
Regards,
Krupa -
ABAP Client proxy - IF_WSPROTOCOL_ASYNC_MESSAGING
I have a question regarding the value for the attribue ASYNC_MESSAGING. In every client proxy, this attribute is defaulted to IF_WSPROTOCOL_ASYNC_MESSAGING. (inherits the value from IF_WSPROTOCOL).
Does that mean that the client ABAP proxy uses EOIO ? If so, how do you change it to EO?
If the change of QoS from EOIO to EO is not possible, would creating custom queues and using the SERIALIZATION CONTEXT to specify the custom queue help me alleviate issues with stuck EOIO queues on the sender/receiver sides while using proxy? Since the QoS is determined by the sender, I would assume that if there is way to set it on the Sender client proxy, that would prevent the queues from stopping processing if a message fails. In my case, I am not too concerned about preserving the sequence of the messages.
Any input will be appreciated.
Thanks
SridharHello Sridhar,
I'm not sure if I understand your question right, but I think following applies : ABAPProxy client (SAP sends data to SAP PI) behaves as EO by default. And if one needs to have messages to be delivered to the destination system in order, you need to "tell" this to SAP PI, when you send the data from ABAPProxy client. Thats the case you need include coding as mentioned here: http://help.sap.com/saphelp_nw04/helpdata/en/65/40c9a4a1fa476288ac61b5fcc6bbde/frameset.htm.
Please note, that for WAS 620 ABAPProxy client another routine applies. For more information see the link: http://help.sap.com/saphelp_xi20sr1/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
Regards
Tomas -
JAX-WS proxy and WS-ReliableMessaging
Hello all,
JDeveloper 11.1.2.3
I've started the foray into looking at reliable web services as specified by WS-ReliableMessaging. I have a very simple Hello World web service deployed (it was written in C# and deployed on IIS, if you have to ask :P). In JDeveloper, I've generated a JAX-WS Style proxy and test class using the JDeveloper wizard to do so. I've specified that no Async methods be generated and that there are no client OWSM policies (none are deemed compatible with the web service anyway).
I then add a bit of code to my test class and run to test. The first time I run the class, the WS calls work successfully, although after the sequence of calls, I get an exception displayed in the console (see below). If I try to run the class again, the web service calls don't even execute and I get a different exception in the console (again, see below - at least part of this error is captured by my ReliabilityErrorListener). This sequence of events alternates ad-infinitum (odd-numbered attempts work with an exception, even-numbered attempts don't work.
I show my test code here:
// Add your code to call the desired methods.
WsrmClientInitFeature f = new WsrmClientInitFeature(true);
ReliabilityErrorListener listener = new ReliabilityErrorListener()
public void onReliabilityError(ReliabilityErrorContext context)
// At a *minimum* do this
System.out.println("RM sequence failure: " + context.getFaultSummaryMessage());
// And optionally do this...
// The context parameter tells you whether a request or the entire
// sequence has failed. If a sequence fails, you'll get a notification
// for each undelivered request (if any) on the sequence.
if (context.isRequestSpecific())
// We have a single request failure (possibly as part of a larger
// sequence failure).
// We can get the original request back like this:
String operationName = context.getOperationName();
System.out.println("Failed to deliver request for operation '" + operationName + "'. Fault summary: " +
context.getFaultSummaryMessage());
else
// The entire sequence has encountered an error.
System.out.println("Entire sequence failed: " + context.getFaultSummaryMessage());
f.setErrorListener(listener);
hello = helloService.getWSHttpBindingHello(f);
WsrmClient c = WsrmClientFactory.getWsrmClientFromPort(hello);
System.out.println("Sequence ID is " + c.getSequenceId());
// c.reset();
System.out.println(hello.getGreeting("John"));
System.out.println(hello.getGreeting("Fred"));
System.out.println(hello.getGreeting("Josephine"));
System.out.println("Sequence ID is " + c.getSequenceId());
try
System.out.println(c.getAckRanges().first().lowerBounds);
System.out.println(c.getAckRanges().first().upperBounds);
catch (Exception e)
// c.setFinalMessage();The calls that work look like this in the console:
Sequence ID is null
<05-Mar-2013 14:55:53 o'clock EAT> <Info> <Store> <BEA-280008> <Opening the persistent file store "weblogic.wsee.persistence.WseeFileStore" for recovery: directory=C:\JDeveloper\11.1.2.3\mywork\WSReliableClientPOC\Client requestedWritePolicy="Cache-Flush" fileLockingEnabled=true driver="NIO".>
<05-Mar-2013 14:55:53 o'clock EAT> <Info> <Store> <BEA-280009> <The persistent file store "weblogic.wsee.persistence.WseeFileStore" (569ea4fb-b0fd-4906-bb74-003b6885b1d5) has been opened: blockSize=512 actualWritePolicy="Cache-Flush(single-handle-non-direct)" explicitIOEnforced=false records=57.>
Hello, John. You have just communicated with me using WS-reliablemessaging
Hello, Fred. You have just communicated with me using WS-reliablemessaging
Hello, Josephine. You have just communicated with me using WS-reliablemessaging
Sequence ID is uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffd
1
3
<05-Mar-2013 14:56:03 o'clock EAT> <Error> <WseeRm> <BEA-224016> <An unexpected error occurred: weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.getConversation(DefaultSendingServiceProvider.java:222)
at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.stopConversation(DefaultSendingServiceProvider.java:287)
at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:257)
at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
<05-Mar-2013 14:56:03 o'clock EAT> <Error> <WseePersist> <BEA-221000> <An unexpected error occurred: java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@6ac27081 - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@6ac27081 - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
at weblogic.wsee.reliability2.sequence.Sequence.removePropertyChangeListener(Sequence.java:1250)
at weblogic.wsee.reliability2.store.SequenceMap.shutdownSequence(SequenceMap.java:558)
at weblogic.wsee.reliability2.store.TimedSequenceMap.shutdownSequence(TimedSequenceMap.java:182)
at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:274)
at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
Process exited with exit code 0.The calls that don't work look like this:
Sequence ID is null
<05-Mar-2013 14:57:49 o'clock EAT> <Info> <Store> <BEA-280008> <Opening the persistent file store "weblogic.wsee.persistence.WseeFileStore" for recovery: directory=C:\JDeveloper\11.1.2.3\mywork\WSReliableClientPOC\Client requestedWritePolicy="Cache-Flush" fileLockingEnabled=true driver="NIO".>
<05-Mar-2013 14:57:49 o'clock EAT> <Info> <Store> <BEA-280009> <The persistent file store "weblogic.wsee.persistence.WseeFileStore" (569ea4fb-b0fd-4906-bb74-003b6885b1d5) has been opened: blockSize=512 actualWritePolicy="Cache-Flush(single-handle-non-direct)" explicitIOEnforced=false records=59.>
RM sequence failure:
weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
Failed to deliver request for operation 'GetGreeting'. Fault summary:
weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
Exception in thread "main" java.lang.AssertionError: weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:689)
at com.sun.xml.ws.client.Stub.process(Stub.java:272)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
at $Proxy36.getGreeting(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
at $Proxy35.getGreeting(Unknown Source)
at org.tempuri.WSHttpBinding_HelloClient.main(WSHttpBinding_HelloClient.java:96)
Caused by: weblogic.wsee.sender.api.PermanentSendException: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
at weblogic.wsee.reliability2.store.SourceSequenceSender.checkForPermanentSendFailure(SourceSequenceSender.java:549)
at weblogic.wsee.reliability2.store.SourceSequenceSender.handleFailureForSuspendedFiber(SourceSequenceSender.java:604)
at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponseForSuspendedFiber(SourceSequenceSender.java:452)
at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponse(SourceSequenceSender.java:293)
at weblogic.wsee.reliability2.store.SourceSequenceSender.send(SourceSequenceSender.java:184)
at weblogic.wsee.sender.DefaultProvider.Conversation.sendOneRequest(Conversation.java:671)
at weblogic.wsee.sender.DefaultProvider.Conversation.sendPendingRequests(Conversation.java:579)
at weblogic.wsee.sender.DefaultProvider.Conversation.access$1400(Conversation.java:44)
at weblogic.wsee.sender.DefaultProvider.Conversation$2.timerExpired(Conversation.java:476)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused by: javax.xml.ws.WebServiceException: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:258)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:273)
at weblogic.wsee.reliability2.store.SourceSequenceSender.sendRequestAndHandleResponseForSuspendedFiber(SourceSequenceSender.java:442)
... 10 more
Caused by: SequenceFaultException: The value of wsrm:Identifier is not a known Sequence identifier.: uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-94bc5:13d3a6864db:-7ffe
at weblogic.wsee.reliability2.tube.WsrmTubelineDeploymentListener$WsrmClientProtocolTube.processResponse(WsrmTubelineDeploymentListener.java:222)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:877)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
at com.sun.xml.ws.client.Stub.process(Stub.java:272)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:238)
... 12 more
<05-Mar-2013 14:57:58 o'clock EAT> <Error> <WseeRm> <BEA-224016> <An unexpected error occurred: weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
weblogic.wsee.sender.api.ConversationNotFoundException: [WseeSender:221102]The conversation with the given name (uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd) could not be found.
at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.getConversation(DefaultSendingServiceProvider.java:222)
at weblogic.wsee.sender.DefaultProvider.DefaultSendingServiceProvider.stopConversation(DefaultSendingServiceProvider.java:287)
at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:257)
at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
<05-Mar-2013 14:57:58 o'clock EAT> <Error> <WseePersist> <BEA-221000> <An unexpected error occurred: java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@79424b7b - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
java.lang.IllegalStateException: Attempt to remove listener from weblogic.wsee.reliability2.sequence.SourceSequence@79424b7b - uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-156fc54b:13d3a5dab50:-7ffd when it is not the master instance
at weblogic.wsee.reliability2.sequence.Sequence.removePropertyChangeListener(Sequence.java:1250)
at weblogic.wsee.reliability2.store.SequenceMap.shutdownSequence(SequenceMap.java:558)
at weblogic.wsee.reliability2.store.TimedSequenceMap.shutdownSequence(TimedSequenceMap.java:182)
at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:274)
at weblogic.wsee.reliability2.store.SourceSequenceMap.shutdownSequence(SourceSequenceMap.java:30)
at weblogic.wsee.reliability2.store.SequenceStore.removePhysicalStore(SequenceStore.java:109)
at weblogic.wsee.persistence.LogicalStore.close(LogicalStore.java:955)
at weblogic.wsee.persistence.LogicalStore.closeLogicalStores(LogicalStore.java:402)
at weblogic.wsee.persistence.LogicalStore.closeStore(LogicalStore.java:384)
at weblogic.wsee.persistence.LogicalStore.closeAllStores(LogicalStore.java:365)
at weblogic.wsee.persistence.LogicalStore$1.run(LogicalStore.java:164)
>
Process exited with exit code 1.Does anyone have any insight about this behaviour?
Thanks,
JohnSome additional information for the second case. Using HTTP analyzer in JDeveloper, I can see 2 HTTP POSTs going to the web service. The first one is to initiate the WS-RM sequence and shows an offered conversation identifier and the reply shows that the server has given its own identifier instead of the offered one:
request:
POST http://xgis-lel-05717.ad.xglobal.com:80/WSReliablePOC/HelloService.svc HTTP/1.1
Proxy-Authorization:
Content-type: application/soap+xml;charset="utf-8";action="http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence"
Accept: application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: Oracle JAX-WS 2.1.5
Host: xgis-lel-05717.ad.xglobal.com
Proxy-Connection: Keep-Alive
Content-Length: 1620
X-HTTPAnalyzer-Rules: 1@localhost:8099
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Header>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing" env:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffb</wsa:MessageID>
<wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</wsa:To>
<ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
</ReplyTo>
<FaultTo xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
</FaultTo>
</env:Header>
<env:Body xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
<wsrm:CreateSequence>
<wsrm:AcksTo xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address>
<wsa:ReferenceParameters xmlns:clspi="http://www.oracle.com/wsee/jaxws/cluster/spi">
<clspi:PhysicalStoreName
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" wsa:IsReferenceParameter="true">WseeFileStore</clspi:PhysicalStoreName>
</wsa:ReferenceParameters>
</wsrm:AcksTo>
<wsrm:Expires>P1D</wsrm:Expires>
<wsrm:Offer>
<wsrm:Identifier>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffe</wsrm:Identifier>
<wsrm:Expires>P1D</wsrm:Expires>
</wsrm:Offer>
</wsrm:CreateSequence>
</env:Body>
</env:Envelope>
reply:
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Cache-Control: private
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
Content-Length: 673
Server: Microsoft-IIS/7.5
Date: Tue, 05 Mar 2013 12:10:44 GMT
X-HTTPAnalyzer-RuleName: Pass through :
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse</a:Action>
<a:RelatesTo>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffb</a:RelatesTo>
</s:Header>
<s:Body>
<CreateSequenceResponse xmlns="http://schemas.xmlsoap.org/ws/2005/02/rm">
<Identifier>urn:uuid:b6886ed1-6cf2-40a4-99a3-f17cc5a295d7</Identifier>
<Expires>P1D</Expires>
<Accept>
<AcksTo>
<a:Address>http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</a:Address>
</AcksTo>
</Accept>
</CreateSequenceResponse>
</s:Body>
</s:Envelope>The second POST shows the JDeveloper proxy calling the web service and sending a wsrm:Identifier value that the one originally offered by JDeveloper (see the sequence acknowledgement), not the one the server advised to use:
request:
POST http://xgis-lel-05717.ad.xglobal.com:80/WSReliablePOC/HelloService.svc HTTP/1.1
Proxy-Authorization:
Content-type: application/soap+xml;charset="utf-8";action="http://tempuri.org/Hello/GetGreeting"
Accept: application/soap+xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: Oracle JAX-WS 2.1.5
Host: xgis-lel-05717.ad.xglobal.com
Proxy-Connection: Keep-Alive
Content-Length: 1444
X-HTTPAnalyzer-Rules: 1@localhost:8099
<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">
<S:Header>
<wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://xgis-lel-05717.ad.xglobal.com/WSReliablePOC/HelloService.svc</wsa:To>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://tempuri.org/Hello/GetGreeting</wsa:Action>
<ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
</ReplyTo>
<FaultTo xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://www.w3.org/2005/08/addressing/anonymous</Address>
</FaultTo>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:201221c6:13d3a75f768:-7ffc</wsa:MessageID>
<wsrm:SequenceAcknowledgement xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
<wsrm:Identifier>uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-725c9c83:13d3a75543c:-7ffe</wsrm:Identifier>
<wsrm:AcknowledgementRange Lower="1" Upper="3"/>
</wsrm:SequenceAcknowledgement>
<wsrm:Sequence
xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm" S:mustUnderstand="true">
<wsrm:Identifier>urn:uuid:b6886ed1-6cf2-40a4-99a3-f17cc5a295d7</wsrm:Identifier>
<wsrm:MessageNumber>1</wsrm:MessageNumber>
</wsrm:Sequence>
</S:Header>
<S:Body>
<GetGreeting
xmlns:ns2="http://schemas.microsoft.com/2003/10/Serialization/" xmlns="http://tempuri.org/">
<name>John</name>
</GetGreeting>
</S:Body>
</S:Envelope>
response:
HTTP/1.1 500 Internal Server Error
Content-Type: application/soap+xml; charset=utf-8
Cache-Control: private
X-Powered-By: ASP.NET
X-AspNet-Version: 4.0.30319
Content-Length: 710
Server: Microsoft-IIS/7.5
Date: Tue, 05 Mar 2013 12:10:52 GMT
X-HTTPAnalyzer-RuleName: Pass through :
<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
</s:Header>
<s:Body>
<s:Fault>
<s:Code>
<s:Value>s:Sender</s:Value>
<s:Subcode>
<s:Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/rm">a:UnknownSequence</s:Value>
</s:Subcode>
</s:Code>
<s:Reason>
<s:Text xml:lang="en-GB">The value of wsrm:Identifier is not a known Sequence identifier.</s:Text>
</s:Reason>
<s:Detail>
<r:Identifier xmlns:r="http://schemas.xmlsoap.org/ws/2005/02/rm">uuid:WLS1:WseeFileStore:3f3d2d8955322f32:-725c9c83:13d3a75543c:-7ffe</r:Identifier>
</s:Detail>
</s:Fault>
</s:Body>
</s:Envelope>This seems to be an issue in the JDev-generated Proxy (still need to find out why it happens "every other time" and not "every time." The time it works, JDeveloper is sending the Identifier returned by the service. The time it works, however - you can also see that the "conversation not found" exception is referring to the original "offered" identifier and not the one that was used in the conversation. I'm now starting to suspect that the proxy generation for WS-RM may be a bit buggy. Anyone else with experience in this area?
A quick look at support.oracle.com does find note 1082278.1 which although for old versions of WebLogic, that WS-RM isn't supported for JAX-WS in WLS, but is supported for JAX-RPC. Since this seems to be for publishing web services, it is not at all clear as to whether this applies to me. In any case, the JDeveloper WS proxy wizard won't let me generate a JAX-RPC proxy, instead saying that the WSDL has no SOAP 1.1 bindings (which is correct, it has SOAP 1.2 bindings).
John
John -
Hi Experts
Working on the SOAP to Proxy scenario, XML message is coming, I am transforming the message from xml into HTML by using the XSLT mapping
I receive the following errror while testing, Can anyone tell how to trace the error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Thanks
PRHi,
Please have a look at the following links and see if it helps
Exception handling Proxy to SOAP
SOAP to Proxy test scenario 7.1 PI
How To Debug XML Serialization Error With Deployable Proxy
Best Regards -
SvcUtil creates incorrect namespace in the proxy
I create the WCF proxy with the cmd:
svcutil.exe /wrapped /serializer:XmlSerializer GenericTicketConnector.wsdl /o:OTRS.cs /config:App.Config /n:*,OTRSClient.OTRSServiceReference
Contract GenericTicketConnector.wsdl you can see here:
https://raw.githubusercontent.com/OTRS/otrs/rel-3_3/development/webservices/GenericTicketConnector.wsdl
My WCF client code:
using (OTRSClient.OTRSServiceReference.GenericTicketConnector_InterfaceClient tst = new OTRSClient.OTRSServiceReference.GenericTicketConnector_InterfaceClient("GenericTicketConnector_endPoint"))
OTRSClient.OTRSServiceReference.OTRS_SessionCreate sc = new OTRSClient.OTRSServiceReference.OTRS_SessionCreate();
sc.ItemElementName = OTRSClient.OTRSServiceReference.ItemChoiceType8.UserLogin;
sc.Item = "soap";
sc.Password = "1234567";
OTRSClient.OTRSServiceReference.OTRS_SessionCreateResponse res = tst.SessionCreate(sc);
File.WriteAllText("SessionID.txt", res.SessionID);
SvcUtil created this proxy:
[System.ServiceModel.MessageBodyMemberAttribute(Name="SessionCreateResponse", Namespace="", Order=0)]
public OTRSClient.OTRSServiceReference.OTRS_SessionCreateResponse SessionCreateResponse1;
But response from server looks like this:
<soap:Envelope soap:encodingStyle="http://www.w3.org/2003/05/soap-encoding" xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc="http://www.w3.org/2003/05/soap-encoding" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<s:Header xmlns:s="http://www.w3.org/2003/05/soap-envelope"></s:Header>
<soap:Body>
<SessionCreateResponse xmlns="http://www.otrs.org/TicketConnector/">
<SessionID>r3oRuOPBXiYtOZCCKIL5ZNSCDCKS7lAt</SessionID>
</SessionCreateResponse>
</soap:Body>
</soap:Envelope>
Response in my WCF client's code was null.
I manually corrected the proxy like this:
[System.ServiceModel.MessageBodyMemberAttribute(Name="SessionCreateResponse", Namespace="http://www.otrs.org/TicketConnector/", Order=0)]
public OTRSClient.OTRSServiceReference.OTRS_SessionCreateResponse SessionCreateResponse1;
And the answer began to contain the required data (response is not null).
How to fix the parameters of the command line SvcUtil call? Or I must fix the WSDL file?
I need to make a proxy automatically with the correct namespace.Hi Andrey Antipov,
Based on your description, it seems that you are using the XmlSerializer, please try to use the
DataContractSerializer to see if it can work.
Besides, please also try to use the "Add Servicexs Reference" to see if it can make a proxy automatically with the correct namespace.
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Amy,
What is happening is that you are trying to send an object between 2
partitions
(probably a parameter of the UpdateAllChannelsState(), of type
JC_DSGService),
and this object references, at its own level or through a cascade of
attributes,
an object of type EventRegistration (Object returned by the Register()
statement).
Such objects, just like Timers and Files, can NOT be sent to a remote
partition.
To fix it, you have to Nil out such references before sending between
partitions.
Hope this helps,
Vincent Figari
On Fri, 6 Mar 1998 12:07:28 -0500 Amy Devine <[email protected]>
writes:
We have an application that runs successfully in interpreted mode, but
once
we make the distribution, we get the following error:
Exception escaped from terminating task PlaybackWindow.Display:
SYSTEM ERROR: Error serializing attribute 2 of class JC_DSGService
(serialization type 5).
Class: qqsp_SerializationException
Detected at: qqrt_4GLClassType::InstanceXlate at 1
Last TOOL statement: method PlaybackWindow.UpdateAllChannelsState
Error Time: Fri Mar 06 12:01:30
Distributed method called: JobControllerProxy.GetObjAttr (object
name
site/iseng_jobcontroller_3_cl0/iseng_ui_4_cl1-jobcontrollerso)
from
partition "ISENG_UI_4_cl1_Client", (partitionId =
8FCF8A10-B2BE-11D1-AB24-3CCB8932AA77:0x1e5:0x8, taskId =
[8FCF8A10-B2BE-11D1-AB24-3CCB8932AA77:0x1e5.74]) in application
"FTLaunch_cl0", pid 75 on node KATHY in environment centrale
Exception occurred (remotely) on partition "Forte_Executor",
(partitionId
= 8FCF8A10-B2BE-11D1-AB24-3CCB8932AA77:0x1e9, taskId =
[8FCF8A10-B2BE-11D1-AB24-3CCB8932AA77:0x1e9.15]) in application
"ISENG_UI_4_cl1", pid 111 on node KATHY in environment centrale.
The remainder of the Error Manager stack is:
SYSTEM ERROR: An attempt was made to send a reference to an anchored
object
(qqlo_EventHandlerInfo) to another partition, but the object has no
Proxy
class. The object was anchored by setting the IsShared or
IsAnchored
attribute, but the object's class did not have the Distributed
property
set.
Class: qqsp_UsageException with ReasonCode:
SP_ER_SERIALIZATIONERROR
Detected at: qqdo_ProxyMgr::GetScopeClass at 1
Error Time: Fri Mar 06 12:01:30
Exception occurred (remotely) on partition "Forte_Executor",
(partitionId
= 8FCF8A10-B2BE-11D1-AB24-3CCB8932AA77:0x1e9, taskId =
[8FCF8A10-B2BE-11D1-AB24-3CCB8932AA77:0x1e9.15]) in application
"ISENG_UI_4_cl1", pid 111 on node KATHY in environment centrale.
We are running Forte 3.0.F.0 on NT. The service object cited in the
error,
JC_DSGService has its properties set as IsShared = Allowed and
IsDistributed = Allowed. Any ideas what could be causing this error?
TIA,
Amy Devine
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com
Or call Juno at (800) 654-JUNO [654-5866]As I thought, you're trying to query from the triggering table.
I believe the following would give you the desired result without having to include that table in the query...
CREATE OR REPLACE TRIGGER XXWMM_REQUISITION_TRG before insert on PO_REQUISITION_LINES_ALL
FOR EACH row
Declare
v_source_code VARCHAR2(200);
Begin
SELECT interface_source_code
into v_source_code
FROM po_requisition_headers_all prh
where prh.requisition_header_id = :new.requisition_header_id
IF v_source_code = 'MSC' THEN
:new.NOTE_TO_VENDOR := :new.NOTE_TO_RECEIVER;
ELSE
Null;
END IF;
End;
Maybe you are looking for
-
Here is a screenshot of what I'm talking about [http://cl.ly/1P0O0U1s0K0W0r142N22 http://cl.ly/1P0O0U1s0K0W0r142N22] This is not happening in other browsers on my computer, and just started when I updated to the latest version of Firefox.
-
Issue with Monitoring of Subscription Orders
Dear Experts , Recently we are facing an issue in the monitoring of subscription orders. We have scheduled the Monitoring ( Tcode : JKRM) in the background during the night time. Since last few days, our basis guy is complaining about creation of too
-
Weblogic 9.2 MP3 giving error on startup : java.io.IOException: CreateProce
Hi, I upgraded my server from weblogic 9.2 MP1 to MP3 and I get this error during weblogic startup. I have JDK150_12 in the classpath. What could be causing this error? java.io.IOException: Compiler failed executable.exec: java.io.IOException: Create
-
Tables parameters are obsolete
hi, i am trying to create one function module in ecc6.0 version. And after declaration under tables table like "errortable like bapiret2" i am getting the warning "tables parameters are obsolete". please help me to solve this problem.
-
How do I disable yahoo contact sync?
After installing 10.7.2 on my 2010 21.5 iMac, I started getting popup Yahoo windows asking if I wanted to sync my contacts. I keep clicking cancel but every 15 min or so, the same window comes up. I have checked my address book and I have it set to