I have a problem with tibco Administrator TEA. My Tibco project is using a database connection with mysql server , and I have deployed it on TEA , when the Database Server is Down I see in Tibco logs DB Connection failed and when the database server is again up I am still seeing in Tibco logs DB Connection is failed , to solve that i need to restart the AppNode but I don't want to restart it every time . Is there any way to avoid that and let my application work automatically when the DB Server is up again . Thanks in advance
doesn't restart of application work? Do as follows:
* create moduleActivator process and include DBConnection call there and load all configuration within it to be used within process
* in the same bwp, catch exception event and do shutdown procedure, which will shut down your application.
Once DB connection is up, just start up your engine again and it should work without any exceptions.
Check and let me know if it works. If it doesn't, please share logs.
Related
I have a WebLogic server and oracle db. At some point WebLogic server returns with ORA-1422 error but while executing the same procedure from backend it works. Also this will work when I restart the WebLogic server.
Any idea why its happening like this and any resolutions?
If you have uncommitted data then it is only visible to the session in which the data was inserted/updated and each connection will be a different session even if you are connecting as the same user.
Therefore, if you insert/update some data and end up with duplicate data but forget to COMMIT it in the WebLogic server then you will only see the issue in the WebLogic server (particularly if you are using a connection pool and you are reusing the same connection and session over-and-over) because that session is the only one that can see the uncommitted data.
You will not see the issue from other connections (i.e. if you connect to the backend or if you close and reopen the WebLogic server's connections).
You need to check that you are always committing your data.
Currently using version 7.13.2 with MySQL database.
When the usage in production server is high (with alot of concurrent user), Umbraco tend to create alot of database connection to handle those job. Those connection is not close after used but sleep.
Umbraco would continue to create more database connection when necessary until it reach the database max pool size.
Is this the intention behaviour by Umbraco? Else, how could we configure this issue?
After hundred hours of debugging, I finally found out the cause and the solution is easy.
This bug has nothing to do with Umbraco, it handles the connection perfectly. Umbraco using MySql Connector when connecting to MySql database. When the connection close, it is actually not close but instead, added to connection pool. Please refer to link below for more information.
MySql Connection not closing using .net MySql Connector
The solution as suggested from the link, just adding "Pooling=false" as a string parameter into connection string. The connection string locate inside the web config.
enter image description here
I am trying to connect to a sybase ASE 15 enterprise edition database. Initially the connection is working fine but suddenly the page becomes unresponsive. There are no exceptions in the log nor is there any error displayed on the page. Also I have noticed that only the connection related to a particular database is unresponsive and remaining all are working just fine. However, if I restart the server, everything's working fine.
I have tried to increase the number of user connections and modified sytem configurations. But the result is all the same. Please help me out
I recommend you trace the session to get more log information:
1- initiate a connection to the database
2- use the stored procedure'sp_who' to identify the spid of the process of your connection on the server side
3- set up the trace file for this spid:
set tracefile 'log_file' for spid
(follow doc: http://www.sybase.com/files/White_Papers/ASE15-apptrace-070507-wp.pdf
OR
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00743.1502/html/queryprocessing/BABJDBHJ.htm )
4- analyze your log file
let us know if it helped.
In WebSphere 6.1 I have created a datasource to an Oracle 11g instance using the thin JDBC client.
In Oracle I have two users, one existing and another newly created.
My websphere datasource is OK if I use the component-managed authentication alias of the existing user, but fails with "invalid user/password" message if I use the alias of the new user. The error message is:
The test connection operation failed for data source MyDB (Non-XA) on
server nodeagent at node MY_node with the following exception:
java.sql.SQLException: ORA-01017: invalid username/password;
logon denied DSRA0010E: SQL State = 72000, Error Code = 1,017.
View JVM logs for further details.
There is nothing in the JVM logs. I have grepped all websphere logs and they do not mention my connection at all.
I can confirm that the username and password are correct by logging in via SQLPlus or (to prove the JDBC connection is OK) via SQuirreL.
I have checked in Oracle that the new user has all the system privs that the existing user has.
Any thoughts on what is going on or how I can debug this further?
Just FYI. I am guessing you are running WebSphere in Network Deployment mode.
This behavior you're experiencing is actually by design.
The reason for it is that the "Test Connection" button you see on the admin console, invokes the JDBC connection test from within the process of the Node Agent. There is no way for the J2C Alias information to propagate to the Node Agent without restarting it; some configuration objects take effect in WebSphere as soon as you save the configuration to the master repository, and some only take effect on a restart. J2C aliases take effect on restarts.
In a Network Deployment topology, you may have any number of server instances controlled by the same Node Agent. You may restart your server instances as you'd like, but unless you restart the Node Agent itself, the "test connection" button will never work.
It's a known WebSphere limitation... Which also exists on version 7.0, so don't be surprised when you test it during your next migration. :-)
If this happens to anyone else, I restarted WebSphere and all my problems went away. It's a true hallmark of quality software.
Oftentimes when people tell me they can't log into Oracle 11g with the correct password, I know they've been caught out by passwords becoming case-sensitive between 10g and 11g.
Try this :
data source definition
security
use the j2c alias both autentication managed by component and autentication managed by container
IBM WAS 8.5.5 Knowledge Center - Managing Java 2 Connector Architecture authentication data entries for JAAS
If you create or update a data source that points to a newly created J2C authentication data alias, the test connection fails to connect until you restart the deployment manager.
After you restart the deployment manager, the J2C authentication data is reflected in the runtime configuration. Any changes to the J2C authentication data fields require a deployment manager restart for the changes to take effect.
The node agent must also be restarted.
I have point my data source to componenet-manage authentication as well as container-managed authentication.Its working fine now........
After creating a db using Database Configuration Assistant, I go to Enterprise Manager, log into it, and it tells me, that java.lang.Exception: Exception in sending Request :: null. OracleDBConsole for this db, and iSQLPlus services are started. When I run %ORACLE_HOME%\bin\emctl status dbconsole, it says
EM Daemon is not running.
How do I deal with this? How do I start the EM daemon?
Try this command:
%ORACLE_HOME%\bin\emctl start dbconsole