I can not access the Build Forge after migrating the databas
Hi
Good afternoon.
It was the migration from one server to another database (SQL) of Build Forge. To reconnect to this database is made all the steps to modify and update the file buildforge.conf as BuildForge-InstallGuide-7114.
After completing this activity successfully, you try to access Build Forge, as follows:
Place the username and password in the login window of the Build Forge, and click on "login"
Then a message appears stating:
Loading and next to this post another message that says "click here if not redirected automatically"
Pressed in the above message appears again and login window that Build Forge to re-enter the username and password. He again entered username and password, the message reappears:
Loading and next to this post another message that says "click here if not redirected automatically," and again and again pressed the message window appears Build Forge login, and you cannot access the tool.
We consulted with the database area and indicated that they attempt to log the audit log database as the user configured displays and out user_build immediately.
In the file: catalina.2011-1021.log, see the following message:
Oct 21, 2011 12:27:03 PM com.buildforge.services.server.dispatch.Dispatcher signal
WARNING: !!!
java.io.IOException: An existing connection was forcibly closed by the remote host.
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:52)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:267)
at sun.nio.ch.IOUtil.read(IOUtil.java:240)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236)
at com.buildforge.services.server.dispatch.handler.BufferedConnection.signal(BufferedConnection.java:205)
at com.buildforge.services.server.dispatch.Dispatcher.signal(Dispatcher.java:238)
at com.buildforge.services.server.dispatch.Dispatcher.run(Dispatcher.java:203)
Please could tell what might be happening, you cannot access the tool?
Thanking you in advance for your cooperation.
Regards
Good afternoon.
It was the migration from one server to another database (SQL) of Build Forge. To reconnect to this database is made all the steps to modify and update the file buildforge.conf as BuildForge-InstallGuide-7114.
After completing this activity successfully, you try to access Build Forge, as follows:
Place the username and password in the login window of the Build Forge, and click on "login"
Then a message appears stating:
Loading and next to this post another message that says "click here if not redirected automatically"
Pressed in the above message appears again and login window that Build Forge to re-enter the username and password. He again entered username and password, the message reappears:
Loading and next to this post another message that says "click here if not redirected automatically," and again and again pressed the message window appears Build Forge login, and you cannot access the tool.
We consulted with the database area and indicated that they attempt to log the audit log database as the user configured displays and out user_build immediately.
In the file: catalina.2011-1021.log, see the following message:
Oct 21, 2011 12:27:03 PM com.buildforge.services.server.dispatch.Dispatcher signal
WARNING: !!!
java.io.IOException: An existing connection was forcibly closed by the remote host.
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:52)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:267)
at sun.nio.ch.IOUtil.read(IOUtil.java:240)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236)
at com.buildforge.services.server.dispatch.handler.BufferedConnection.signal(BufferedConnection.java:205)
at com.buildforge.services.server.dispatch.Dispatcher.signal(Dispatcher.java:238)
at com.buildforge.services.server.dispatch.Dispatcher.run(Dispatcher.java:203)
Please could tell what might be happening, you cannot access the tool?
Thanking you in advance for your cooperation.
Regards
5 answers
Hi, good day.
The database is initially installing the tool, even as we have worked on it, hence moved from server to not lose your work. This was what was done to migrate the database to another server, separate lists techniques that were required to do so. Then buildforge.conf file was modified, as indicated in manual to continue using the database and not have to create a new one.
The databases are the same level of Build Forge and the same supplier, as I explained is the same database which had been working.
The result of this work was exhibited in the previous query.
I appreciate your help.
Regards
The database is initially installing the tool, even as we have worked on it, hence moved from server to not lose your work. This was what was done to migrate the database to another server, separate lists techniques that were required to do so. Then buildforge.conf file was modified, as indicated in manual to continue using the database and not have to create a new one.
The databases are the same level of Build Forge and the same supplier, as I explained is the same database which had been working.
The result of this work was exhibited in the previous query.
I appreciate your help.
Regards
Hello,
From you initial description, it appears that you had update only one of the buildforge.conf file used to configure the database connection.
There is a second buildforge.conf file that is used by the Build Forge service layer, handled by the Tomcat service under default installations.
Please ensure that the buildforge.conf file located under the service layer has been updated to reflect the new database connection settings.
You may also copy the buildforge.conf file from the install directory.
The service layer buildforge.conf file will be located under the following under default installation with Tomcat.
Windows: %BF_HOME%\Apache\tomcat\webapps\rbf-services\WEB-INF\classes
UNIX\Linux: $BF_HOME/server/tomcat/webapps/rbf-services/WEB-INF/classes/
After updating the service layer buildforge.conf, you must restart Build Forge to take effect.
From you initial description, it appears that you had update only one of the buildforge.conf file used to configure the database connection.
There is a second buildforge.conf file that is used by the Build Forge service layer, handled by the Tomcat service under default installations.
Please ensure that the buildforge.conf file located under the service layer has been updated to reflect the new database connection settings.
You may also copy the buildforge.conf file from the install directory.
The service layer buildforge.conf file will be located under the following under default installation with Tomcat.
Windows: %BF_HOME%\Apache\tomcat\webapps\rbf-services\WEB-INF\classes
UNIX\Linux: $BF_HOME/server/tomcat/webapps/rbf-services/WEB-INF/classes/
After updating the service layer buildforge.conf, you must restart Build Forge to take effect.
Hello, good day.
Dear Joshua.
Is that you mentioned was what was done after migrating the database. According to the chapter that talks about the configuration file Buiid Forge (buildforge.conf) in the document entitled BuildForge-InstallGuide-7114, on page 74.
Could you tell me that another library is the other file buildforge.conf?, Since the only place I know is: Windows:% BF_HOME% \ Apache \ tomcat \ webapps \ rbf-services \ WEB-INF \ classes, as according to the manual modification is made on this directory.
We appreciate your help
Regarts
Dear Joshua.
Is that you mentioned was what was done after migrating the database. According to the chapter that talks about the configuration file Buiid Forge (buildforge.conf) in the document entitled BuildForge-InstallGuide-7114, on page 74.
Could you tell me that another library is the other file buildforge.conf?, Since the only place I know is: Windows:% BF_HOME% \ Apache \ tomcat \ webapps \ rbf-services \ WEB-INF \ classes, as according to the manual modification is made on this directory.
We appreciate your help
Regarts
There are two buildforge.conf files that must be updated if the database connection settings have changed.
%BF_HOME%\buildforge.conf
%BF_HOME%\Apache\tomcat\webapps\rbf-services\WEB-INF\classes\buildforge.conf
If the issue you are encountering is user are not able to access the console after logging in, please ensure that user are not access the console via the login page directly.
ie:
https://myhost.mydomain.com:8443/rbf-services/login.jsp
If user attempt to access Build Forge via the login page directly, they may not be redirected to the console appropriately.
User who have logged in and are redirected to the login page should attempt to access the Build Forge console directly via the Apache (port 80) address.
ie:
http://myhost.mydomain.com/fullcontrol
User who have the Build Forge console bookmarked to the login page should update the bookmarks to console page.
If you are still having issue afterwards, please open a PMR with Build Forge Support for assistance.
%BF_HOME%\buildforge.conf
%BF_HOME%\Apache\tomcat\webapps\rbf-services\WEB-INF\classes\buildforge.conf
If the issue you are encountering is user are not able to access the console after logging in, please ensure that user are not access the console via the login page directly.
ie:
https://myhost.mydomain.com:8443/rbf-services/login.jsp
If user attempt to access Build Forge via the login page directly, they may not be redirected to the console appropriately.
User who have logged in and are redirected to the login page should attempt to access the Build Forge console directly via the Apache (port 80) address.
ie:
http://myhost.mydomain.com/fullcontrol
User who have the Build Forge console bookmarked to the login page should update the bookmarks to console page.
If you are still having issue afterwards, please open a PMR with Build Forge Support for assistance.