Utilice el mandato pkgrm BFAgent para eliminar el agente de Build Forge de Solaris existente antes de ejecutar el mandato pkgadd.
El URL de la plantilla de notificación abre el informe de trabajo de Build Forge al pulsar el enlace URL del correo electrónico de notificación.
En las versiones 7.0.1 y 7.1, el URL de las plantillas de notificación ha cambiado; en consecuencia, es posible que el URL no funcione al actualizar de 7.0 a una versión posterior.
http://${CONSOLEHOST}:${CONSOLEPORT}/fullcontrol/index.php?mod=projectruns&action=
edit&bfid=${PID}&bfid=${BID}&bfid=${UID}
Elementos de URL | Elementos de URL de la versión 7.0.1 (y posteriores) |
---|---|
projectruns | jobs |
& | & |
action=edit | action=build.view |
&bfid=${PID} | &bfid=${BID} | &bfid=${UID} | &bf_id=${BID} |
Si Rational Build Forge no responde, compruebe los registros en <bfinstall>/Apache/tomcat/logs/ (UNIX o Linux) o <bfinstall>\Apache\tomcat\logs\ (Windows) para obtener un mensaje parece al siguiente:
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 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
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.
donde XXX.XXX.XXX.XXX es el servidor que aloja la base de datos.
Este mensaje indica que no hay conexión entre Rational Build Forge y la base de datos.
Para volver a establecer la conexión: