Exception in Transport

i have a problem, there are the exception:
07/08/06 16:16:18 Oracle Application Server Containers for J2EE 10g (10.1.2.0.0) initialized
07/08/06 16:16:47 DEBUG: not loading system providers in <java.home>/lib
07/08/06 16:16:47 DEBUG: successfully loaded optional custom providers from URL: jar:file:/C:/jdev10g/jdk/jre/lib/ext/pop3.jar!/META-INF/javamail.providers
07/08/06 16:16:47 DEBUG: successfully loaded default providers
07/08/06 16:16:47
DEBUG: Tables of loaded providers
07/08/06 16:16:47 DEBUG: Providers Listed By Class Name: {com.sun.mail.smtp.SMTPTransport=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc], com.sun.mail.imap.IMAPStore=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], com.sun.mail.pop3.POP3Store=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsystems, Inc]}
07/08/06 16:16:47 DEBUG: Providers Listed By Protocol: {imap=javax.mail.Provider[STORE,imap,com.sun.mail.imap.IMAPStore,Sun Microsystems, Inc], pop3=javax.mail.Provider[STORE,pop3,com.sun.mail.pop3.POP3Store,Sun Microsy stems, Inc], smtp=javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]}
07/08/06 16:16:47 DEBUG: not loading optional address map file: /META-INF/javamail.address.map
07/08/06 16:16:47 listos para transportar el msj
07/08/06 16:16:47 javax.mail.NoSuchProviderException: No provider for smtps
07/08/06 16:16:47      at javax.mail.Session.getProvider(Session.java:289)
07/08/06 16:16:47      at javax.mail.Session.getTransport(Session.java:484)
07/08/06 16:16:47      at javax.mail.Session.getTransport(Session.java:464)
07/08/06 16:16:47      at com.apps.EnvioMail.enviarCorreo(EnvioMail.java:106)
07/08/06 16:16:47      at prj_reunion._jspService(prj_reunion.jsp:387)
07/08/06 16:16:47      at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:57)
07/08/06 16:16:47      at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
07/08/06 16:16:47      at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
07/08/06 16:16:47      at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
07/08/06 16:16:47      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
07/08/06 16:16:47      at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
07/08/06 16:16:47      at oracle.security.jazn.oc4j.JAZNFilter.doFilter(Unknown Source)
07/08/06 16:16:47      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649)
07/08/06 16:16:47      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
07/08/06 16:16:47      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
07/08/06 16:16:47      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
07/08/06 16:16:47 Excepcion javax.mail.NoSuchProviderException: No provider for smtps
07/08/06 16:16:47      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
07/08/06 16:16:47      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
07/08/06 16:16:47      at java.lang.Thread.run(Thread.java:534)
I use JDeveloper, i make a jsp page to send a email, but i can't
this is the code: (javabean)
//Properties prop = System.getProperties();
        Properties prop = new Properties();
        prop.put("mail.smtp.host", this.host);
        prop.put("mail.smtps.auth", "true");
        prop.put("mail.debug", "true");
        prop.put("mail.smtp.starttls.enable", "true");
        prop.put("mail.smtp.port", this.puerto);
        try {
            SMTPAuthenticator auth = new SMTPAuthenticator();
            Session sesion1 = Session.getInstance(prop);
            sesion1.setDebug(true);
            MimeMessage mensaje = new MimeMessage(sesion1);
            mensaje.setSubject(this.asunto);
            mensaje.setFrom(new InternetAddress(this.de));
            mensaje.addRecipient(Message.RecipientType.TO, new InternetAddress(this.para));
            BodyPart partesMensaje = new MimeBodyPart();
            partesMensaje.setText(this.mensaje);
            Multipart multipartes = new MimeMultipart();
            if (archivo != null) {
                multipartes.addBodyPart(partesMensaje);
                //aqui se agrega el attachment
                partesMensaje = new MimeBodyPart();
                DataSource source = new FileDataSource(archivo);
                partesMensaje.setDataHandler(new DataHandler(source));
                partesMensaje.setFileName(archivo.getName());
            multipartes.addBodyPart(partesMensaje);
            //se ingresa las partes del mensaje a mandar
            mensaje.setContent(multipartes);
            mensaje.saveChanges();
            System.out.println("listos para transportar el msj");
            Transport tr = sesion1.getTransport("smtps");  
            tr.connect(host,this.de, this.password);
            tr.sendMessage(mensaje, mensaje.getAllRecipients());
            tr.close();
            System.out.println("El mensaje ha sido enviado");
        } catch (Exception ex) {
            ex.printStackTrace();
            System.out.println("Excepcion "+ex);
        } the settings values:
host="smtp.gmail.com";
puerto="665";
password="xxxxxxx";
de="[email protected]";
i hope your help.

you don't use javamail 1.4... problem of multiple mail.jar librairies in your java server (search all .jar!)
regards,

Similar Messages

  • Transport classes and programs to another server

    Except for transport routing and charm copy function, do we have other ways to do so?
    for example copy or so forth.
    best regards,
    Blake Le

    Hi Blake
    SAP R/3 Correction and Transport System
    Operating system level files in the transport process:
    The SAP C program TP, requires a special file structure for the transport process. The file system is operating system dependent. TP uses a transport directory or file system, which is called /usr/sap/trans.
    The /usr/sap/trans file system is generally NFS mounted form the development system to other systems unless a system is defined as a single system in the CTS pipeline. All the sub directories should have <SID>adm as the owner and sapsys as the group; and proper read, write and execute access should be given to owner and the group. The TP imports are always performed by <SID>adm.
    The following are the subdirectories in /usr/sap/trans:
    /data
    /cofiles
    /bin
    /log
    /actlog
    /buffer
    /sapnames
    /tmp
    /usr/sap/trans/data: holds the data of transport objects after they are released . The example of a data file is R904073.DEV. The extension DEV means the data file was released from the DEV or development system.
    /usr/sap/trans/cofiles: The cofiles directory holds the command files for all change requests. These files are like a command or control files used to import the data files. The common directory for CTS system is /usr/sap/trans. After a change request is released from the source system , the data is exported immediately to the file system of the operating system. The SAP transport utility TP uses the cofile to transport a data file. The example of a file in cofiles directory is K904073.DEV.
    /usr/sap/trans/bin: holds the most important file TPPARAM in the CTS system. TPPARAM file has all the information about the CTS systems in the CTS pipeline. TPPARAM file is the parameter file for the transport program TP and it is the common file for all the systems in the CTS pipeline. As you know already that /usr/sap/trans should be NFS mounted to all the systems in a CTS pipeline, TP program has access to the TPPARAM file from all the systems. The following is an example of typical TPPARAM file for five SAP systems in the CTS pipeline:
    #@(#) TPPARAM.sap 20.6 SAP 95/03/28
    Template of TPPARAM for UNIX #
    First we specify global values for some parameters, #
    later the system specific incarnation of special parameters #
    global Parameters #
    transdir = /usr/sap/trans/
    dbname = $(system)
    alllog = ALOG$(syear)$(yweek)
    syslog = SLOG$(syear)$(yweek).$(system)
    System spezific Parameters #
    Beispiel T11 #
    DEV/dbname = DEV
    DEV/dbhost = sap9f
    DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
    QAS/dbname = QAS
    QAS/dbhost = sap8f
    QAS/r3transpath = /usr/sap/QAS/SYS/exe/run/R3trans
    TRN/dbname = TRN
    TRN/dbhost = sap17
    TRN/r3transpath = /usr/sap/TRN/SYS/exe/run/R3trans
    PRE/dbname = PRE
    PRE/dbhost = sap19f
    PRE/r3transpath = /usr/sap/PRE/SYS/exe/run/R3trans
    PRD/dbname = PRD
    PRD/dbhost = sap18f
    PRD/r3transpath = /usr/sap/PRD/SYS/exe/run/R3trans
    /usr/sap/trans/log: holds the entire log files, trace files and statistics for the CTS system. When the user goes to SE09 (workbench organizer) or SE10 (customizing organizer) transaction and opens the log for a transport, the log file for that transport will be read from /usr/sap/trans/log directory. Each change request should have a log file. Examples of log files are DEVG904073.QAS, DEVI904073.QAS and DEVV904073.QAS. The name of a log file consists of the names of the change request, the executed step, and the system in which the step was executed:
    <source system><action><6 digits>.<target system>
    Now we can analyze the above example DEVG904073. QAS. The <source system> = DEV, <action> = G or report and screen generation, <6 digits> = 904073 (these six digits numbers are exactly the same number as the six digits of the transport) and the <target system> = QAS
    Possible values for <action> are:
    A: Dictionary activation
    D: Import of application-defined objects
    E: R3trans export
    G: Report and screen generation
    H: R3trans dictionary import
    I: R3trans main import
    L: R3trans import of the command files
    M: Activation of the enqueue modules
    P: Test import
    R: Execution of reports after put (XPRA)
    T: R3trans import of table entries
    V: Set version flag
    X: Export of application-defined objects.
    /usr/sap/trans/actlog: holds action log files. The example of an action file is DEVZ902690.DEV. The following are the contents of the file:
    1 ETK220 u201C==================================================u201D u201C=================
    =============================
    1 ETK191 u201C04/30/1998u2033 Action log for request/task: u201CDEVK902690u2033
    1 ETK220 u201C==================================================u201D u201C=================
    =============================
    1 ETK185 u201C04/30/1998 18:02:32u2033 u201CMOHASX01u2033 has reincluded the request/task
    4 EPU120 Timeu2026 u201C18:02:32u2033 Run timeu2026 u201C00:00:00u2033
    1 ETK193 u201C04/30/1998 18:02:33u2033 u201CMOHASX01u2033 owner, linked by u201CMOHASX01u2033 to u201CDEVK902691u2033
    4 EPU120 Timeu2026 u201C18:02:33u2033 Run timeu2026 u201C00:00:00u2033
    1 ETK190 u201C05/04/1998 11:02:40u2033 u201CMOHASX01u2033 has locked and released the request/task
    1 ETK194 u201C05/04/1998 11:02:40u2033 **************** End of log *******************
    4 EPU120 Timeu2026 u201C11:02:40u2033 Run timeu2026 u201C00:00:09u2033
    ~
    ~u201DDEVZ902690.DEVu201D 10 lines, 783 characters
    /usr/sap/trans/buffer: transport buffer of the target systems; contains control information on which requests are to be imported into which systems and in what order the imports must occur. The /usr/sap/trans/buffer will have a directory for each system in the CTS pipeline. For example the buffer file for DEV system is /usr/sap/trans/buffer/DEV.
    /usr/sap/trans/sapnames: holds information pertaining to transport requests for each system user. There are files for each user who released change requests from the system.
    /usr/sap/trans/tmp: holds information about temporary data and log files. While the transport is occurring the Basis administrator can find a file that is related to the transport in the tmp directory; that file shows the exact status if the transport (What objects are being imported at that time).
    Important SAP delivery class and table types and tables in the CTS process:
    Delivery class
    The delivery class defines who (i.e. the SAP system itself or the customer) is responsible for maintaining the table contents. In addition the delivery class controls how the table behaves in a client copy and an upgrade. For example when you select a SAP defined profiles to perform a client copy, certain tables are selected according to their delivery class. DD02L table can show what delevery class a table belongs to.
    The following delivery classes exist:
    A: Application table.
    C: Customizing table, maintenance by customer only.
    L: Table for storing temporary data.
    G: Customizing table, entries protected against overwriting.
    E: Control table.
    S: System table, maintenance only by SAP.
    W: System table, contents can be transported via own TR objects.
    Table type
    The table type defines whether a physical table exists for the logical table description defined in the ABAP/4 Dictionary and how the table is stored on the database.
    The following are different table types in SAP:
    Transparent Tables
    There is a physical table on the database for each transparent table. The names of the physical table and the logical table definition in the ABAP/4 Dictionary are same. For every transparent table in SAP, there is a table in database. The business and application data are stored in transparent tables.
    Structure
    No data records exist on the database for a structure. Structures are used for the interface definition between programs or between screens and programs.
    Append Structure
    An Append structure defines a subset of fields which belong to another table or structure but which are treated as a separate object in the correction management. Append structures are used to support modifications.
    The following table types are used for internal purposes, for example to store control data or for continuous texts:
    Pooled table
    Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated-pooled tables are stored.
    Cluster table
    Cluster tables contain continuous text, for example documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least part of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
    Tables in CTS process:
    TRBAT and TRJOB:
    TRJOB and TRBAT are the major tables in the CTS process. After TP program has sent the event to the r3 system, RDDIMPDP checks table TRBAT in the target system to find out if there is an action to be performed. Mass activation, distribution, or table conversions are the examples of actions. If there is action to be performed, RDDIMPDP starts the appropriate program in the background task. RDDIMPDP then reschedules itself.
    By checking table TRJOB, RDDIMPDP automatically recognizes if a previous step was aborted, and restarts this step. For each transport request , TP program inserts an entry into table TRBAT. If the return code 9999 in this table then the step is waiting to be performed. Return code 8888 indicates that the step is active and currently being processed. A return code of 12 or less indicates that the step is finished. In addition, TP inserts a header entry to let the RDDIMPDP program know to start processing. The column return code will therefore contain a B for begin. When RDDIMPDP is started, it sets the header entry to R(un), and starts the required program. When all the necessary actions are performed for all the transport requests, the column return code contains all the return codes received, and the column TIMESTAMP contains the finishing time. The header entry is set to F(inished). TP monitors the entries in TRBAT and TRJOB tables. When the header entry in TRBAT is set to finished. The entry in TRJOB is deleted.
    Transport Tables SE06
    TDEVC - Development classes
    TASYS - Details of the delivery. Systems in the group that should automatically receive requests, have to be specified in table TASYS.
    TSYST - The transport layers will be assigned to the integration systems. ( Define all systems)
    TWSYS - Consolidation routes ( define consolidation path)
    DEVL - Transport layers are defined here
    In u201CConfiguring the CTS systemu201D section, We will learn more about the transport tables in SE06 transaction
    Programs in the CTS process:
    In the CTS table section we learned about the RDDIMPDP program. RDDIMPDP program needs to be scheduled in all the clients in an instance. It is recommended to schedule the RDDIMPDP as event driven.
    RDDPUTPP and RDDNEWPP programs can be used to schedule RDDIMPDP program in the background.
    The ABAP/4 programs that RDDIMPDP starts are determined by the transport step to be executed that is entered in the function field of table TRBAT.
    Function Job Name Description of transport Steps
    J RDDMASGL Activation of ABAP/4 dictionary objects
    M RDDMASGL Activation of match codes and lock objects
    S RDDDISOL Analysis of database objects to be converted
    N RDDGENOL Conversion of database objects
    Y RDDGENOL Conversion of matchcode tables
    X RDDDICOL Export of AD0 objects
    D RDDDIC1L Import of AD0 objects
    E RDDVERSE Version management update during export
    V RDDVERSL Version management update during import
    R RDDEXECL Execution of programs for post - import processing
    G RDDDIC3L Generation of ABAP/4 programs and screens
    Version Management:
    One of the important features of Workbench Organizer is Version Management. This feature works for all the development objects. Using the version management feature the users can compare and retrieve previous versions of objects.
    Version management provides for comparisons, restore of previous versions, documentation of changes and assistance in the adjustment of data after upgrading to a new release. With the release of a change request, version maintenance is automatically recorded for each object. If an object in the system has been changed N times, it will have N delta versions and one active version. To display version management, for ABAPs use transaction SE38 and for tables, domains and data elements use SE11. The path to follow is Utilities -> Display version. Using version management the users can view existing version for previously created ABAP code, make changes to the code, compare code versions and restore original version of the code. Now the users will be restore previous versions without cut and paste steps of the past.
    TP and R3trans program:
    The basis administrator uses TP program to transport SAP objects from one system to another. TP is a C program delivered by SAP that runs independently of the R/3 system. TP program uses the appropriate files located in a common transport directory /usr/sap/trans. TP starts C programs, ABAP/4 programs and special operating system commands to its job. R3trans is one of the most important utility program called by TP. Before using the TP program, the basis administrator needs to make sure that the CTS system is setup properly and the right version of TP is running in the system. The TP program is located in the run time directory /usr/sap/<SID>/SYS/exe/run directory. It is automatically copied in the install process. A global parameter file TPPARAM that contains the databases of the different target systems and other information for the transport process controls TP. The global parameter file determines which R3trans is used for each system. If the parameter r3transpath is not defined properly then no export and import can be done. The basis administrator should make sure that the default value u201Cr3transpathu201D is properly defined. Later in this chapter we will learn more about TP and R3trans; also we are going to see how they are used.
    Configuring the TPPARAM file:
    Each time TP is started, it must know the location of the global parameter file. As we have seen before TPPARAM file should be in directory /usr/sap/trans/bin. The parameters in TPPARAM can either global (valid for each and every system in the cts pipeline) or local to one system. Th parameters are either operating system dependant (these parameters preceded by a keyword corresponding to the specific operating system) or database dependant (contain a keyword corresponding to a specific database system).
    The global parameter file provides variables that can be used for defining parameters. The variables can be defined in format: $(xyz). The brackets can be substituted with the u201C\u201D-character if required.
    The following pre-defined variables are available for the global parameter file:
    $(cpu1): The CPU name can be sun or as4 for example. In heterogeneous networks this variable is very important.
    $(cpu2): Acronym for the name of the operating system. The example for this variable can be
    hp-ux, or sunos . This is an operating system specific variable.
    $(dname): Used for the day of the week (SUN,MON,u2026.).
    $(mday): Used for the day of the current month (01-31).
    $(mname): Used for the name of the month (JANu2026DEC).
    $(mon): Used for the Month (01-12).
    $(system): R/3 System name.
    $(wday): Day of the week (00-06, Sunday=00, Monday=01, Tuesday=02 and so on).
    $(yday): Day of the current year (001-366). Using the number any day of the year can be chosen.
    $(year): Year (Example:1998 or 1999).
    $(syear): Short form of the year (two positions).
    $(yweek): Calendar week (00-53). The first week begins with the first Sunday of the year.
    For the database connection:
    The transport environment also needs parameters to connect to the R/3 System database. As we know already the every instance in the R/3 CTS pipeline has its own database, therefore specific parameters should be defined for each database system. From dbtype parameter of RSPARAM file, TP program identifies the database system.
    The two parameters u201Cdbnameu201D and u201Cdbhostu201D are required for ORACLE databases.
    DBHOST: is the name of the computer on which the database processes execute. TCP/IP name of the host if NT is being used.
    DBNAME: is the name of the database instance.
    As of Release 3.0E, two new parameters have been introduced.
    DBLOGICALNAME: The default value is $(system). The logical name that was used to install the database.
    DBCONFPATH: The default value is $(transdir).
    The parameters u201Cdbnameu201D and u201Cdbhostu201D are also used for INFORMIX databases in an installation:
    DBHOST: Same as Oracle.
    DBNAME: Name of the database instance, uppercase and lowercase are distinguished here.
    INFORMIXDIR : u201C/informix/<SAPSID>u201D is the default value. Defines the directory namewhere the database software can be found.
    INFORMIXSQLHOSTS: u201C$(informixdir)/etc/sqlhosts[.tli|.soc]u201Cis default value under Unix. The name of the SQLhosts file with its complete path is defined with this parameter.
    INFORMIX_SERVER: u201C$(dbhost)$(dbname)shmu201D is the default value. The name of the database server may be specified for a local connect.
    INFORMIX_SERVERALIAS: u201C$(dbhost)$(dbname)tcpu201Dis the default vlue. The name of the database server can be specified for a remote connect.
    For Microsoft SQL Server database the two parameters u201Cdbnameu201D and u201Cdbhostu201D are also required. DBHOST: The TCP/IP name of the host on which the database is running.
    DBNAME: The database instance name.
    For DB2 in AS/400 only u201Cdbhostu201D is required.
    DBHOST: System name of the host on which the database is running.
    If theu201DOptiConnectu201D is used, the following line should be specified:
    OPTICONNECT 1
    For DB2/ AIX
    The two parameters u201Cdbnameu201D and u201Cdbhostu201D are required
    DBHOST: The host on which the database processes are running. It is the TCP/IP name of the host for Windows NT (As we have seen in the earlier examples).
    DBNAME: Database instance name.
    The DB2 for AIX Client Application Enabler Software must also be installed on the host on which tp is running.
    ALLLOG: u201CALOGu201D $(syear) $(yweek)u201Dis the default value. This variable can be used in TPPARAM file to specify the name of a file in which tp stores information about every transport step carried out for a change request anywhere in the transport process. The file always resides in the log directory.
    SYSLOG: u201CSLOG $(syear) $(yweek).$(system)u201D is the default value. This variable can be used to name a file in which tp stores information about the progress of import actions in a certain R/3 System. The file does not store information for any particular change request. The file always resides in the log directory.
    tp_VERSION: Zero is the default value. If this parameter is set to not equal to zero, a lower version of tp may not work with this TPPARAM file. If the default value (zero) is set, the parameter has no affect.
    STOPONERROR: (Numeric value) The default value is 9. When STOPONERROR is set to zero, tp is never stopped in the middle of an u201Cimportu201D or u201Cputu201D call. When STOPONERROR is set to a value greater than zero, tp stops as soon as a change request generates a return code that is equal to or greater than this value (The numeric value of the STOPONERROR parameter is stored in the variable BADRC). Change requests, which still have to be processed for the current step, are first completed. A u201CSYNCMARKu201D in the buffer of the R/3 System involved, sets a limit here. tp divides the value of this parameter between two internal variables. STOPONERROR itself is treated as a boolean variable that determines whether tp should be stopped, if the return code is too high.
    REPEATONERROR (Numeric value too): The default value is 9. The REPEATONERROR parameter is similar to STOPONERROR. The difference is, REPEATONERROR specifies the return code up to which a change request is considered to be successfully processed. Return codes less than REPEATONERROR are accepted as u201Cin Orderu201D. Change requests that were not processed successfully stay in the buffer.
    NEW_SAPNAMES: Default value is u201CFALSEu201D. A file is created for each user of the R/3 System group in the u201Csapnamesu201D subdirectory of the transport directory. Except some of the operating system,the name of the user is the name of the file. It is very important to remember hat the special characters or length of the file name could cause problems. If all the R/3 Systems in the transport group have at least Release level 3.0.; TP program is efficient to handle this problem. The user names are modified to create file names that are valid in all operating systems and the real user names are stored in a corresponding file.
    Though we have seen so many parameters, for the minimum configuration the following two parameters are very important.
    TRANSDIR: specifies the name of the common transport directory. The following is a typical example from TPPARAM of Unix as we have seen before.
    transdir = /usr/sap/trans/
    DBHOST: contains the name of the database host. In Windows NT environment, this is the TCP/IP host name. The following is an example in Unix:
    DEV/dbname = DEV
    DEV/dbhost = sap9f
    DEV/r3transpath = /usr/sap/DEV/SYS/exe/run/R3trans
    For TP, to control u2018Start and Stopu2019 command files and database in R/3 the following important parameters are specified in TPPARAM:
    Parameters for the tp Function u201CPUTu201D: LOCK_EU (boolean) default value is u201CTRUEu201D. Though from version 3.1 onward the tp put command is used seldom in cts process still it is important to know how this parameter works. When u201Ctp putu201D is used, it changes the system change option . If the parameter is set to u201CFALSEu201D nothing gets changed. If the parameter is set to u201CTRUEu201D, the system change option is set to u201CObjects cannot be changedu201D at the beginning of the call, and gets changed back to its previous value at the end of the call. The u201Ctp putu201D command will give the exact status of the locking mechanism.
    LOCKUSER (used as boolean value): Default value is u201CTRUEu201D. This parameter is about the user login while tp put call is executed. If this parameter is set to u201CFALSEu201D, no locking mechanism for the users takes affect. If this parameter is defined as u201CTRUEu201D then a character is set in the database level; so only DDIC and SAP* can log on to the system. Users that have already logged on are not affected (this is a reason for activating the parameters STARTSAP and STOPSAP). The charactertor is removed at the end of the call, and all the users can log on to the SAP R/3 System again.
    STARTSAP: Default value is u201D u201C.or u201CPROMPTu201D for Windows NT . This parameter is used by TP to start an R/3 System. It is not necessary for the clients to make tp start and stop R/3 system..
    STOPSAP: Default value is u201D u201Cor u201CPROMPTu201D for Windows NT. TP uses this parameter to stop an R/3 System.
    STARTDB: Default value is u201D u201C. TP uses the value of this parameter to start the database of an R/3 System.
    The parameter is not active under Windows NT.
    STOPDB: Default value is u201D u201C. TP uses the value of this parameter to stop the database of an R/3 System.
    This parameter is not active under Windows NT.
    The above parameters in UNIX can be used as following:
    STARTSAP = startsap R3
    STOPSAP = stopsap R3
    STARTDB = startsap db
    STOPDB = stopsap db
    In Windows NT:
    STARTSAP =
    $(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\startsap.exe
    R3 <SID> <HOST NAME> <START PROFILE>
    STOPSAP =
    $(SAPGLOBALHOST)\sapmnt\$(system)\sys\exe\run\stopsap.exe
    R3 <SID> <HOST NAME> <INSTANCE> <PROFILE PATH + Instance profile>
    The parameters STARTDB and STOPDB are not active under Windows NT.
    Parameters for the tp function u201CCLEAROLDu201D
    DATALIFETIME (Numeric): Default value is u201C200u2033. When the data file has reached a minimum age, it is moved to the subdirectory old data with tp check. tp clearold all. The life span of the data files in the data sub directory can be set in days with this all, parameter.
    OLDDATALIFETIME (Numeric): Default value is u201C365u2033. When a file located in the olddata subdirectory is no longer needed for further actions of the transport system and has reached a minimum age, it is removed with tp check.all, tp clearold all. The minimum age in days can be set with this parameter.
    COFILELIFETIME (Numeric): Default value is u201C365u2033. This parameter is used just like DATALIFETIME parameter.
    LOGLIFETIME (Numeric): Default value is u201C200u2033. This parameter applies to the life span of the log files. When the log files in log subdirectory is no longer needed for the transport system and has reached a minimum age, it is deleted with the calls tp check.all, tp clearold all. The minimum age in days can be defined with this parameter.
    The Three Key Utilities of the CTS system (TP, R3trans and R3chop):
    TP: Earlier in this chapter we have seen the objectives of TP. The TP transport control program is a utility program that helps the user to transport objects from one system to another. TP program is the front-end for the utility R3trans. TP stands for u201CTransports and Putsu201D. To make the TP work successfully the CTS system needs to be correctly configured. The following steps are very important for TP to run properly.
    The transport directory /usr/sap/trans must be installed and NFS mounted to all the systems in the CTS pipe line.
    RDDIMPDP program must be running (event driven is recommended) in each client. RDDIMPDP can be scheduled in the background by executing RDDNEWPP or RDDPUTPP. Use the tp checkimpdp <sap sid> command in /usr/sap/trans/bin directory as <sid>adm user to check RDDIMPDP program.
    Use the tp connect <sap sid> command in /usr/sap/trans/bin directory to see whether the tp program is connecting to the database successfully or not. To run TP command the user has to logon as <sid>adm in source or target system.
    The R/3 Systems in the CTS pipeline must have different names.
    The Global CTS Parameter File TPPARAM must be correctly configured.
    The source system (for the export) and target system ( for the import) must have at least two background work processes. TP always schedules the C class job, so if all the background jobs are defined as A class job then there will be problems in transport steps.
    Important Tips :.It is always better to have the up to date TP version installed in your system. A user can ftp a current version of TP from SAPSERV4 of SAP. Though R3trans and other utility programs can be used to do the transport, it is recommended to use TP whenever possible for the following reasons..
    The exports and imports are done separately using TP program. For example: when a transport is released from the system, the objects are exported from the source database to the operating system and then the import phase starts to transport those objects to the target system.
    TP takes care of the order of the objects. The order, that was followed to export the objects; the same order will be followed to import them to the target database.
    The TP command processes all change requests or transports in the SAP system buffer that have not yet been imported successfully. All the import steps are executed automatically after TP calls R3trans program to execute the following necessary steps:
    Dictionary Import: ABAP/4 dictionary objects will be imported in this step.
    Dictionary Activation: Name tabs or runtime descriptions will be written inactively. The R/3 system keeps running until the activation phase is complete. The enqueue modules are the exceptions in the running phase. After the activation of new dictionary structure the new actions are decided to get the runtime objects to the target system.
    Structure conversion: If necessary the table structure is changed in this phase.
    Move Nametabs: The new ABAP/4 Dictionary runtime objects which were inactive up to now are moved into the active runtime environment in this process. The database structures are adjusted accordingly. From the first step to the Main import step inconsistencies can occur to the R/3 system. After the main import phase all the inconsistency ca be solved.
    Main import with R3trans: All the data are imported completely and the system comes to a consistent state.
    Activation of enqueue-objects: The enqueue-objects cannot be activated in the same way as the objects of the ABAP/4 Dictionary, so they have to be activated after the main import in this step. They are then used directly in the running system.
    Structure Conversion of match codes, Import application defined objects, versioning and execution of user defined activities are some of the steps after activation of enqueue-objects. The next step is generation of ABAP/4 programs and screens, where all the programs and screens associated with the change request are generated. When all the import steps are completed successfully, the transport request is removed from the import buffer.
    It is recommended by SAP to schedule regular periods for imports into the target system (e.g. daily, weekly or monthly). Shorter periods between imports are not advisable. The transport to production should not be done in the off hours when the users are not working
    TP can be started with different parameters. The u201Ctp helpu201D command can help user to generate a short description about the use of the command.
    The following are the some important commands of TP:
    For export:
    tp export <change request>: The complete objects in the request from the source system will be transported. This command also used by SAP System when it releases a request.
    tp r3e <change request>: R3trans export of one transport request.
    tp sde <change request>: Application defined objects in one transport request can be exported.
    tp tst <change request> <SAP system >: The test import for transport request can be done using this command.
    tp createinfo <change request>: This command creates a information file that is automatically done during the export.
    tp verse <request>: This command creates version creates versions of the objects in the specified request.
    To Check the transport buffer, global parameter file and change requests:
    tp showbuffer <sid>: Shows all the change requests ready to be imported to the target system.
    tp count <sid>: Using this command users can find out the number of requests in the buffer waiting for import.
    tp go <sid>: This command shows the environment variables needed for the connection to the database of the <sid> or target system.
    tp showparams <sid>: All the values of modifiable tp parameters in the global parameter file. The default value is shown for parameters that have not been set explicitly.
    To import the change requests or transports:
    tp addtobuffer <request>.<sid>: If a change request is not in the buffer then this command is used to add it to the buffer, before the import step starts.
    tp import all <sid>: This command imports all the change requests from the buffer to the target system.
    tp put <sid>: The objective of this command is same as u201Ctp import all <sid>u201D, but this command locks the system. This command also starts and stops the SAP system, if the parameters startsap and stopsap parameters are not set to u201D u201C.
    tp import <change request> <sid>: To import a single request from the source system to target system.
    tp r3h <change request>| all <sid>: Using this command user can import the dictionary structures of one transport or all the transport from the buffer.
    tp act <change request>|all <sid>: This command activates all the dictionary objects in the change request.
    tp r3i <change request> | all <sid>: This command imports everything but dictionary structures of one.
    tp sdi <change request>|all <sid>: Import application-defined objects.
    tp gen <change request>|all <sid>: Screen and reports are generated using this command.
    tp mvntabs <sid>: All inactive nametabs will be activated with this command.
    tp mea <change request>|all <sid>: This command will activate the enqueue modules in the change request.
    When you call this command, note the resulting changes to the import sequence.
    Additional tp utility options:
    tp check <sid>|all (data|cofiles|log|sapnames|verbose): User uses this command to find all the files in the transport directory that are not waiting for imports and they have exceeded the minimum time specified using the COFILELIFETIME, LOGFILELIFETIME, OLDDATALIFETIME and DATALIFETIME parameters of TPPARAM file.
    tp delfrombuffer <request>.<sid>: This command removes a single change request from the buffer. In case of TMS, the request will be deleted from the import queue.
    tp setstopmark <sid>: A flag is set to the list of requests ready for import into the target system. When the user uses the command tp import all <sapsid> and tp put <sapsid>, the requests in front of this mark are only processed. After all the requests in front of the mark have been imported successfully, the mark is deleted.
    tp delstopmark <sid>: This command deletes the stop mark from the buffer if it exists.
    tp cleanbuffer <sapsid>: Removes all the change requests from the buffer that are ready for the import into the target system.
    tp locksys <sid>: This command locks the system for all the users except SAP* and DDIC. The users that have already logged on are not affected by the call.
    tp unlocksys <sid>: This command unlocks the system for all the users.
    tp lock_eu <sid>: This command sets the system change option to u201Csystem can not be changedu201D tmporarily.
    tp unlock_eu <sid>: This command unlocks the system for all the changes.
    tp backupall <sid>: This command starts a complete backup using R3trans command. It uses /usr/sap/trans/backup directory for the backup.
    tp backup delta <sid>: Uses R3trans for a delta backup into /usr/sap/trans/backup directory.
    tp sapstart <sid>: To start the R/3 system.
    tp stopsap <sid>: To stop the R/3 system.
    tp dbstart <sid>: To start the database.
    tp dbstop <sid>: To stop the database.
    Unconditional modes for TP: Unconditional modes are used with the TP program and these modes are intended for the special actions needed in the transport steps. Using unconditional mode user can manipulate the rules defined by the workbench organizer. The unconditional mode should be used when needed, otherwise it might create problems for the R/3 system database. Unconditional mode is used after the letter u201CUu201D in the TP command. Unconditional mode can be a digit between 0 to 9 and each has a meaning to it. The following is a example of a import having unconditional mode.
    tp import devk903456 qas client100 U12468
    0: Called a overtaker; change request can be imported from buffer without deleting it and then uncoditional mode 1 is used to allow another import in the correct location.
    1: If U1 is used with the export then it ignores the correct status of the command file; and if it is used with import then it lets the user import the same change request again.
    2: When used with tp export, it dictates the program to not to expand the selection with TRDIR brackets. If used in tp import phase, it overwrites the originals.
    3: When used with tp import, it overwrites the system-dependant objects.
    5: During the import to the consolidation system it permits the source systems other than the integration system.
    6: When used in import phase, it helps to overwrite objects in unconfirmed repairs.
    8: During import phase it ignores the limitations caused by the table classification.
    9: During import it ignores that the system is locked for this kind of transport.
    R3trans: TP uses R3trans program to transport data from one system to another in the CTS pipeline. efficient basis administrator can use R3trans directly to export and import data from and into any SAP systems. Using this utility transport between different database and operating system can e done without any problems. Different versions of R3trans are fully compatible with each other and can be used for export and import. The basis administrator has to be careful using R3trans for different release levels of R/3 software; logical inconsistency might occur if the up to date R3trans is not used for the current version of R/3 system.
    The syntax for using the control file is following:
    R3trans [<options>] <control file> (several options used at the same time; at least one option must be there)
    For example: R3trans u2013u 1 u2013w test.log test
    In the above example a unconditional mode is used, a log file u201Ctest.logu201D file is used to get the log result and a control file u201Ctestu201D, where the instructions are given for the R3trans to follow. The user needs to logon as <sid>adm to execute R3trans.
    The following options are available for the R3trans program:
    R3trans -d : This command is used to check the database connection .
    R3trans -u <int>: Unconditional mode can be used as we have seen in the above example.
    R3trans -v : This is used for verbose mode. It writes additional details to the log file
    R3trans -i <file>: This command directly imports data from data file without a control file.
    R3trans -l <file>: This provides output of a table of contents to the log file.
    R3trans -n : This option provides a brief information about new features of R3trans.
    R3trans u2013t: This option is used for the test mode. All modifications in the database are rolled back.
    R3trans -c <f1> [<f2>]: This command is used for conversion. The <f1> file will be copied to <f2> file after executing a character set conversion to the local character set.
    Important tips: Do not confuse the backup taken using R3trans with database backup. The backups taken using R3trans are logical backups of objects. In case something happens to the SAP system these backups can not be used for recovery. R3trans backups can be only used to restore a copy of a particular object that has been damaged or lost by the user.
    R3trans -w <file>: As we have seen in the above example this option can be used to write to a log file. If no file is mentioned then trans.log is default directory for the log.
    R3trans also can be used for the database backup.
    R3trans u2013ba: This command is used for a complete backup. we will see in the next paragraph how to use
    the control file for the backup.
    R3trans u2013bd: This command is used for a delta backup if the user does not want a complete backup.
    R3trans u2013bi: This option will display backup information.
    The following are some of the examples of control files:
    We have already learned how to use a command for the logical backup of the objects in the database. To get a complete backup the following example control file can be used.
    backup all
    file = /usr/sap/trans/backall
    The option u201Cfile = u2026u201D is the name of the directory into which the data files are to be written. If you are taking a complete backup of DEV system then the backup file is going to look like u201CDEV.A000.bcku201D the next complete
    Reward if useful
    Regards
    divya

  • Javamail Transport.send problem

    I send an email once in a while from my web application on a virtual dedicated server. Usually the email works. But sometimes Transport.send hangs up. Processing just stops at that statement. I don’t get anything from debug.
    public class SendEmail {
        public void SendEmail(String toEmailAddress,
                String fromEmailAddress,
                String smtphost, String subject, String content)
                throws AddressException, MessagingException {
            // Create a mail session
            java.util.Properties props = new java.util.Properties();
            props.put("mail.smtp.host", smtphost);
            props.put("mail.debug", "true");
            Session session = Session.getInstance(props, null);
            // Construct the message
            Message msg = new MimeMessage(session);
            msg.setFrom(new InternetAddress(fromEmailAddress;));
            msg.setRecipient(Message.RecipientType.TO, new InternetAddress(toEmailAddress));
            msg.setSubject(subject);
            msg.setText(content);
            // Send the message
            Transport.send(msg);
            return;
    }What could be causing the problem with Transport.send? Any help would be very much appreciated. Thanks.

    I didn’t get anything from debug. No messages at all. I'm on Centos and looked at the console. Is this not correct?
    I added this code to try to capture exceptions:
    try {
                Transport.send(msg);
            } catch (Exception e) {
                try {
                    out = new BufferedWriter(new FileWriter("TestLog.txt", true));
                    out.newLine();
                    out.write(e.getMessage());
                    out.newLine();
                    out.close(); 
                } catch (Exception err) {
                } finally {
            } finally {
                }But I haven't been able to duplicate the problem since then. I'm not familiar with jstack, so I'll have to research it.
    Thanks for your response.

  • Calling https web service from pl/sql

    hi,
    i've to call a web service from my database, after some research, i've tryed to use utl_dbws package to get the job, i've managed to put to work some of the examples i saw, that allways use http. My webservice is invoked using https with some user credentials.
    i'me getting the following message:
    ORA-29532: Java call terminated by uncaught Java exception: HTTP transport error:
    javax.xml.soap.SOAPException: java.security.PrivilegedActionException:
    javax.xml.soap.SOAPException: Message send failed: Socket is closed
    ORA-06512: at "SYS.UTL_DBWS", line 388
    ORA-06512: at "SYS.UTL_DBWS", line 385
    ORA-06512: at line 85
    i've tryed with this 2 procedures:
    declare
    service_ sys.utl_dbws.SERVICE;
    call_ sys.utl_dbws.CALL;
    service_qname sys.utl_dbws.QNAME;
    port_qname sys.utl_dbws.QNAME;
    operation_qname sys.utl_dbws.QNAME;
    string_type_qname sys.utl_dbws.QNAME;
    retx ANYDATA;
    retx_string VARCHAR2(100);
    retx_len number;
    params sys.utl_dbws.ANYDATA_LIST;
    wsm varchar2(4000);
    config varchar2(4000);
    request sys.XMLTYPE;
    response sys.XMLTYPE;
    begin
    Request := sys.XMLTYPE('<?xml version="1.0" encoding="utf-8"?>'||
    ' <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">'||
    ' <soap:Header>'||
    ' <UserCredentials xmlns="http://tempuri.org/">'||
    ' <UserID>username</UserID>'||
    ' <Password>password</Password>'||
    ' </UserCredentials>'||
    ' </soap:Header>'||
    ' <soap:Body>'||
    ' <GetInfo xmlns="http://tempuri.org/">'||
    ' <wsID>13</wsID>'||
    ' </GetInfo>'||
    ' </soap:Body>'||
    ' </soap:Envelope>');
    service_qname := sys.utl_dbws.to_qname(null, 'GetInfo');
    service_ := sys.utl_dbws.create_service(service_qname);
    operation_qname := sys.utl_dbws.to_qname('http://tempuri.org/', 'GetInfo');
    call_ := sys.utl_dbws.create_call(service_);
    sys.utl_dbws.set_target_endpoint_address(call_, 'https://ws.livesolutions.pt:8800/wsLivesolutions.asmx');
    sys.utl_dbws.set_property( call_
    , 'OPERATION_STYLE'
    , 'document'
    sys.utl_dbws.set_property( call_
    , 'SOAPACTION_URI'
    ,' https://ws.livesolutions.pt:8800/wsLivesolutions');
    response:= sys.utl_dbws.invoke(call_, request);
    END;
    declare
    service_ utl_dbws.SERVICE;
    call_ utl_dbws.CALL;
    service_qname utl_dbws.QNAME;
    port_qname utl_dbws.QNAME;
    operation_qname utl_dbws.QNAME;
    string_type_qname utl_dbws.QNAME;
    retx ANYDATA;
    retx_string VARCHAR2(1000);
    retx_double number;
    retx_len number;
    params utl_dbws.ANYDATA_LIST;
    l_input_params utl_dbws.anydata_list;
    l_result ANYDATA;
    l_namespace VARCHAR2(1000);
    request sys.XMLTYPE;
    response sys.XMLTYPE;
    begin
    l_namespace := 'http://tempuri.org/';
    service_qname := utl_dbws.to_qname(l_namespace, 'wsLivesolutions');
    service_ := utl_dbws.create_service(service_qname);
    port_qname := utl_dbws.to_qname(l_namespace, 'wsLivesolutionsSoap');
    operation_qname := utl_dbws.to_qname(l_namespace, 'GetInfo');
    call_ := utl_dbws.create_call(service_, port_qname, operation_qname);
    utl_dbws.set_target_endpoint_address(call_, 'https://ws.livesolutions.pt:8800/wsLivesolutions.asmx');
    utl_dbws.set_property(call_, 'SOAPACTION_USE', 'TRUE');
    utl_dbws.set_property(call_, 'SOAPACTION_URI', 'http://tempuri.org/GetInfo');
    utl_dbws.set_property(call_, 'OPERATION_STYLE', 'document');
    UTL_DBWS.set_property(call_, 'USERNAME', 'username');
    UTL_DBWS.set_property(call_, 'PASSWORD', 'password');
    string_type_qname := utl_dbws.to_qname('http://www.w3.org/2001/XMLSchema', 'schema');
    utl_dbws.add_parameter(call_, 'wsID', string_type_qname, 'ParameterMode.IN');
    utl_dbws.set_return_type(call_, string_type_qname);
    params(0) := ANYDATA.convertnumber(13);
    retx := utl_dbws.invoke(call_, params);
    utl_dbws.release_service(service_);
    end;
    can anyone help me in this?
    thx

    Are you expecting us to guess at the message you received when you got the 28868?
    I guess: "the wallet is closed."
    If I guessed correctly then open it.
    ALTER SYSTEM SET ENCRYPTION WALLET OPEN IDENTIFIED BY "<your_wallet_password_here>";If I didn't guess correctly then you need to provide all of the information you neglected in your original post.
    Start with the version number.

  • SAAJ0537: Invalid Content-Type. Could be an error message instead of a SOAP

    Hi,
    At present i am using JCAPS version 5.1.1
    com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-
    Type:text/html. Is this an error message instead of a SOAP response?
    I got above error message while invoking the webservice.
    My intention is to get HttpRequest from user and based on the input from user, a web service should be invoked. For this i am using BusinessProcess[einsight]
    In my BusinessProcess, i have HttpServer processRequest service,
    to receive HTTP requests and then i am passing the value of parameter received from http[As String] to next partner which is responsible for invoking a webservice.[Used a wsdl in client mode]
    I am able to get http request successfully , but i got error while invoking web service.
    Please let me know, what to do for rectifying error.

    Although this is an aged topic, this is plaguing our development efforts currently. I have successfully created a webservice that can be executed externally using the generated wsdl but I am unable to get a JCD to execute the WS without getting the following error:
    [#|2007-10-09T19:51:02.700-0700|SEVERE|IS5.1.2|javax.xml.messaging.saaj.soap|_ThreadID=32606; ThreadName=Worker: 34758;|SAAJ0537: Invalid Content-Type. Could be an error message instead of a SOAP message|#]
    [#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
    com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-Type:text/html. Is this an error message instead of a SOAP response?|#]
    [#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.xml.messaging.saaj.soap.MessageImpl.identifyContentType(MessageImpl.java:296)|#]
    [#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:146)|#]
    [#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.createMessage(SOAPMessageFactory1_1Impl.java:32)|#]
    [#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.xml.rpc.client.http.HttpClientTransport.readResponse(HttpClientTransport.java:169)|#]
    [#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:83)|#]
    [#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:69)|#]
    [#|2007-10-09T19:51:02.701-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at tp6.ExecutePortType_Stub.opGetControl(ExecutePortType_Stub.java:66)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at tp6.ExecutePortType_opGetControl.invoke(ExecutePortType_opGetControl.java:188)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.stc.wsclient.runtime.impl.WSDLOtdDelegateImpl.invoke(WSDLOtdDelegateImpl.java:78)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at urn_stc_egate_jce_AI_WebServices_GetControl_jcdGetControl.OpGetControl.invoke(urn_stc_egate_jce_AI_WebServices_GetControl_jcdGetControl.OpGetControl:113)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at AIWebServicesTEST_GetControl_WS.jcdTEST_GetControl_WS.start(jcdTEST_GetControl_WS.java:21)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at TEST_GetControl_WS.cmTEST_GetControl_WS_jcdTEST_GetControl_WS1.jcdTEST_GetControl_WS_Runtime_Handler.handleRequest(jcdTEST_GetControl_WS_Runtime_Handler.java:369)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at sun.reflect.GeneratedMethodAccessor4463.invoke(Unknown Source)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at java.lang.reflect.Method.invoke(Method.java:615)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:140)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:135)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at $Proxy108.handleRequest(Unknown Source)|#]
    [#|2007-10-09T19:51:02.702-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at STC_MDB__eaJCAP_Scheduler_cmTEST_GetControl_WS_jc1527518542.sendMessage(STC_MDB__eaJCAP_Scheduler_cmTEST_GetControl_WS_jc1527518542.java:213)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at STC_MDB__eaJCAP_Scheduler_cmTEST_GetControl_WS_jc1527518542.onContents(STC_MDB__eaJCAP_Scheduler_cmTEST_GetControl_WS_jc1527518542.java:100)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at sun.reflect.GeneratedMethodAccessor4462.invoke(Unknown Source)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at java.lang.reflect.Method.invoke(Method.java:615)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at java.security.AccessController.doPrivileged(AccessController.java:275)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:940)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:948)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:42)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:136)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at $Proxy111.onContents(Unknown Source)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.stc.schedulerotd.scheduleradapter.FileReaderWork.run(FileReaderWork.java:77)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:54)|#]
    [#|2007-10-09T19:51:02.703-0700|WARNING|IS5.1.2|javax.enterprise.system.stream.err|_ThreadID=32606; ThreadName=Worker: 34758;|
         at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:382)|#]
    [#|2007-10-09T19:51:02.704-0700|SEVERE|IS5.1.2|javax.xml.messaging.saaj.soap|_ThreadID=32606; ThreadName=Worker: 34758;|SAAJ0535: Unable to internalize message|#]
    [#|2007-10-09T19:51:02.704-0700|INFO|IS5.1.2|STC.eGate.CMap.Collabs.TEST_GetControl_WS.cmTEST_GetControl_WS_jcdTEST_GetControl_WS1.AIWebServicesTEST_GetControl_WS.jcdTEST_GetControl_WS|_ThreadID=32606; ThreadName=Worker: 34758;|+++EXCEPTION = HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message; nested exception is:
         HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message|#]
    [#|2007-10-09T19:51:02.704-0700|INFO|IS5.1.2|STC.eGate.CMap.Collabs.TEST_GetControl_WS.cmTEST_GetControl_WS_jcdTEST_GetControl_WS1.AIWebServicesTEST_GetControl_WS.jcdTEST_GetControl_WS|_ThreadID=32606; ThreadName=Worker: 34758;|+++STACK     = [Ljava.lang.StackTraceElement;@31de31de|#]
    [#|2007-10-09T19:51:02.705-0700|INFO|IS5.1.2|com.stc.codegen.OTDImpl.runtime.ejb.OTDService|_ThreadID=32606; ThreadName=Worker: 34758;|terminate each service|#]
    Is anybody else having this same error and how was it resolved? Both my client and server settings seems to be in sync. My only iffy piece is the servlet context. For both client and server external components, host, port, servlet context match. What am I missing??

  • PL/SQL Web Service: Broken Pipe

    We have successfully deployed PL/SQL Web Services on the Oracle Application Server 10g with about 6 containers. The web services are being consumed by a .NET application. All seems to be working well but we continually are having intermittent (every 2-3 days) "BROKEN PIPE" errors which is causing us to bounce the container constantly. This is not very effecient for a production environment. Does anybody have any ideas........? Here is what shows up in the log:
    javax.servlet.ServletException: Io exception: Broken pipe
    at swprodweb.__Ws_reservationImplSPWrapper.destroy(__Ws_reservationImplSPWrapper.java:605)
    at oracle.j2ee.ws.RpcWebService.destroy(RpcWebService.java:93)
    at com.evermind.server.http.ServletInstanceInfo.destroy(ServletInstanceInfo.java:127)
    at com.evermind.server.http.HttpApplication.destroyServlets(HttpApplication.java:5805)
    at com.evermind.server.http.HttpApplication.destroy(HttpApplication.java:5732)
    at com.evermind.server.http.HttpSite.destroy(HttpSite.java:881)
    at com.evermind.server.http.HttpServer.destroy(HttpServer.java:613)
    at com.evermind.server.ApplicationServer.destroy(ApplicationServer.java:2033)
    at com.evermind.server.ApplicationServerShutdownHandler.run(ApplicationServerShutdownHandler.java:39)
    at java.lang.Thread.run(Thread.java:534)
    So everytime I see this error I know that we have to bounce the container. Very Frustrating!!

    Hi,
    Although it's a long time since you posted your message, I nowadays working with this issue, that is, calling web services from Oracle database 10g through UTL_DBWS package. It turns out that almost 3 of 100 requests fail due to this error (broken pipe). Actually, the trace is:
    ERROR on line 1:
    ORA-29532: Java call finished due to an unresolved exception: HTTP
    transport error: javax.xml.soap.SOAPException:
    java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message
    send failed: send failed
    Broken pipe
    ORA-06512: en "SYS.UTL_DBWS", línea 403
    ORA-06512: en "SYS.UTL_DBWS", línea 400
    I'm looking for the cause of this error. Has anyone any idea about this?
    Thanks a lot.
    Luis Serrano.

  • Can I Use Boot Camp to Install Windows XP on Late2012 MacMini

    I can't remember everything I've read here in the Community, I still have my Windows XP laptop, haven't used it except to transport videos. Can I use Boot Camp to partition & install the XP on my Dec 2012 Mac Mini? Running Mountain Lion 10.8.5. I still have my Seagate ext HD 1.5 TB, connected to the Mini, but haven't reset it to Mac only. I'm having a slight prob with memory loss, mine, not the Mac's. I think I read that I can't do this with Mountain Lion, but when I try to find what I think I read, it's so far back, I can't get to it. Please help? Thanks in advance.

    The Late 2012 Mac mini only supports 64-bit Windows 7 and 8 versions, so you can't install Windows XP with Boot Camp.
    If you need Windows XP, download an application like Parallels, VMware Fusion or VirtualBox, create a virtual machine and install Windows XP there. You shouldn't have any RAM problem with Windows XP.
    OS X can copy to FAT and exFAT drives, so you can format your external drive in "MS-DOS (FAT)". First, open Finder, choose your external drive in the sidebar and copy all the files to the desktop. Then, use Disk Utility to format your external disk in "MS-DOS (FAT)" > http://pondini.org/OSX/DU1.html Finally, copy all the files back

  • Web Services Connection Timeout

    Hello All,
    I have a web services client that runs in Tomcat. When making a web service call, I am getting the following exception:
    HTTP transport error: java.net.ConnectException: A remote host did not respond within the timeout period.
         at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:87)
         at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:71)
    Initially, I thought this was a tomcat problem and just to prove that it was, I added code to make a HTTPS connection to the server that is running the web service. I am able to connect and download the WSDL through the client code running on Tomcat. So this seems to be a web services client problem rather than a tomcat problem. I am using the following:
    JDK = 1.3.1
    OS = IBM AIX 5.2
    Tomcat = 4.1.27
    Web Services = 1.1
    JAX RPC = 1.0.3
    Any help is appreciated.
    Regards,
    Jeba

    I am able to make HTTPS connection from the Tomcat. If is the connection time out, would that affect the straight HTTPS call also. Also this seems to work on a Windows box. The connection timeout is being received on AIX only and I am able to make HTTPS connection from within tomcat. The web service call using HTTPS is getting the connection time out error message.

  • Assign PO Condition Type to Purchase Order Type

    Dear Gurus,
    I'm trying to assign a condition type which is currently not assigned to a specific PO type. Could anyone give me the flow of configuring PO Condition Types. Thank you VM
    Regards,
    Jin

    uu need to assign ur condition type to the procedure and then assign calculation schema to the vendor the  procedure u define flows through the vendor master not directly according to the document type except stock transport order

  • JWSDP, webservices and weblogic 8.1 talking to a PHP web service

    Hello all. I have a web service client running in weblogic 8.1 on Redhat, when I try to send the data to the service I get:
    Sep 14, 2006 12:00:29 PM com.sun.xml.messaging.saaj.soap.MessageImpl identifyContentType
    SEVERE: SAAJ0537: Invalid Content-Type. Could be an error message instead of a SOAP message
    Sep 14, 2006 12:00:29 PM com.sun.xml.messaging.saaj.soap.MessageImpl <init>
    SEVERE: SAAJ0535: Unable to internalize message
    Thu Sep 14 12:00:29 MDT 2006 RiverbedShipmentSubscriberMDB.createAndSendXML(): Exception: HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message; nested exception is:
            HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
    Thu Sep 14 12:00:30 MDT 2006: email information TO: [email protected] FROM: [email protected]
    Thu Sep 14 12:00:30 MDT 2006: sent mail
    java.rmi.RemoteException: HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message; nested exception is:
            HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
            at com.mcdata.websvc.riverbed.client.DataExchangerSoap_Stub.exchangeData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;(DataExchangerSoap_Stub.java:88)
            at com.mcdata.ejb.riverbedshipment.RiverbedShipmentSubscriberMDB.createAndSendXML(Ljava.lang.String;)V(RiverbedShipmentSubscriberMDB.java:621)
            at com.mcdata.ejb.riverbedshipment.RiverbedShipmentSubscriberMDB.onMessage(Ljavax.jms.Message;)V(RiverbedShipmentSubscriberMDB.java:434)
            at weblogic.ejb20.internal.MDListener.execute(Lweblogic.kernel.ExecuteThread;)V(MDListener.java:382)
            at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:197)
            at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
            at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
    Caused by: HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
            at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(Ljava.lang.String;Lcom.sun.xml.rpc.soap.message.SOAPMessageContext;)V(HttpClientTransport.java:140)
            at com.sun.xml.rpc.client.StreamingSender._send(Ljava.lang.String;Lcom.sun.xml.rpc.client.StreamingSenderState;)V(StreamingSender.java:96)
            at com.mcdata.websvc.riverbed.client.DataExchangerSoap_Stub.exchangeData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;(DataExchangerSoap_Stub.java:72)That is using JSWDP 1.6, when I use 1.3 I get a similar message:
    Thu Sep 14 11:46:29 MDT 2006 RiverbedShipmentSubscriberMDB.createAndSendXML(): Exception: HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html; nested exception is:
            HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html
    Thu Sep 14 11:46:29 MDT 2006: email information TO: [email protected] FROM: [email protected]
    Thu Sep 14 11:46:29 MDT 2006: sent mail
    java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html; nested exception is:
            HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html
            at com.mcdata.websvc.riverbed.client.DataExchangerSoap_Stub.exchangeData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;(DataExchangerSoap_Stub.java:88)
            at com.mcdata.ejb.riverbedshipment.RiverbedShipmentSubscriberMDB.createAndSendXML(Ljava.lang.String;)V(RiverbedShipmentSubscriberMDB.java:621)
            at com.mcdata.ejb.riverbedshipment.RiverbedShipmentSubscriberMDB.onMessage(Ljavax.jms.Message;)V(RiverbedShipmentSubscriberMDB.java:434)
            at weblogic.ejb20.internal.MDListener.execute(Lweblogic.kernel.ExecuteThread;)V(MDListener.java:382)
            at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:197)
            at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
            at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
    Caused by: HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html
            at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(Ljava.lang.String;Lcom.sun.xml.rpc.soap.message.SOAPMessageContext;)V(HttpClientTransport.java:140)
            at com.sun.xml.rpc.client.StreamingSender._send(Ljava.lang.String;Lcom.sun.xml.rpc.client.StreamingSenderState;)V(StreamingSender.java:96)
            at com.mcdata.websvc.riverbed.client.DataExchangerSoap_Stub.exchangeData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;(DataExchangerSoap_Stub.java:72)This makes me think that the PHP web service is returning a content type header of text/html instead of text/xml. Is there a way to make the JWSDP code ignore that or to make the PHP code return the correct header content type?
    Here is a similar thread but I'm not having any luck with the answers in it:
    http://forum.java.sun.com/thread.jspa?threadID=643810

    Hello all. I have a web service client running in weblogic 8.1 on Redhat, when I try to send the data to the service I get:
    Sep 14, 2006 12:00:29 PM com.sun.xml.messaging.saaj.soap.MessageImpl identifyContentType
    SEVERE: SAAJ0537: Invalid Content-Type. Could be an error message instead of a SOAP message
    Sep 14, 2006 12:00:29 PM com.sun.xml.messaging.saaj.soap.MessageImpl <init>
    SEVERE: SAAJ0535: Unable to internalize message
    Thu Sep 14 12:00:29 MDT 2006 RiverbedShipmentSubscriberMDB.createAndSendXML(): Exception: HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message; nested exception is:
            HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
    Thu Sep 14 12:00:30 MDT 2006: email information TO: [email protected] FROM: [email protected]
    Thu Sep 14 12:00:30 MDT 2006: sent mail
    java.rmi.RemoteException: HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message; nested exception is:
            HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
            at com.mcdata.websvc.riverbed.client.DataExchangerSoap_Stub.exchangeData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;(DataExchangerSoap_Stub.java:88)
            at com.mcdata.ejb.riverbedshipment.RiverbedShipmentSubscriberMDB.createAndSendXML(Ljava.lang.String;)V(RiverbedShipmentSubscriberMDB.java:621)
            at com.mcdata.ejb.riverbedshipment.RiverbedShipmentSubscriberMDB.onMessage(Ljavax.jms.Message;)V(RiverbedShipmentSubscriberMDB.java:434)
            at weblogic.ejb20.internal.MDListener.execute(Lweblogic.kernel.ExecuteThread;)V(MDListener.java:382)
            at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:197)
            at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
            at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
    Caused by: HTTP transport error: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
            at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(Ljava.lang.String;Lcom.sun.xml.rpc.soap.message.SOAPMessageContext;)V(HttpClientTransport.java:140)
            at com.sun.xml.rpc.client.StreamingSender._send(Ljava.lang.String;Lcom.sun.xml.rpc.client.StreamingSenderState;)V(StreamingSender.java:96)
            at com.mcdata.websvc.riverbed.client.DataExchangerSoap_Stub.exchangeData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;(DataExchangerSoap_Stub.java:72)That is using JSWDP 1.6, when I use 1.3 I get a similar message:
    Thu Sep 14 11:46:29 MDT 2006 RiverbedShipmentSubscriberMDB.createAndSendXML(): Exception: HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html; nested exception is:
            HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html
    Thu Sep 14 11:46:29 MDT 2006: email information TO: [email protected] FROM: [email protected]
    Thu Sep 14 11:46:29 MDT 2006: sent mail
    java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html; nested exception is:
            HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html
            at com.mcdata.websvc.riverbed.client.DataExchangerSoap_Stub.exchangeData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;(DataExchangerSoap_Stub.java:88)
            at com.mcdata.ejb.riverbedshipment.RiverbedShipmentSubscriberMDB.createAndSendXML(Ljava.lang.String;)V(RiverbedShipmentSubscriberMDB.java:621)
            at com.mcdata.ejb.riverbedshipment.RiverbedShipmentSubscriberMDB.onMessage(Ljavax.jms.Message;)V(RiverbedShipmentSubscriberMDB.java:434)
            at weblogic.ejb20.internal.MDListener.execute(Lweblogic.kernel.ExecuteThread;)V(MDListener.java:382)
            at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:197)
            at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
            at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
    Caused by: HTTP transport error: javax.xml.soap.SOAPException: Unsupported Content-Type: text/html
            at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(Ljava.lang.String;Lcom.sun.xml.rpc.soap.message.SOAPMessageContext;)V(HttpClientTransport.java:140)
            at com.sun.xml.rpc.client.StreamingSender._send(Ljava.lang.String;Lcom.sun.xml.rpc.client.StreamingSenderState;)V(StreamingSender.java:96)
            at com.mcdata.websvc.riverbed.client.DataExchangerSoap_Stub.exchangeData(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Ljava.lang.String;(DataExchangerSoap_Stub.java:72)This makes me think that the PHP web service is returning a content type header of text/html instead of text/xml. Is there a way to make the JWSDP code ignore that or to make the PHP code return the correct header content type?
    Here is a similar thread but I'm not having any luck with the answers in it:
    http://forum.java.sun.com/thread.jspa?threadID=643810

  • Failed to register a web service portlet provider

    Hi,
    I'm trying to register a portlet provider in Portal 11g. however, the following error was returned. Is there anyone can help? Thanks.
    WSDL URL: http://host:port/webapp6/portlets/wsrp2?WSDL
    Error
    ===
    Internal error (WWC-00006)
    Unexpected error - User-Defined Exception (WWC-35000)
    An error occurred during the call to the WSRP Provider: java.rmi.RemoteException: ; nested exception is:
    HTTP transport error: java.io.InterruptedIOException: recv() timed out
    A non-blocking socket operation could not be completed immediately.
    Java stack trace from root exception:
    HTTP transport error: java.io.InterruptedIOException: recv() timed out
    A non-blocking socket operation could not be completed immediately.
    at oracle.webdb.wsrp.client.BaseHTTPClientTransport.invoke(Unknown Source)
    at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java)
    at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:110)
    at oracle.webdb.wsrp.v2.runtime.WSRP_v2_ServiceDescription_Binding_SOAP_Stub.getServiceDescription(Unknown Source)
    at oracle.webdb.wsrp.client.design.v2.OraWSRP_v2_ServiceDescription_PortType.getServiceDescription(Unknown Source)
    CAUSE:
    java.io.InterruptedIOException: recv() timed out
    A non-blocking socket operation could not be completed immediately.
    at oracle.webdb.wsrp.client.BaseHTTPClientTransport.invoke(Unknown Source)
    at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java)
    at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:110)
    at oracle.webdb.wsrp.v2.runtime.WSRP_v2_ServiceDescription_Binding_SOAP_Stub.getServiceDescription(Unknown Source)
    at oracle.webdb.wsrp.client.design.v2.OraWSRP_v2_ServiceDescription_PortType.getServiceDescription(Unknown Source)
    Caused by: java.io.InterruptedIOException: recv() timed out
    A non-blocking socket operation could not be completed immediately.
    at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:129)
    at HTTPClient.BufferedInputStream.fillBuff(BufferedInputStream.java:172)
    at HTTPClient.BufferedInputStream.read(BufferedInputStream.java)
    at HTTPClient.StreamDemultiplexor.read(StreamDemultiplexor.java)
    at HTTPClient.RespInputStream.read(RespInputStream.ja (WWC-43273)

    Finally I restore both Portal 11g and SSO 10g from backup images and the portlets can be resigtered succesfully. It seems that something is corrupted.

  • ADS configuration problem

    Hi guys,
    I'm facing a problem with the configuration of the ADS.
    First I had only ABAP AS, my BASIS man installed for me a JAVA AS beside the ABAP.
    I didn't do any configuration for the ADS or any thing, I started with report FP_PDF_TEST_00 which gave me this error
    ADS:SOAP Runtime Exception: CSoapException Transport :(100101)
    Now I don't know really from where I should start my configuration, and bear in mind that I want to use only the Adobe Print Forms, I don't need interactive forms.
    Reagrds,
    Mahmoud

    Hello ,
       To start with ADS configuration , please check the
    ADS configuration guide provided by SAP -
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30a9630b-4f89-2a10-6fab-e311b3ffd9a6
    you can also take help from link
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/1094a46a-ce44-2a10-e7bf-b934ab505b0a [original link is broken]
    hope this helps.
    Thanks,
    Sahiba

  • Error Handling in XI3

    Hi all,
    I am new to XI. Can anyone guide me how to handle error in XI. To elaborate more, if we use asynchronous or syncronous scenarios and if there are any problems or errors during execution of those scenarios, how to handle that?
    thanks,
    KP

    Hi,
    first you have to distinguish between error handling in the applications and monitoring. As writen before, there is the CCMS and the alerting functions of the XI Runtime Workbench for the monitoring.
    The error handling differs in synchronous and asynchronous scenarios and by the adapters you use. If you are using proxies (ABAP or JAVA) the receiver application can raise an exception. In a synchronous scenario the exception is transported by XI to the sender and a exception is raised there too. You can define different exceptions in the XI repository and add datatypes for specific error data. These fault messages are assigned to an interface and exception classes are generated for the proxies. Unfortunately most adapters don't make it that easy. In RFCs you can use the message structure sy-msgid, sy-msgty, sy-msgno and sy-msgv1 to sy-msgv4. It depends on the adapters what is possible.
    If you are in an asynchronous world, there is no return message to the sender. If a receiver proxy raises an exception, you can see the exception in the inbound monitoring (SXMB_MONI or MessagingSystem) of the receiver system. Then you can use the error monitoring via ccms or alerting, to monitor and report the errors to the operating.
    Another way is to use Acknowlegments to send back the status of the process. In this case you don't handle errors, but send back success messages. If the success messages is not coming back, you know there is a problem. but you need to keep track of your outgoing messages.
    Notice, that if you use the XI messsaging (standard functionality) for error messages, you can not report errors, if the messaging system is broken down. CCMS is working parallel, and low level, to the messaging functionality of XI and can operate, even if XI is not working. It may be good to have a seperate monitoring server like SAP Solution Manager.
    Regards,
    Christian

  • Adobe forms error

    Hi,
    While activating my adobe forms I am getting error message as :
    SOAP Framework error : SOAP Runtime Exception : CSoapException Transport:
    HTTP send failed with exception communication_failure(100.101).
    After pressing activate then
    Also it is not going to activate.
    Can anybody explain me what should be the error.
    Thanks
    naresh

    Hello there.
    I had that problem once. Kindly check SAP note 944221. It's a troubleshouting guide regarding ADS.
    For example, if report FP_PDF_TEST_00 doesn't return ADS version, could mean that ADS is down.
    This note is very well constructed, giving step by step actions to trace what's wrong.
    Best regards.
    Valter Oliveira.

  • Consuming utl_dbws webservice via proxy gives error (sometimes)

    Hi all,
    We provide a webservice for our clients, and some of them have reported they have issues calling a specific operation. Only clients who connect through a proxy have this problem. Others can call the service without issues.
    When I browse to the wsdl (both from my local machine, and via an RDP-session to our customer's network) I get result, so I know the service itself works and that we can connect to it.
    The service has 4 operations, each returning an xmltype.
    When I call the first operation (from my machine aswell as the customer's machine), I get the correct result.
    When I call the second operation from my machine, I get the expected result, but hen I call it from the customer's machine however (which connects via a proxy), the service errors out with following message:
    ORA-29532: Java call terminated by uncaught Java exception: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <HTML dir=ltr><HEAD><TITLE>The page cannot be displayed</TITLE>
    <STYLE>A:link {
         FONT: 8pt/11pt verdana; COLOR: #ff0000
    A:visited {
         FONT: 8pt/11pt verdana; COLOR: #4e4e4e
    </STYLE>
    <META content=NOINDEX name=ROBOTS>
    <META http-equiv=Content-Type coI've written the entire SQLERRM to a table to be sure, but that's all there is in it.
    The operation requires no parameters, so there isn't something wrong with my input.
    The code i use to call the service is as follows:
          -- service en call aanmaken
          v_service := create_service(service_name => to_qname(i_name_space => NULL,
                                                               i_name       => get_ws_param_val(i_ws_code    => i_ws_code,
                                                                                                i_param_code => 'SERVICE_NAME')));
          v_call    := create_call(service_handle => v_service);
          -- proxy instellen indien nodig
          v_proxy := get_ws_param_val(i_ws_code => i_ws_code, i_param_code => 'HTTP_PROXY');
          IF v_proxy IS NOT NULL THEN
             set_http_proxy(httpproxy => v_proxy);
          END IF;
          -- endpoint instellen
          v_endpoint := get_ws_param_val(i_ws_code => i_ws_code, i_param_code => 'ENDPOINT');
          IF instr(lower(v_endpoint), '?wsdl') > 0 THEN
             v_endpoint := substr(v_endpoint, 1, length(v_endpoint) - 5);
          END IF;
          set_target_endpoint_address(call_handle => v_call, endpoint => v_endpoint);
          set_property(call_handle => v_call,
                       key         => 'SOAPACTION_USE',
                       VALUE       => get_operation_param_val(i_ws_code        => i_ws_code,
                                                              i_operation_code => i_ws_operation,
                                                              i_param_code     => 'SOAP_ACTION_USE'));
          set_property(call_handle => v_call,
                       key         => 'SOAPACTION_URI',
                       VALUE       => get_operation_param_val(i_ws_code        => i_ws_code,
                                                              i_operation_code => i_ws_operation,
                                                              i_param_code     => 'SOAP_ACTION_URI'));
          set_property(call_handle => v_call,
                       key         => 'OPERATION_STYLE',
                       VALUE       => get_ws_param_val(i_ws_code    => i_ws_code,
                                                       i_param_code => 'OPERATION_STYLE'));
          set_property(call_handle => v_call,
                       key         => 'ENCODINGSTYLE_URI',
                       VALUE       => get_ws_param_val(i_ws_code    => i_ws_code,
                                                       i_param_code => 'ENCODING_STYLE_URI'));
          -- eventueel username instellen
          v_username := get_ws_param_val(i_ws_code => i_ws_code, i_param_code => 'USERNAME');
          IF v_username IS NOT NULL THEN
             set_property(call_handle => v_call, key => 'USERNAME', VALUE => v_username);
             set_property(call_handle => v_call,
                          key         => 'PASSWORD',
                          VALUE       => get_ws_param_val(i_ws_code    => i_ws_code,
                                                          i_param_code => 'PASSWORD'));
          END IF;
          -- request opbouwen met parameters
          v_target_ns := get_ws_param_val(i_ws_code => i_ws_code, i_param_code => 'TARGET_NAMESPACE');
          v_req_root  := get_operation_param_val(i_ws_code        => i_ws_code,
                                                 i_operation_code => i_ws_operation,
                                                 i_param_code     => 'REQUEST_ROOT');
          v_request   := xmltype('<' || v_req_root || ' xmlns="' || v_target_ns || '"/>');
          v_request   := v_request.appendchildxml(xpath      => '/' || v_req_root,
                                                  value_expr => i_parameters.extract('/parameters/*'),
                                                  namespace  => 'xmlns="' || v_target_ns || '"');
          -- web service oproepen
          v_response := invoke(call_handle => v_call, request => v_request);
          -- vernietigen van gemaakte objecten
          release_call(call_handle => v_call);
          release_service(service_handle => v_service);
          RETURN v_response;The invoke procedure:
       -- Invokes a Document-style webservices in a synchronous
       -- request-response interaction mode.
       --   callHandle - the instance of the call
       --   request - a SOAPElement request
       --   Returns a SOAPElement response
       FUNCTION invoke(call_handle CALL,
                       request     sys.xmltype) RETURN sys.xmltype IS
       BEGIN
          set_call(call_handle);
          RETURN invoke_proxy(request);
       END invoke;
       FUNCTION invoke_proxy(request sys.xmltype) RETURN sys.xmltype AS
          LANGUAGE JAVA NAME 'oracle.jpub.runtime.dbws.DbwsProxy.invokeProxy(oracle.xdb.XMLType) return oracle.xdb.XMLType';I've been searching the web for half a day now and havn't found anything helpful. I'm actually considering rewriting my code to use utl_http (as I've done before) but that would be my last resort.
    Anyone have any ideas as to why this sometimes fails?
    TIA!
    ps: Moderators, if this is in the wrong forum, feel free to move it.
    Edited by: Jo on Jul 16, 2012 3:20 AM -> fixed the code blocks

    Some extra info: the webservice is hosted in an OC4J container on a 10g application server (judging from the Help pages I'm guessing the full version number is 10.1.3).
    I can access the Enterprise Manager and I found a Logs section in there.
    The "Last modified" column for the webservices' Audit and Trace logs show June 30, with a size of 0B (even though I tried again a couple of times today).
    The diagnostic logs (found in the Components -> OC4J -> webservices (this is the container's name) -> Diagnostic Logs section) show a couple of warnings in there on July 16, at about the same time I tried executing the webservice, with a Message Text saying "Unable to determine operation id from SOAP Message.", but there's no log for today, so not really sure if that's the correct file.
    The server.log (Components -> OC4J -> webservices -> server.log) keeps updating, but shows only "oracle.ons.Notification@1b4fd6a" messages, so that's probably not it either.
    I can also see the response/load graph updating as I execute the webservice, so I'm pretty sure connectivity is not the issue here.
    Any advice as to which log file I'm looking for?

Maybe you are looking for