Use o comando pkgrm BFAgent para remover o agente existente do Build Forge no Solaris antes de executar o comando pkgadd.
A URL do modelo de notificação abre o relatório de tarefas do Build Forge quando você clica no link da URL no e-mail de notificação.
Nas versões 7.0.1 e 7.1, a URL nos modelos de notificação mudou; consequentemente, poderá não funcionar quando você atualizar da versão 7.0 para uma mais recente.
http://${CONSOLEHOST}:${CONSOLEPORT}/fullcontrol/index.php?mod=projectruns&action=
edit&bfid=${PID}&bfid=${BID}&bfid=${UID}
Elementos de URL | Elementos de URL da versão 7.0.1 (e superiores) |
---|---|
projectruns | jobs |
& | & |
action=edit | action=build.view |
&bfid=${PID} | &bfid=${BID} | &bfid=${UID} | &bf_id=${BID} |
Se o Rational Build Forge começar a não responder, consulte os logs em <bfinstall>/Apache/tomcat/logs/ (UNIX ou Linux) ou <bfinstall>\Apache\tomcat\logs\ (Windows) para obter uma mensagem similar a seguinte:
Services: 20075: CRRBF1381I: Established connection to Build Forge Services.
DBD::DB2::st execute failed: [IBM][CLI Driver] SQL30081N A communication error has been detected.
Communication protocol being used: "TCP/IP".
Communication API being used: "SOCKETS".
Location where the error was detected: "XXX.XXX.XXX.XXX".
Communication function detecting the error: "recv".
Protocol specific error code(s): "131", "*", "0". SQLSTATE=08001
August 17, 2010 7:18:14 AM EDT
Database: 20075: CRRBFEEEEE: DBD::DB2::st execute failed:
[IBM][CLI Driver] SQL30081N Um erro de comunicação foi detectado.
Communication protocol being used: "TCP/IP".
Communication API being used: "SOCKETS".
Location where the error was detected: "XXX.XXX.XXX.XXX".
Communication function detecting the error: "recv".
Protocol specific error code(s): "131", "*", "0". SQLSTATE=08001
Database: 20075: CRRBF0551I: StackTrace from Process id [20075] called from [
BuildForge::DB::db2(./PerlApp/BuildForge/DB/db2.pm:65)
BuildForge::Utilities::SysParams(./PerlApp/BuildForge/Utilities/SysParams.pm:57)
main(.buildforge.pl:305)
main(.buildforge.pl:213)
]
Database: 20075: CRRBF0556I: Trying to call [execute] on a non-existant database handle
DBD::DB2::st fetchrow_hashref failed: no statement executing at /PerlApp/BuildForge/DB/db2.pm
line 78, <$sock> line 1054.
20075: CRRBF0555E: Problem performing Database Operation [fetchrow_hashref] : DBD::DB2::st
fetchrow_hashref failed: no statement executing at /PerlApp/BuildForge/DB/db2.pm
line 78, <$sock> line 1054.
Database: 20075: CRRBFEEEEE: DBD::DB2::st fetchrow_hashref failed: no statement executing
at /PerlApp/BuildForge/DB/db2.pm line 78, <$sock> line 1054.
Database: 20075: CRRBF0551I: StackTrace from Process id [20075] called from [
BuildForge::Utilities::SysParams(./PerlApp/BuildForge/Utilities/SysParams.pm:59)
main(.buildforge.pl:305)
main(.buildforge.pl:213)
]
[IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003 at /PerlApp/BuildForge/DB/Handle.pm line 385, <$sock> line 1054.
Database: 20075: CRRBF0555E: Problem performing Database Operation [prepare] :
query [SELECT * FROM bf_jobcount WHERE bf_engine_id=?]
DBD::DB2::db prepare failed: [IBM][CLI Driver] CLI0106E Connection is closed.
SQLSTATE=08003 at /PerlApp/BuildForge/DB/Handle.pm line 385, <$sock> line 1054.
Database: 20075: CRRBFEEEEE: DBD::DB2::db prepare failed: [IBM][CLI Driver] CLI0106E
Connection is closed. SQLSTATE=08003 at /PerlApp/BuildForge/DB/Handle.pm line 385, <$sock> line 1054.
em que XXX.XXX.XXX.XXX é o servidor que hospeda seu banco de dados.
Essa mensagem indica que não há conexão entre o Rational Build Forge e o banco de dados.
Para restabelecer a conexão: