Thursday, June 25, 2009

Summary JUNE 2009

Apa yang best sangat bulan ni yer?

1. First of all, ntah la korang sume ni lupa ke apa.. Birthday aku jatuh bulan ni.. (7.6.1984).. Kepada memember yang wish dan bagi hadiah birthday tu terima kasih yer.. Kalau ada rezeki nanti aku balas hadiah kat korang jugak k..

Hari tu, xder buat pape celebrate pun.. Maklum la, usia dh makin muda.. Xyah la ek.. Baik simpan duit untuk kawin lagi bagus yer dak? Ahaks! Nampaknya hari tu jugak, member se-company and se-sekelas aku kawin.. Ambik berkat 7.6 ek? He3... Ni dia pasangan bahagia tu.. Kalau ada yang x berkesempatan tengok lagi..
2. 21hb 6 hari tu plak.. ada lagi sorang member kawin.. Dia ni house mate aku.. Kelam kabut gak bila dapat tau dia nak kawin.. Yer la kan, nnt sapa lak yang nak ambik alih rumah sewa tu? Fikir punya fikir, aku je la yang ambik alih.. Kalau x, nnt aku nak dok mana plak.. Lagi pun dah lama dok kat rumah tu.. Rasa sayang la plak...

3. Bila dah ada sorang nak kuar kena la cari penganti. Seb baik la si housemate aku yang sorang ni pandai bab2 advertising ni.. He3.. Kejab je dh dapat penganti.. Harap2 housemate yang baru ni pun ok and saling respect each other la.

4. Aku dah kuar dari project kat Taylors... Sayonara Taylors.... Kalau ada rezeki kita jupa lagi... Huhuhuhu.... So.. KFH.. Here I come!

5. Aku dh siapkan OJT report untuk Cosmo... Akhirnya! Siap gak.. Xsangka.. Aku ambik masa 2 hari je untuk siap kan sume 3 bulan report tu.. Isk3..

OK lah.. ni je kot rasanya untuk SUMMARY JUNE 2009...

Monday, May 25, 2009

Berehat Sebentar Bersama NESCAFE ^^

Ermm... Nak tulis pe ek? Dah lama x menconteng kat sini.. Sejak dh kerja ni macam kurang lak idea..

Tadi sempat melawat blog si DarC.. Memang colorful.. Tercabar pulak rasa.. He3.. Tapi xpe.. Kita colorful je blog ni lain kali..

Apa cite hari ni?.. Ok.. Sebelum lupa baik taip kat sini cepat2..
Sejak minggu lepas lg asyik dok customize ProcessPack.. Geram! Asyik xjadi2.. Bila siap deploy.. Asyik Content Publishing Error je.. Pening2.. Akhirnya, problem tu dapat jugak di settle.. Million thanks to Sylvia.. Sbb bgtau yg error logs to ada kat C:\BV1TO1\JBoss\server\bv_framework\log... Kalau x, mmg xder idea nak settle mcmana coding bodoh tu... Dan lagi.. Millions Thanks untuk si Yana jugak yang xjemu2 mentranslate code tu.. JASA KORANG MEMANG AKAN DI KENANG SAMPAI BILA2... Mmuahh..

Thursday, May 14, 2009

Nasi Lemak

Bahan-bahan ( 4-6 orang )

* Bahan untuk nasi:-
* @ 2 cawan beras
* @ 1 cawan santan n 1 cawan air( jun guna 1/2 cwn santan pekat n 1 1/2 cwn air)
* @ 1 helai daun pandan - disimpul
* @ 3 hirisan halia
* @ secubit garam

* Bahan untuk sambal:-
* * 6 sudu besar cili kering mesin
* * 4 ulas bawang merah -ditumbuk
* * 2 ulas bawang putih -ditumbuk
* * 1 biji bawang besar -dihiris
* * segenggam ikan bilis (dibasuh, separuh darinya ditumbuk)
* * sedikit air asam jawa
* * sedikit belacan (jika suka)
* * garam n gula
* Bahan sampingan lain :-
* Ikan bilis goreng, telur rebus dan timun.

Cara-cara

1. Campur semua bahan untuk nasi dan masak seperti nasi biasa.
2. Tumis bawang besar, masukkan bawang2 yg ditumbuk, cili mesin, belacan dan ikan bilis yg ditumbuk..hingga sedikit garing dan pecah minyak.
3. Masukkan air asam dan separuh lagi ikan bilis yg sudah dibersihkan tadi.
4. Masukkan garam n gula. Masak sehingga agak pekat.

Thursday, May 7, 2009

ProcessPack Error

ERROR 2009/05/07 09:47:34:509 broadvision.data.common.XmlUtil.getXsdSchemaFromInstance: Bad input data for insert, update or query operations String index out of range: -1
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name CL_NAME - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name STORE_ID - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name STATUS - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name CL_TYPE - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name AUTHOR_ID - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name START_DATE - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name END_DATE - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name ITEM_CLAIMED - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name CL_IMAGE_WIDTH - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name CL_IMAGE_HEIGHT - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name LOCATION - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name CONTACT_NO - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name CONTACT_STATUS - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.common.XmlUtil.getRowData: Invalid or unknown attribute name EMAIL - data type unknown
ERROR 2009/05/07 09:47:37:978 broadvision.data.client.DataManager.getContentTypeId: Invalid input argument null input: cntTypeName

REASON:

- Database cannot find the specific table.
- parameter setting

SOLUTION:

- check the bv_param.xml file in the svc_ejb and svc_clt folder
- if all the parameter is define just run this command in command prompt:

bvtool set-param -name bv.core.content.BROWSABLE_CONTENT_TYPES -value AD,EDITORIAL,PRODUCT,SSP_PROCESS,URL,BULLETIN,LOSTFOUND,CLASSIFIED

bvtool set-param -name bv.core.content.Filtering.FILTERED_CONTENT_TYPES -value PRODUCT,KM_PROGRAM,SSP_PROCESS,EDITORIAL,AD,URL,BULLETIN,LOSTFOUND,CLASSIFIED

bvtool set-param -name bv.portal.tool.content.PROGRAM_CONTENT_TYPES -value AD,EDITORIAL,PRODUCT,SSP_PROCESS,URL,BULLETIN,LOSTFOUND,CLASSIFIED

bvtool set-param -name bv.portal.services.relatedItem.RELATABLE_CONTENT_TYPES -value CS_MEETING,CS_TASK,DF_MESSAGE,PRODUCT,EDITORIAL,BULLETIN,LOSTFOUND,CLASSIFIED

bvtool set-param -name bv.portal.services.relatedItem.RELATED_ITEM_CONTENT_TYPES -value CS_MDOC,DF_MESSAGE,PRODUCT,EDITORIAL,URL,BULLETIN,LOSTFOUND,CLASSIFIED

bvtool set-param -name bv.portal.services.attachment.ATTACHABLE_CONTENT_TYPES -value EDITORIAL:BV_EP_EDAT,PRODUCT:BV_EP_PDAT,BULLETIN:TC_EP_BDAT,LOSTFOUND:TC_EP_LFDAT,CLASSIFIED:TC_EP_CLDAT

bvtool set-param -name bv.portal.services.content.KEYS -value AD:AD_NAME,EDITORIAL:ED_NAME,PRODUCT:PROD_ID,URL:NAME,BULLETIN:BULLETIN_NAME,LOSTFOUND:LNF_NAME,CLASSIFIED:CL_NAME

Tuesday, April 28, 2009

Install BVNqa49247 for 8.1AB

Install BVNqa49247 for 8.1AB to make content list support dynamic sorting.

1. Update bvmc.war/WEB-INF/conf/view-beans-cm.xml
The file under:($bv1to1\Jboss\server\bv_framework\deploy\bvmc.war)

2. Update cmContentDTO for new common content attributes (make sure the attribute name in upper case)
Add this line:

<form-property name="CREATION_TIME" type="java.util.Date" />

3. Customized the bvmc.war/cm/browse/browseBody.jsp

4. Stop JBOSS

5. Copy patch folder into %BV1TO1%

6. Set environment of BV
cd BV1TO1\bin
BV1TO1\bin>setEnv.cmd

7. Go into BV1TO1\patch\BVNqa49247\installer\bin
run command: install-patch BVNqa49247

Create New Content Type

1. create xml file



2. generate sql script



hsqldb

- run command:

bvtool generate-schema -schema %BV1TO1%\bin\xml\tc_classified.xml - script %BV1TO1%\bin\xml\tc_classified.sql -vendor hsqldb



oracle

- run command:

bvtool generate-schema -schema %BV1TO1%\bin\xml\tc_classified.xml -script %BV1TO1%\bin\xml\tc_classified.sql -vendor oracle



3. execute sql to BVMC database



4. update bv-param.xml



Modify

- C:\BV1TO1\baseSuites\bv_services\modules\svc_ejb\bv_param.xml



<param name="BROWSABLE_CONTENT_TYPES">

<value>new-content-type </value>




<param name="FILTERED_CONTENT_TYPES">

<value> new-content-type </value>




Modify

- C:\BV1TO1\baseSuites\bv_services\modules\svc_clt\bv_param.xml



<param name="PROGRAM_CONTENT_TYPES">

</value> new-content-type </value>




<param name="RELATABLE_CONTENT_TYPES">

</value> new-content-type </value>




- RELATED_ITEM_CONTENT_TYPES



- ATTACHABLE_CONTENT_TYPES



- KEYS



5. run bvtool command : bvtool deploy-config -no-res



6. restart server



7. bvtool set-param



- bvtool set-param -name bv.portal.tool.content.PROGRAM_CONTENT_TYPES -value AD,EDITORIAL,PRODUCT,SSP_PROCESS,URL,BULLETIN,LOSTFOUND,CLASSIFIED

- bvtool deploy-config -no-res



- bvtool set-param -name bv.portal.services.content.KEYS -value AD:AD_NAME,EDITORIAL:ED_NAME,PRODUCT:PROD_ID,URL:NAME,BULLETIN:BULLETIN_NAME,LOSTFOUND:LNF_NAME,CLASSIFIED:CL_NAME

- bvtool deploy-config -no-res



8. generate process pack



- bvant -f %BV1TO1%\lib\generate_publish_pack.xml -DdestDir=%BV1TO1%/tools/eclipse/workspace/ClassifiedPack -Dcontent=CLASSIFIED -DdeployPack=false
-DpackName=ClassifiedPack

Wednesday, April 22, 2009

SMTP Status Codes

These ones are by RFC821

211
System status, or system help reply

214
Help message
(Information on how to use the receiver or the meaning of a particular non-standard command; this reply is useful only to the human user)

220
Service ready

221
Service closing transmission channel

250
Requested mail action okay, completed

251
User not local; will forward to

354
Start mail input; end with .

421
Service not available, closing transmission channel
(This may be a reply to any command if the service knows it must shut down)

450
Requested mail action not taken: mailbox unavailable
(E.g., mailbox busy)

451
Requested action aborted: local error in processing

452
Requested action not taken: insufficient system storage

500
Syntax error, command unrecognized
(This may include errors such as command line too long)

501
Syntax error in parameters or arguments

502
Command not implemented

503
Bad sequence of commands

504
Command parameter not implemented

550
Requested action not taken: mailbox unavailable
(E.g., mailbox not found, no access)

551
User not local; please try

552
Requested mail action aborted: exceeded storage allocation

553
Requested action not taken: mailbox name not allowed
(E.g., mailbox syntax incorrect)

554
Transaction failed (Or, in the case of a connection-opening response, "No SMTP service here")

RFC-2821 defines the following additional

252
Cannot VRFY user, but will accept message and attempt delivery

Better explained codes:

SMTP Reply Codes

When issuing a command, the server will respond with one of the reply codes listed below. As said before, the text associated with the reply code can differ from each server; however, the syntax of the reply defaults to

In case of multiple lines, the syntax of the "text-only" lines is - . The last line is that of the default syntax, so the client understands the server is done with the reply.

The reply codes can be divided into five values for the first digit (out of 3):

1xy Positive Preliminary reply (only for Extended SMTP commands)
2xy Positive Completion reply (The command has been accepted)
3xy Positive Intermediate reply (There should be further information [i.e. DATA])
4xy Transient Negative Completion reply (Command Failed, but can be repeated)
5xy Permanent Negative Completion reply (Command Failed)

The detailed information of the reply codes is listed below

2xy Reply codes

System status, or system help reply (211)
This reply code is followed by information concerning the server, the server status, the server system, or server help.

Reply Code: 211
Issued Command(s): HELP
Standard Timeout: N/A (Server Default)

Help message (214)
This reply code is followed by information on how to use the receiver or the meaning of a command. Usually it provides a list of commands accepted by the server.

Reply Code: 214
Issued Command(s): HELP
Standard Timeout: N/A (Server Default)

Service ready (220)
The 220 reply code is used to confirm connection establishment. It is the primary command after making a TCP connection

Reply Code: 220
Issued Command(s): N/A
Standard Timeout: 5 minutes

Service Closing Transmission Channel (221)
After issuing the Quit command, the server replies with the 221 code, immediately closing the TCP connection. Therefore, this is the final reply code (unless the connection is terminated before closing the session).

Reply Code: 221
Issued Command(s): QUIT
Standard Timeout: N/A (Connection Closed)

Requested mail action okay, completed (250)
This is the most commonly used reply code when a command is accepted and executed without errors. After the 250 reply code the server waits until the next command is issued, or a timeout occurs.

Reply Code: 250
Issued Command(s): HELO, MAIL, RCPT, DATA, RSET, VRFY, NOOP
Standard Timeout: See command description

User not local; will forward to (251)
When the server receives a RCPT or VRFY command, it will try to verify the specified user with the local mailboxes. When the user doesn't exists or has a forward path, the server will reply with the 251 code saying it will accept the user and relay the message.

(Please refer to section 1.3.5 for more information about the 251 and 551 reply codes)

Reply Code: 251
Issued Command(s): RCPT, VRFY
Standard Timeout: 5 Minutes (RCPT command)

Cannot VRFY user, but will accept message and attempt delivery (252)
This code works the same as the 251 reply code; however, it will be issued only in response to the VRFY command.

Reply Code: 252
Issued Command(s): VRFY
Standard Timeout: N/A (Server Default)

3xy Reply codes

Start mail input; end with . (354)
Issued after the DATA command, the 354 code is used to state that more information is required, and thus the server is waiting for the message body.

Reply Code: 354
Issued Command(s): DATA
Standard Timeout: 2 Minutes (DATA command), 3 Minutes (DATA block), 10 Minutes (DATA Termination)

4xy Reply codes

Service not available, closing transmission channel (421)
This reply code is given when the server is temporarily unavailable for accepting connections. This would be the case when the server is in the process of shutting down. This code can be replied during the entire client session if unusual circumstances are encountered

Reply Code: 421
Issued Command(s): N/A
Standard Timeout: N/A (Connection Closed)

Requested mail action not taken: mailbox unavailable (450)
When a user mailbox is busy because of administrative work (i.e. backup), the 450 reply code is generated when the RCPT command is issued. It states that the message cannot be delivered to that user at this time. The client can repeat the command at a later time.

Reply Code: 450
Issued Command(s): RCPT
Standard Timeout: 5 Minutes (RCPT Command)

Requested action aborted: local error in processing (451)
This reply code specifies that an error has occurred while processing the command locally. However, the error is transient, allowing the user to repeat the command after an unspecified period of time.

Reply Code: 451
Issued Command(s): MAIL, RCPT, DATA
Standard Timeout: See command description

Requested action not taken: insufficient system storage (452)
The 452 reply code specifies that the SMTP server system has insufficient storage to process the message. Most SMTP server alerts the system administrator when this happens allowing them to solve the problem and thus giving the client the possibility to repeat the command after an unspecified period of time. This reply code can also be issued when there are too many recipients. See the RCPT command for further details.

Reply Code: 452
Issued Command(s): MAIL, RCPT, DATA
Standard Timeout: See command description

5xy Reply codes

Syntax error, command unrecognized (500)
This reply code is issued when the SMTP server doesn't recognize an SMTP command. It can be issued at any time during the client session. Note that all SMTP servers compliant to the RFC accept the standard commands necessary for sending an e-mail (HELO, MAIL, RCPT, DATA, QUIT). The 500 reply code is also issued when the command line is too long

Reply Code: 500
Issued Command(s): All
Standard Timeout: See command description

Syntax error in parameters or arguments (501)
When a command is recognized but doesn't comply to the specified parameters or arguments, the 501 reply code is returned. This reply code can be issued at any time during the client session. In default, it will be returned when the DATA, RSET or QUIT command have parameters or arguments while no EHLO extensions are available.

Reply Code: 501
Issued Command(s): All
Standard Timeout: N/A (Server Default)

Command not implemented (502)
The 502 Reply code is related to the 500 command with the only difference that this reply code is issued when the server does recognize the command, but didn't implement it, so it cannot be executed. Again, the 502 reply code may not be issued when handling the standard commands necessary for sending an e-mail.

Reply Code: 502
Issued Command(s): VRFY, EXPN, HELP
Standard Timeout: N/A (Server Default)

Bad sequence of commands (503)
When sending e-mail, a default sequence is specified (as shown in 2.2). Not complying with this sequence can result in the 503 reply code. When this code is returned, the server will wait for a new command, preserving the data already supplied.

Reply Code: 503
Issued Command(s): MAIL, RCPT, DATA
Standard Timeout: See command description

Command parameter not implemented (504)
There are a few commands which don't allow command parameters to be supplied. Ignoring this rule will result in a 504 reply code. Below is a list of commands on which this rule applies.

Reply Code: 504
Issued Command(s): HELO, VRFY, EXPN, HELP
Standard Timeout: N/A (Server Default)

Requested action not taken: mailbox unavailable (550) Although similar to the 450 reply code (1.3.3.2), there is one difference. When the 550 reply code is issued by the server, the mailbox or command is permanently unavailable. With the 450 reply code, the client can repeat the command at a later time. The 550 reply code is issued when a mailbox cannot be found, access is prohibited, or the command is rejected based on security/company policies.

Reply Code: 550
Issued Command(s): HELO, MAIL, RCPT, VRFY, EXPN
Standard Timeout: See command description

User not local; please try (551)
Although similar to the 251 reply code (1.3.1.6), the main difference between them is that the server will reject the address when returning a 551 reply code and attempt to deliver the message when returning a 251 reply code.

(Please refer to section 1.3.5 for more information about the 251 and 551 reply codes)

Reply Code: 551
Issued Command(s): RCPT, VRFY
Standard Timeout: See command description

Requested mail action aborted: exceeded storage allocation (552)
The 552 reply code is a remaining instance of the 821 RFC published in 1982. In this RFC, the 552 reply code was designed to alert clients exceeding the number of recipients allowed by the server. However, in the 2821 RFC, the 452 reply code became the appropriate command. Since there is a possibility that there are SMTP servers active that were designed on the 821 RFC, clients should treat the 552 reply code as a 452 temporary failure instead of permanently based on the 5xy logic.

Reply Code: 552
Issued Command(s): RCPT
Standard Timeout: 5 Minutes (RCPT command)

Requested action not taken: mailbox name not allowed (553)
The 553 reply code is issued when an e-mail address parameter of a command is invalid. This can occur because the syntax of the parameter is invalid or because of security/company policies.

Reply Code: 553
Issued Command(s): MAIL, RCPT, VRFY
Standard Timeout: See command description

Transaction failed OR No SMTP service here (554)
When connecting to a SMTP server, the server initiates an SMTP session. In this session the client can issue commands to the server. However, an SMTP server can formally reject an SMTP transaction. If so, the SMTP server will, instead of the normal 220 reply code upon establishing the connection, issue a 554 reply code. The server will maintain the SMTP session until a QUIT command is issued, the connection times out, or the client closed the connection. When receiving a command, with the exception of the QUIT command, after a 554 reply code has been issued, a server will reply with a 503 reply code (1.3.4.4).

Reply Code: 554
Issued Command(s): N/A
Standard Timeout: 5 Minutes

Detailed information about the 251 and 551 reply code
The reason these two reply codes are discussed here is because both deal with the Forward-Path of a mailbox. The Forward-Path can be used by companies or individuals to hide the original address of the user. However, when an SMTP server issues a 251 or 551 reply code, the original address will be revealed. Therefore, most SMTP servers have chosen not to implement these two codes returning a 250 or a 550 reply code instead. If SMTP servers did implement these codes, the server is obliged by the RFC to give users the possibility to disable their use. Also the RFC specifies that the SMTP server SHOULD not expect the client software to update the e-mail address repeating the command. Therefore, implementation of the 251 and 551 reply code within the SMTP client component isn't necessary.

Tuesday, April 21, 2009

Send Email using Servlet

package com.sendNotification;

import java.io.*;
import java.net.*;

import java.util.Properties;
import javax.mail.AuthenticationFailedException;
import javax.mail.Authenticator;
import javax.mail.PasswordAuthentication;
import javax.mail.Message;
import javax.mail.MessagingException;
import javax.mail.Session;
import javax.mail.Transport;
import javax.mail.internet.AddressException;
import javax.mail.internet.InternetAddress;
import javax.mail.internet.MimeMessage;
import javax.servlet.*;
import javax.servlet.http.*;

public class SendNotify extends HttpServlet {

protected void processRequest(HttpServletRequest request,
HttpServletResponse response)
throws IOException, ServletException {

final String err = "./ep/error.jsp";
final String succ = "./ep/success.jsp";

String from = "my@gmail.com"; //gmail acccount
String to = request.getParameter("to");
String subject = request.getParameter("subject");
String message = request.getParameter("message");
String login = "my"; //gmail username
String password = "mymymy"; //gmail password

try {
Properties props = new Properties();
props.setProperty("mail.host", "smtp.gmail.com");
props.setProperty("mail.smtp.port", "587");
props.setProperty("mail.smtp.auth", "true");
props.setProperty("mail.smtp.starttls.enable", "true");

Authenticator auth = new SMTPAuthenticator(login, password);

Session session = Session.getInstance(props, auth);

MimeMessage msg = new MimeMessage(session);
msg.setText(message);
msg.setSubject(subject);
msg.setFrom(new InternetAddress(from));
msg.addRecipient(Message.RecipientType.TO, new InternetAddress(to));
Transport.send(msg);

} catch (AuthenticationFailedException ex) {
request.setAttribute("ErrorMessage", "Authentication failed");

RequestDispatcher dispatcher = request.getRequestDispatcher(err);
dispatcher.forward(request, response);

} catch (AddressException ex) {
request.setAttribute("ErrorMessage", "Wrong email address");

RequestDispatcher dispatcher = request.getRequestDispatcher(err);
dispatcher.forward(request, response);

} catch (MessagingException ex) {
request.setAttribute("ErrorMessage", ex.getMessage());

RequestDispatcher dispatcher = request.getRequestDispatcher(err);
dispatcher.forward(request, response);
}
RequestDispatcher dispatcher = request.getRequestDispatcher(succ);
dispatcher.forward(request, response);

}

private class SMTPAuthenticator extends Authenticator {

private PasswordAuthentication authentication;

public SMTPAuthenticator(String login, String password) {
authentication = new PasswordAuthentication(login, password);
}

protected PasswordAuthentication getPasswordAuthentication() {
return authentication;
}
}

protected void doGet(HttpServletRequest request,
HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}

protected void doPost(HttpServletRequest request,
HttpServletResponse response)
throws ServletException, IOException {
processRequest(request, response);
}


}

Monday, April 20, 2009

Package com.sun.mail.smtp


An SMTP protocol provider for the JavaMail API that provides access to an SMTP server.

See:
Description

Class Summary
SMTPMessage This class is a specialization of the MimeMessage class that allows you to specify various SMTP options and parameters that will be used when this message is sent over SMTP.
SMTPSSLTransport This class implements the Transport abstract class using SMTP over SSL for message submission and transport.
SMTPTransport This class implements the Transport abstract class using SMTP for message submission and transport.

Exception Summary
SMTPAddressFailedException This exception is thrown when the message cannot be sent.
SMTPAddressSucceededException This exception is chained off a SendFailedException when the mail.smtp.reportsuccess property is true.
SMTPSendFailedException This exception is thrown when the message cannot be sent.

Package com.sun.mail.smtp Description

An SMTP protocol provider for the JavaMail API that provides access to an SMTP server. Refer to RFC 821 for more information.

When sending a message, detailed information on each address that fails is available in an SMTPAddressFailedException chained off the top level SendFailedException that is thrown. In addition, if the mail.smtp.reportsuccess property is set, an SMTPAddressSucceededException will be included in the list for each address that is successful. Note that this will cause a top level SendFailedException to be thrown even though the send was successful.

The SMTP provider also supports ESMTP (RFC 1651). It can optionally use SMTP Authentication (RFC 2554) using the LOGIN, PLAIN, and DIGEST-MD5 mechanisms (RFC 2592 and RFC 2831).

To use SMTP authentication you'll need to set the mail.smtp.auth property (see below) and provide the SMTP Transport with a username and password when connecting to the SMTP server. You can do this using one of the following approaches:

  • Provide an Authenticator object when creating your mail Session and provide the username and password information during the Authenticator callback.

    Note that the mail.smtp.user property can be set to provide a default username for the callback, but the password will still need to be supplied explicitly.

    This approach allows you to use the static Transport send method to send messages.

  • Call the Transport connect method explicitly with username and password arguments.

    This approach requires you to explicitly manage a Transport object and use the Transport sendMessage method to send the message. The transport.java demo program demonstrates how to manage a Transport object. The following is roughly equivalent to the static Transport send method, but supplies the needed username and password:

    Transport tr = session.getTransport("smtp");
    tr.connect(smtphost, username, password);
    msg.saveChanges(); // don't forget this
    tr.sendMessage(msg, msg.getAllRecipients());
    tr.close();

When using DIGEST-MD5 authentication, you'll also need to supply an appropriate realm; your mail server administrator can supply this information. You can set this using the mail.smtp.sasl.realm property, or the setSASLRealm method on SMTPTransport.

SMTP can also optionally request Delivery Status Notifications (RFC 1891). The delivery status will typically be reported using a "multipart/report" (RFC 1892) message type with a "message/delivery-status" (RFC 1894) part. JavaMail does not currently provide direct support for these new MIME types, but you can process them as any other "multipart" or "message" content, using MimeMultipart and MimeMessage objects.

See below for the properties to enable these features.

Note also that THERE IS NOT SUFFICIENT DOCUMENTATION HERE TO USE THESE FEATURES!!! You will need to read the appropriate RFCs mentioned above to understand what these features do and how to use them. Don't just start setting properties and then complain to us when it doesn't work like you expect it to work. READ THE RFCs FIRST!!!

The SMTP protocol provider supports the following properties, which may be set in the JavaMail Session object. The properties are always set as strings; the Type column describes how the string is interpreted. For example, use

        props.put("mail.smtp.port", "888");
to set the mail.smtp.port property, which is of type int.

Note that if you're using the "smtps" protocol to access SMTP over SSL, all the properties would be named "mail.smtps.*".

Name Type Description
mail.smtp.user String Default user name for SMTP.
mail.smtp.host String The SMTP server to connect to.
mail.smtp.port int The SMTP server port to connect to, if the connect() method doesn't explicitly specify one. Defaults to 25.
mail.smtp.connectiontimeout int Socket connection timeout value in milliseconds. Default is infinite timeout.
mail.smtp.timeout int Socket I/O timeout value in milliseconds. Default is infinite timeout.
mail.smtp.from String Email address to use for SMTP MAIL command. This sets the envelope return address. Defaults to msg.getFrom() or InternetAddress.getLocalAddress(). NOTE: mail.smtp.user was previously used for this.
mail.smtp.localhost String Local host name used in the SMTP HELO or EHLO command. Defaults to InetAddress.getLocalHost().getHostName(). Should not normally need to be set if your JDK and your name service are configured properly.
mail.smtp.localaddress String Local address (host name) to bind to when creating the SMTP socket. Defaults to the address picked by the Socket class. Should not normally need to be set, but useful with multi-homed hosts where it's important to pick a particular local address to bind to.
mail.smtp.localport int Local port number to bind to when creating the SMTP socket. Defaults to the port number picked by the Socket class.
mail.smtp.ehlo boolean If false, do not attempt to sign on with the EHLO command. Defaults to true. Normally failure of the EHLO command will fallback to the HELO command; this property exists only for servers that don't fail EHLO properly or don't implement EHLO properly.
mail.smtp.auth boolean If true, attempt to authenticate the user using the AUTH command. Defaults to false.
mail.smtp.auth.mechanisms String If set, lists the authentication mechanisms to consider, and the order in which to consider them. Only mechanisms supported by the server and supported by the current implementation will be used. The default is "LOGIN PLAIN DIGEST-MD5", which includes all the authentication mechanisms supported by the current implementation.
mail.smtp.submitter String The submitter to use in the AUTH tag in the MAIL FROM command. Typically used by a mail relay to pass along information about the original submitter of the message. See also the setSubmitter method of SMTPMessage. Mail clients typically do not use this.
mail.smtp.dsn.notify String The NOTIFY option to the RCPT command. Either NEVER, or some combination of SUCCESS, FAILURE, and DELAY (separated by commas).
mail.smtp.dsn.ret String The RET option to the MAIL command. Either FULL or HDRS.
mail.smtp.allow8bitmime boolean If set to true, and the server supports the 8BITMIME extension, text parts of messages that use the "quoted-printable" or "base64" encodings are converted to use "8bit" encoding if they follow the RFC2045 rules for 8bit text.
mail.smtp.sendpartial boolean If set to true, and a message has some valid and some invalid addresses, send the message anyway, reporting the partial failure with a SendFailedException. If set to false (the default), the message is not sent to any of the recipients if there is an invalid recipient address.
mail.smtp.sasl.realm String The realm to use with DIGEST-MD5 authentication.
mail.smtp.quitwait boolean If set to false, the QUIT command is sent and the connection is immediately closed. If set to true (the default), causes the transport to wait for the response to the QUIT command.
mail.smtp.reportsuccess boolean If set to true, causes the transport to include an SMTPAddressSucceededException for each address that is successful. Note also that this will cause a SendFailedException to be thrown from the sendMessage method of SMTPTransport even if all addresses were correct and the message was sent successfully.
mail.smtp.socketFactory SocketFactory If set to a class that implements the javax.net.SocketFactory interface, this class will be used to create SMTP sockets. Note that this is an instance of a class, not a name, and must be set using the put method, not the setProperty method.
mail.smtp.socketFactory.class String If set, specifies the name of a class that implements the javax.net.SocketFactory interface. This class will be used to create SMTP sockets.
mail.smtp.socketFactory.fallback boolean If set to true, failure to create a socket using the specified socket factory class will cause the socket to be created using the java.net.Socket class. Defaults to true.
mail.smtp.socketFactory.port int Specifies the port to connect to when using the specified socket factory. If not set, the default port will be used.
mail.smtp.ssl.enable boolean If set to true, use SSL to connect and use the SSL port by default. Defaults to false for the "smtp" protocol and true for the "smtps" protocol.
mail.smtp.ssl.checkserveridentity boolean If set to true, check the server identity as specified by RFC 2595. These additional checks based on the content of the server's certificate are intended to prevent man-in-the-middle attacks. Defaults to false.
mail.smtp.ssl.socketFactory SSLSocketFactory If set to a class that extends the javax.net.ssl.SSLSocketFactory class, this class will be used to create SMTP SSL sockets. Note that this is an instance of a class, not a name, and must be set using the put method, not the setProperty method.
mail.smtp.ssl.socketFactory.class String If set, specifies the name of a class that extends the javax.net.ssl.SSLSocketFactory class. This class will be used to create SMTP SSL sockets.
mail.smtp.ssl.socketFactory.port int Specifies the port to connect to when using the specified socket factory. If not set, the default port will be used.
mail.smtp.ssl.protocols string Specifies the SSL protocols that will be enabled for SSL connections. The property value is a whitespace separated list of tokens acceptable to the javax.net.ssl.SSLSocket.setEnabledProtocols method.
mail.smtp.ssl.ciphersuites string Specifies the SSL cipher suites that will be enabled for SSL connections. The property value is a whitespace separated list of tokens acceptable to the javax.net.ssl.SSLSocket.setEnabledCipherSuites method.
mail.smtp.mailextension String Extension string to append to the MAIL command. The extension string can be used to specify standard SMTP service extensions as well as vendor-specific extensions. Typically the application should use the SMTPTransport method supportsExtension to verify that the server supports the desired service extension. See RFC 1869 and other RFCs that define specific extensions.
mail.smtp.starttls.enable boolean If true, enables the use of the STARTTLS command (if supported by the server) to switch the connection to a TLS-protected connection before issuing any login commands. Note that an appropriate trust store must configured so that the client will trust the server's certificate. Defaults to false.
mail.smtp.starttls.required boolean If true, requires the use of the STARTTLS command. If the server doesn't support the STARTTLS command, or the command fails, the connect method will fail. Defaults to false.
mail.smtp.userset boolean If set to true, use the RSET command instead of the NOOP command in the isConnected method. In some cases sendmail will respond slowly after many NOOP commands; use of RSET avoids this sendmail issue. Defaults to false.

In general, applications should not need to use the classes in this package directly. Instead, they should use the APIs defined by javax.mail package (and subpackages). Applications should never construct instances of SMTPTransport directly. Instead, they should use the Session method getTransport to acquire an appropriate Transport object.

WARNING: The APIs unique to this package should be considered EXPERIMENTAL. They may be changed in the future in ways that are incompatible with applications using the current APIs.

Thursday, April 16, 2009

BVMC Create Process Pack Error

Buildfile: C:\BV1TO1\lib\deploy-pack.xml

init:

deployBundle:

init:

deployBundle_JBoss:
[java] DeployBundle: started.
[java] DeployBundle: deploying ClassifiedPack/000015
[java] 2009.04.15 17:42:00,312 SGT: executing bundle ClassifiedPack/000015
[java] 2009.04.15 17:42:00,343 SGT: executing Task readinessCheck by rootAgent

[java] -------- Performing readiness checking task --------

[java] Checking whether the application server is running ...

[java] The application server is up.

[java] ======== Finished readiness checking task ========

[java] 2009.04.15 17:42:09,359 SGT: finished Task, readinessCheck, finished by rootAgent: 9016 millis elapsed
[java] 2009.04.15 17:42:09,359 SGT: executing Task common by rootAgent

[java] -------- Performing common SSP deployment task --------

[java] updateProcessPack: true
[java] preCompileJSP: true
[java] validatePack: true
[java] Setting the package 'ClassifiedPack' to status In-Deployment ...
[java] Deploying package 'ClassifiedPack' version 3 ...
[java] Checking package dependency ...

[java] The list of JSPs and AA classes are logged to the following file:
[java] C:\BV1TO1\var/logs/ClassifiedPack_ManualDeploy.log

[java] 2009.04.15 17:42:15,843 SGT: Populating database tables ...

[java] 2009.04.15 17:42:16,93 SGT: invoking deployAllPolicies()

[java] Deploying policies to database ...
[java] Deploying policy 'CheckNewContent.bpolicy'.
[java] Loading rule 'CheckNewContent.rule'.
[java] 2009.04.15 17:42:16,906 SGT: invoking deployAllPageflowJsp()
[java] Copying all pageflow JSPs ...
[java] 2009.04.15 17:42:16,906 SGT: invoking deployAllForms()
[java] Deploying forms ....
[java] runtimeRoot: appConfig/bv_framework/sspPackages/ClassifiedPack/version3
[java] packageRoot: C:\BV1TO1\var\appConfig\bv_framework\deployer\bundles\ClassifiedPack\000015
[java] Runtime Directory: C:\BV1TO1\var\appConfig\bv_framework\sspPackages\ClassifiedPack\version3\originals
[java] Bundle Directory: C:\BV1TO1\var\appConfig\bv_framework\deployer\bundles\ClassifiedPack\000015
[java] Processing: forms/CreateUpdateCLASSIFIEDForm.form
[java] Generating JSP files for form 'CreateUpdateCLASSIFIEDForm_Portal'.
[java] Processing: forms/CreateUpdateCLASSIFIEDForm_Portal.form
[java] Generating JSP files for form 'CreateUpdateCLASSIFIEDForm_Portal'.
[java] Processing: forms/ViewCLASSIFIEDForm.form
[java] Generating JSP files for form 'ViewCLASSIFIEDForm'.
[java] Processing: forms/ViewCLASSIFIEDVersionForm.form
[java] Generating JSP files for form 'ViewCLASSIFIEDVersionForm'.
[java] Generating standard error pages ...

[java] Compiling all form JSPs ...

[java] [PageFlowJspLoader] Parsing JSP in C:\BV1TO1\var\appConfig\bv_framework\deployer\bundles\ClassifiedPack\000015\generated\formJsp...
[java] execute JBoss jasper compiler
[java] 2009.04.15 17:42:30,500 SGT: invoking deployAllCollabTemplates()
[java] Deploying collaboration templates ....
[java] 2009.04.15 17:42:30,500 SGT: invoking deployActorAndGroupTable()

[java] 2009.04.15 17:42:30,765 SGT: invoking populateProcessTables()
[java] Deploying processes ...
[java] Deploying process 'CreateUpdateCLASSIFIED'
[java] 139578739
[java] Deploying process 'CreateUpdateCLASSIFIED_Portal'
[java] com.broadvision.data.exceptions.DuplicateDataException: SQL ErrorCode=-9, State=23000, Message=Violation of unique index: BV_PROCESS_KEY_IDX in statement [INSERT INTO BV_PROCESS (NAME, TYPE, GUID, DESCRIPTION, PACKAGE_NAME, DEFINITION_OID, STATUS, OID, STORE_ID, CREATION_TIME, DELETED, LAST_MOD_TIME)VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[java] at com.broadvision.data.exceptions.DBExceptionHandler.HSQLDBHandler(DBExceptionHandler.java:249)
[java] at com.broadvision.data.exceptions.DBExceptionHandler.handle(DBExceptionHandler.java:91)
[java] at com.broadvision.data.exceptions.DBExceptionHandler.handle(DBExceptionHandler.java:61)
[java] at com.broadvision.data.server.ContentDao.insertBVContent(ContentDao.java:1953)
[java] at com.broadvision.data.server.ContentDao.insertContent(ContentDao.java:661)
[java] at com.broadvision.data.ejb.content.ContentDbSLBean.createContent(ContentDbSLBean.java:1202)
[java] at sun.reflect.GeneratedMethodAccessor1636.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
[java] at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:237)
[java] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158)
[java] at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:169)
[java] at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
[java] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
[java] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:350)
[java] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
[java] at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
[java] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
[java] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
[java] at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
[java] at org.jboss.ejb.Container.invoke(Container.java:954)
[java] at sun.reflect.GeneratedMethodAccessor330.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
[java] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
[java] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
[java] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
[java] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
[java] at org.jboss.invocation.local.LocalInvoker$MBeanServerAction.invoke(LocalInvoker.java:169)
[java] at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:118)
[java] at org.jboss.invocation.InvokerInterceptor.invokeLocalMarshalled(InvokerInterceptor.java:295)
[java] at org.jboss.invocation.MarshallingInvokerInterceptor.invoke(MarshallingInvokerInterceptor.java:61)
[java] at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
[java] at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
[java] at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:112)
[java] at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
[java] at $Proxy144.createContent(Unknown Source)
[java] at com.broadvision.data.ejb.content.ContentInfoSLBean.createContent(ContentInfoSLBean.java:1455)
[java] at sun.reflect.GeneratedMethodAccessor1635.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
[java] at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:237)
[java] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158)
[java] at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
[java] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
[java] at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:173)
[java] at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77)
[java] at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:169)
[java] at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
[java] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
[java] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136)
[java] at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
[java] at org.jboss.ejb.Container.invoke(Container.java:954)
[java] at sun.reflect.GeneratedMethodAccessor330.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
[java] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
[java] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
[java] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
[java] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
[java] at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
[java] at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
[java] at sun.reflect.GeneratedMethodAccessor335.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:585)
[java] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
[java] at sun.rmi.transport.Transport$1.run(Transport.java:153)
[java] at java.security.AccessController.doPrivileged(Native Method)
[java] at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
[java] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
[java] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
[java] at java.lang.Thread.run(Thread.java:595)
[java] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
[java] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
[java] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
[java] at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
[java] at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
[java] at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
[java] at org.jboss.invocation.MarshallingInvokerInterceptor.invoke(MarshallingInvokerInterceptor.java:63)
[java] at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)
[java] at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
[java] at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:112)
[java] at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
[java] at $Proxy5.createContent(Unknown Source)
[java] at com.broadvision.data.client.DataManagerImpl.createContent(DataManagerImpl.java:580)
[java] at com.broadvision.data.client.DataManager.createContent(DataManager.java:1026)
[java] at com.broadvision.ssp.deployment.SspProcessDeploy.populateProcessTables(SspProcessDeploy.java:526)
[java] at com.broadvision.ssp.deployment.SspPackageDeploy.populateProcessTables(SspPackageDeploy.java:897)
[java] at com.broadvision.ssp.deployment.SspPackageDeploy.populateDbTables(SspPackageDeploy.java:558)
[java] at com.broadvision.ssp.deployment.CommonTask.deployPackage(CommonTask.java:273)
[java] at com.broadvision.ssp.deployment.CommonTask.performTask(CommonTask.java:188)
[java] at com.broadvision.ssp.deployment.CommonTask.perform(CommonTask.java:108)
[java] at com.broadvision.deployer.tasks.TaskExecution.run(TaskExecution.java:122)
[java] at com.broadvision.deployer.agent.LocalAgent.performTask(LocalAgent.java:59)
[java] at com.broadvision.deployer.coord.LocalCoordinator.executeBundle(LocalCoordinator.java:204)
[java] at com.broadvision.deployer.coord.LocalCoordinator.executeBundle(LocalCoordinator.java:153)
[java] at com.broadvision.deployer.utils.DeployBundle.doIt(DeployBundle.java:35)
[java] at com.broadvision.deployer.utils.DeployBundle.main(DeployBundle.java:57)
[java] com.broadvision.ssp.exceptions.SspDeployException: SQL ErrorCode=-9, State=23000, Message=Violation of unique index: BV_PROCESS_KEY_IDX in statement [INSERT INTO BV_PROCESS (NAME, TYPE, GUID, DESCRIPTION, PACKAGE_NAME, DEFINITION_OID, STATUS, OID, STORE_ID, CREATION_TIME, DELETED, LAST_MOD_TIME)VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[java] at com.broadvision.ssp.deployment.SspProcessDeploy.populateProcessTables(SspProcessDeploy.java:554)
[java] at com.broadvision.ssp.deployment.SspPackageDeploy.populateProcessTables(SspPackageDeploy.java:897)
[java] at com.broadvision.ssp.deployment.SspPackageDeploy.populateDbTables(SspPackageDeploy.java:558)
[java] at com.broadvision.ssp.deployment.CommonTask.deployPackage(CommonTask.java:273)
[java] at com.broadvision.ssp.deployment.CommonTask.performTask(CommonTask.java:188)
[java] at com.broadvision.ssp.deployment.CommonTask.perform(CommonTask.java:108)
[java] at com.broadvision.deployer.tasks.TaskExecution.run(TaskExecution.java:122)
[java] at com.broadvision.deployer.agent.LocalAgent.performTask(LocalAgent.java:59)
[java] at com.broadvision.deployer.coord.LocalCoordinator.executeBundle(LocalCoordinator.java:204)
[java] at com.broadvision.deployer.coord.LocalCoordinator.executeBundle(LocalCoordinator.java:153)
[java] at com.broadvision.deployer.utils.DeployBundle.doIt(DeployBundle.java:35)
[java] at com.broadvision.deployer.utils.DeployBundle.main(DeployBundle.java:57)
[java] Setting the package 'ClassifiedPack' to status Error ...
[java] com.broadvision.ssp.exceptions.SspDeployException: SQL ErrorCode=-9, State=23000, Message=Violation of unique index: BV_PROCESS_KEY_IDX in statement [INSERT INTO BV_PROCESS (NAME, TYPE, GUID, DESCRIPTION, PACKAGE_NAME, DEFINITION_OID, STATUS, OID, STORE_ID, CREATION_TIME, DELETED, LAST_MOD_TIME)VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[java] at com.broadvision.ssp.deployment.CommonTask.performTask(CommonTask.java:215)
[java] at com.broadvision.ssp.deployment.CommonTask.perform(CommonTask.java:108)
[java] at com.broadvision.deployer.tasks.TaskExecution.run(TaskExecution.java:122)
[java] at com.broadvision.deployer.agent.LocalAgent.performTask(LocalAgent.java:59)
[java] at com.broadvision.deployer.coord.LocalCoordinator.executeBundle(LocalCoordinator.java:204)
[java] at com.broadvision.deployer.coord.LocalCoordinator.executeBundle(LocalCoordinator.java:153)
[java] at com.broadvision.deployer.utils.DeployBundle.doIt(DeployBundle.java:35)
[java] at com.broadvision.deployer.utils.DeployBundle.main(DeployBundle.java:57)
[java] SQL ErrorCode=-9, State=23000, Message=Violation of unique index: BV_PROCESS_KEY_IDX in statement [INSERT INTO BV_PROCESS (NAME, TYPE, GUID, DESCRIPTION, PACKAGE_NAME, DEFINITION_OID, STATUS, OID, STORE_ID, CREATION_TIME, DELETED, LAST_MOD_TIME)VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]
[java] The deployment common task failed.
[java] 2009.04.15 17:42:31,500 SGT: failed to finish Task, common, finished by rootAgent: 22141 millis elapsed
[java] DeployBundle: failed to deploy ClassifiedPack/000015.
[java] DeployBundle: finished (-3).
[DEPLOY_STDERR]-->

BUILD FAILED
C:\BV1TO1\lib\deploy-pack.xml:577: The following error occurred while executing this line:
C:\BV1TO1\lib\deploy-pack.xml:584: Java returned: -3


Total time: 35 seconds
<--[DEPLOY_STDERR]

Solution:

Delete the key from table BV_PROCESS

SELECT * FROM BV_PROCESS

DELETE FROM BV_PROCESS WHERE OID = 8707

.... and then deploy again..

u'll success...

... and then... another problem raised!!!
Related Posts Plugin for WordPress, Blogger...