Startup liferay tomcat 6.1.1 ga2 sever with sqlserver database - sql-server

I'm trying now to startup a liferay 6.1.1 ga2 server with sqlserver database.
I created user and database with windows commande line "sqlcmd -S localhost" as the following:
1> create database liferayportal;
2> create login lrUser with password='abc123';
3> create user lrUser for login lrUser;
4> exec sp_addrolemember 'liferayportal' , 'lrUser';
the portal-ext.properties:
jdbc.default.driverClassName=net.sourceforge.jtds.jdbc.Driver
jdbc.default.url=jdbc:jtds:sqlserver://localhost/liferayportal
jdbc.default.username=lrUser
jdbc.default.password=abc123
And this is a summary of the stacktrace
09:28:36,657 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1][BasicResourcePool:1841] com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask#6245a4 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (3). Last acquisition attempt exception:
java.sql.SQLException: Network error IOException: Connection refused: connect
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:410)
.
.
.
09:28:36,702 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0][BasicResourcePool:1841] com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask#c8aeb3 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (3). Last acquisition attempt exception:
java.sql.SQLException: Network error IOException: Connection refused: connect
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:410)
.
.09:28:36,717 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#7][BasicResourcePool:1841] com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask#fab5b1 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (3). Last acquisition attempt exception:
java.sql.SQLException: Network error IOException: Connection refused: connect
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:410)
.
.
.
09:28:36,743 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#4][BasicResourcePool:1841] com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask#12524b0 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (3). Last acquisition attempt exception:
java.sql.SQLException: Network error IOException: Connection refused: connect
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:410)
.
.
.

I would check whether the server has the port related to MSSQL open for remote access (normally the port is 1433) if not, you should set MSSQL to work on that port, and allow remote access and verify that your firewall allows the access to that port.

Related

RedHat DBT | Error Database "Connection reset by peer"

[ubldev#UBL-DEV ~]$ ./DBT
Exception in thread "main" com.temenos.tafj.common.exception.DatabaseRuntimeException: TAFJERR-1020: Error database connection Details : TAFJERR-1020: Error database connection Details : IO Error: Connection reset by peer, Authentication lapse 316987 ms.
at com.temenos.tafj.dataaccess.DataAccessExecutor.doConnection(DataAccessExecutor.java:1825)
at com.temenos.tafj.dataaccess.DataAccessExecutor.doConnection(DataAccessExecutor.java:1667)
at com.temenos.tafj.dataaccess.DataAccessExecutor.getConnection(DataAccessExecutor.java:1639)
at com.temenos.tafj.dataaccess.DataAccessExecutor.getConnection(DataAccessExecutor.java:1630)
at com.temenos.tafj.dataaccess.JDBCDataAccessConductor.getConnection(JDBCDataAccessConductor.java:5301)
at com.temenos.tafj.tools.integration.DBToolsConsole.getConnection(DBToolsConsole.java:1330)
at com.temenos.tafj.tools.integration.DBToolsConsole.init(DBToolsConsole.java:250)
at com.temenos.tafj.tools.integration.AbstractConsole.doIt(AbstractConsole.java:236)
at com.temenos.tafj.tools.integration.DBToolsConsole.main(DBToolsConsole.java:208)
I am trying to access my DB in Redhat and but unable to connect it, following error i found. Pelase provide me a way forward

SSAS error process : A request for a connection ... pool could not be granted

I got this error when I try to process (Full) my cube :
The JSON DDL request failed with the following error: Failed to execute XMLA. Error returned: 'OLE DB or ODBC error: A request for a connection from the data source pool could not be granted. Retrying the evaluation may solve the issue..
'..
Do you have any idea ?
Thank's.
Please check the setting on your data sources.
If the maximum number of connections is too low, you might see this error.
When you do the process data, the data model initials several connections to your data sources. If the number of connections exceeds the allowed maximum number, error happens.
Maximum Number of Connections

Running Flink build-in program sometimes arise Exception:java.io.IOException: Connecting the channel failed

I have set up a flink standalone cluster, with one master and three slaves , all SESU Linux machines. In the master Dashboard http://flink-master:8081/ I can see 3 Task Managers and 3 task slots as I have set taskmanager.numberOfTaskSlots: 1 in flink-conf.yaml in all of the slaves.
When I run a flink built-in program,like the examples/streaming/Iteration.jar,I get exception often:
java.io.IOException: Connecting the channel failed: Connecting to remote task manager + 'ccr202/127.0.0.2:49651' has failed. This might indicate that the remote task manager has been lost.
at org.apache.flink.runtime.io.network.netty.PartitionRequestClientFactory$ConnectingChannel.waitForChannel(PartitionRequestClientFactory.java:197)
at org.apache.flink.runtime.io.network.netty.PartitionRequestClientFactory$ConnectingChannel.access$000(PartitionRequestClientFactory.java:132)
at org.apache.flink.runtime.io.network.netty.PartitionRequestClientFactory.createPartitionRequestClient(PartitionRequestClientFactory.java:84)
at org.apache.flink.runtime.io.network.netty.NettyConnectionManager.createPartitionRequestClient(NettyConnectionManager.java:59)
at org.apache.flink.runtime.io.network.partition.consumer.RemoteInputChannel.requestSubpartition(RemoteInputChannel.java:156)
at org.apache.flink.runtime.io.network.partition.consumer.SingleInputGate.requestPartitions(SingleInputGate.java:480)
at org.apache.flink.runtime.io.network.partition.consumer.SingleInputGate.getNextBufferOrEvent(SingleInputGate.java:502)
at org.apache.flink.streaming.runtime.io.BarrierTracker.getNextNonBlocked(BarrierTracker.java:93)
at org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInputProcessor.java:214)
at org.apache.flink.streaming.runtime.tasks.OneInputStreamTask.run(OneInputStreamTask.java:69)
at org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:264)
at org.apache.flink.runtime.taskmanager.Task.run(Task.java:718)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.flink.runtime.io.network.netty.exception.RemoteTransportException: Connecting to remote task manager + 'ccr202/127.0.0.2:49651' has failed. This might indicate that the remote task manager has been lost.
at org.apache.flink.runtime.io.network.netty.PartitionRequestClientFactory$ConnectingChannel.operationComplete(PartitionRequestClientFactory.java:220)
at org.apache.flink.runtime.io.network.netty.PartitionRequestClientFactory$ConnectingChannel.operationComplete(PartitionRequestClientFactory.java:132)
at org.apache.flink.shaded.netty4.io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:680)
at org.apache.flink.shaded.netty4.io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:603)
at org.apache.flink.shaded.netty4.io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:563)
at org.apache.flink.shaded.netty4.io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:424)
at org.apache.flink.shaded.netty4.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise(AbstractNioChannel.java:268)
at org.apache.flink.shaded.netty4.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:284)
at org.apache.flink.shaded.netty4.io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528)
at org.apache.flink.shaded.netty4.io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
at org.apache.flink.shaded.netty4.io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
at org.apache.flink.shaded.netty4.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
at org.apache.flink.shaded.netty4.io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
... 1 more
Caused by: java.net.ConnectException: Connection refused: ccr202/127.0.0.2:49651
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at org.apache.flink.shaded.netty4.io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:224)
at org.apache.flink.shaded.netty4.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:281)
... 6 more
It seems that the network causes the problem,but sometimes the flink program can successfully finish.So what is the reason?
I also encounter this issue very frequently especially when there are many taskManagers. There are a few config I have tried to solve this issue. It's happened when the taskManager read the remote partition through netty connection. It timed out when request the connection. I increased the config "taskmanager.network.netty.server.numThreads", it solved the issue.

Known Good SQL Logins Failing (Error 18456) Accompanied by "Unable to Reuse a Session" (Error 18056)

I am losing my patience with this problem. I'm running SQL Server 2008 R2 with all updates.
It is very intermittent. Every now and again this SQL server instance will report the error: Login failed for user 'XX'. Reason: Failed to open the database configured in the login object while revalidating the login on the connection.
Error: 18456, Severity: 14, State: 46.
I know this is a good login, it works all of the other times, and no one changes the credentials.
The above error is immediately followed by this error:
The client was unable to reuse a session with SPID 150, which had been
reset for connection pooling. The failure ID is 46. This error may
have been caused by an earlier operation failing. Check the error logs
for failed operations immediately before this error message.
Error: 18456, Severity: 14, State: 46.
When this occurs a few minutes later this is reported also:
Message
All schedulers on Node 0 appear deadlocked due to a large number of worker threads waiting on ASYNC_NETWORK_IO. Process Utilization 0%.
The above message just keeps repeating until I restart the server.
From researching this issue I've increased the maximum worker threads (currently at 1100). The server has 72G memory and 4 vCPUs, running Windows Server 2008 R2.
i don't encounter this issue at all on my other database servers that run the same environment. Just this one. Any help would be greatly appreciated, I'm running out of options.

JMSWMQ0018: Failed to connect to queue manager with 2059

JMSWMQ0018: Failed to connect to queue manager 'RBA.QM.GZ' with connection mode 'Client'
and host name 'rba007.in.ibm.com(1416)'. Check the queue manager is started and if running in client mode,
check there is a listener running. Please see the linked exception for more information.
JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2059'
('MQRC_Q_MGR_NOT_AVAILABLE').
am getting this two errors can any one tell.

Resources