I have a WLS 12c (12.2.1.3) Instance, which runs on Java 9. Additional i have also a webstart application (Java 9). Both runs on localhost. I can start the application without problems but when i want to connect as an user, i will become a exception
java.net.ConnectException: t3://127.0.0.1:7001: Bootstrap to: 127.0.0.1/127.0.0.1:7001' over: 't3' got an error or timed out while trying to connect to 127.0.0.1/127.0.0.1:7001
javax.security.auth.login.LoginException: java.net.ConnectException: t3://127.0.0.1:7001: Bootstrap to: 127.0.0.1/127.0.0.1:7001' over: 't3' got an error or timed out while trying to connect to 127.0.0.1/127.0.0.1:7001
I listen to adress 127.0.0.1 with default port 7001 in my weblogic Instance. How can i solve the problem?
In the admin console, please check the listen address. If the listen address is set to say hostname, you will need to connect to hostname instead of 127.0.0.1.
#Emmanuel is right, it appears that 12.2.1.3 does not support Java 9. Although I doubt this issue is directly related to Java 9.
Related
I've setup a weblogic cluster with 2 managed servers.In order to configure node manager on both nodes i've followed the related article :
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/wls/12c/12_2_1/01-12-001-ConfiguringandUsingNodeManager/Configuring_and_Using_NM.html
with the following configuration :
Machine-0 :
DomainsFile=/u01/app/oracle/config/domains/base_domain/Machine-
0/nodemanager.domains
LogLimit=0
PropertiesVersion=12.1.3
AuthenticationEnabled=true
NodeManagerHome=/u01/app/oracle/config/domains/base_domain/Machine-0
JavaHome=/opt/jdk1.8.0_131
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5558
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=true
LogFile=/u01/app/oracle/config/domains/base_domain/Machine-
0/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
Machine-1 (the second managed server) has the same configuration with the exceptions of ports (5557) and name.
Although node manager is successfully started on both machines (startNodeManager.sh on machine-0 and machine-1) from admin console on Machine-0 the following error occurs and node manager doesnt start :
weblogic.nodemanager.NMConnectException
nodemanager.log of Machine-0 has no indications of errors or any helpful stuff.
Any help would be appreciated.
thanks in advance
These are the things that I usually check when I am setting up a new WebLogic domain:
It is possible that the Listen Address of Machine-1 is not correct. Check the Listen Address of the machine from the WebLogic Domain Configuration. It should match the host's machine name. Using localhost might not work because the Admin Server is trying to connect to the Machine-1, which can be on the other server.
Make sure to check if the port is reachable from the Admin Server's machine.
Check that the Node Manager configuration uses Plain instead of SSL connection, as stated in your nodemanager.properties file. Under Environments > Machines, click the machine and go to Configuration Tab, Node Manager. Check if the Type is Plain and not SSL. Changing this will require a restart of the Admin Server.
Please verify the items below before you start nodemanager.
Check if the nodemanager.domains has your domain name listed.
Try to see if the ports are listening using the commands below.
netstat -an|grep 5557
netstat -an|grep 5558
Also, check if the nodemanager is reachable in weblogic console.
Connecting to Cassandra with non-SSL port works.
But when I try to make a SSL connection by initializing SSLContext, I get this strange exception.
I am using Datastax driver cassandra-driver-core-2.0.0-rc3.jar
Caused by: org.jboss.netty.channel.ChannelPipelineException: Failed to initialize a pipeline.
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:208) [netty-3.9.0.Final.jar:]
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:182) [netty-3.9.0.Final.jar:]
at com.datastax.driver.core.Connection.(Connection.java:92) [cassandra-driver-core-2.0.0-rc3.jar:]
at com.datastax.driver.core.Connection$Factory.open(Connection.java:421) [cassandra-driver-core-2.0.0-rc3.jar:]
at com.datastax.driver.core.ControlConnection.tryConnect(ControlConnection.java:215) [cassandra-driver-core-2.0.0-rc3.jar:]
at com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:170) [cassandra-driver-core-2.0.0-rc3.jar:]
You need to install the Java Unlimited Strength JCE; this has to be done on your client machine in your JRE installation.
Here is one reference in the context of the Cassandra server, but Java clients using SSL need this as well.
http://www.pathin.org/tutorials/java-cassandra-cannot-support-tls_rsa_with_aes_256_cbc_sha-with-currently-installed-providers/
I am using redis server.
I have installed it on a PC having IP address 192.168.10.38. When I connect using the same PC redis servre is working fine.
Now my actual problem is I want to connect with same server using another PC.
Note that redis server is not installed to this PC.
When I use the same application on this another PC, I am getting exception below.
Caused by: redis.clients.jedis.exceptions.JedisConnectionException: java.net.ConnectException: Connection refused
at redis.clients.jedis.Connection.connect(Connection.java:142) ~[jedis-2.4.2.jar:?]
at redis.clients.jedis.BinaryClient.connect(BinaryClient.java:75) ~[jedis-2.4.2.jar:?]
at redis.clients.jedis.BinaryJedis.connect(BinaryJedis.java:1724) ~[jedis-2.4.2.jar:?]
at redis.clients.jedis.JedisFactory.makeObject(JedisFactory.java:65) ~[jedis-2.4.2.jar:?]
at org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:819) ~[commons-pool2-2.0.jar:2.0]
at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:429) ~[commons-pool2-2.0.jar:2.0]
at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:360) ~[commons-pool2-2.0.jar:2.0]
at redis.clients.util.Pool.getResource(Pool.java:40) ~[jedis-2.4.2.jar:?]
Kindly help me with this and let me know can I use remote redis server without installing it to my development PC ?
Redis server is by default binded to 127.0.0.1
I changed it to 0.0.0.0 and finally it uses 0.0.0.0:6379 to listen redis server services.
And it worked for me.
I want to create localhost connection in Oracle SQL Developer tool
my credentials are
username : SYSTEM
password : SYSTEM
Hostname :localhost or 127.0.0.1
port : 1521
sid : xe
When i connect i gives error The Network Adapter could not establish connection
The Network Adapter could not establish connection is caused because:
The database host name or port number is wrong.
The listener process (service) is not running. You can re-start it with the "lsnrctl start" command or on Windows by starting the listener service.
you have either the wrong SQL Developer URL or you have a basic SQL*Net connectivity issue! This error is most likely caused by one of these factors:
You are using the wrong URL
The wrong port number or IP address (or DNS host name) was used
The listener is not configured properly
The listener process (service) is not running. You can re-start it with the "lsnrctl start" command or on Windows by starting the listener service.
For a step by step checklist, see the notes on troubleshooting an Oracle connection problem.
Does anyone know why I am unable to connect to my server using the Notepad++ NppFTP plugin with SFTP?
I have a CentOS 6.4 server with SSH on port 22.
When I try and connect using NppFTP I get the following output:
[NppFTP] Everything initialized
Connecting
[SFTP] Connection failed : Error reading socket
Unable to connect
Disconnected
This used to work when I had my SSH port set to 3264 but when I changed the SSH port back to 22 NppFTP stopped working. All the settings for the profile are correct including the right IP, username, password and port (22).
I can connect with SFTP using FileZilla and WinSCP successfully with these same SFTP details and I can connect with SSH using PuTTY.
I can connect with SFTP to other servers using NppFTP so I believe there is an issue in my server config I'm just not sure where or what.
I looked at the access logs but found no attempt at a connection from NppFTP, I turned the firewall off and still nothing.
In the end I got in touch with my server company and it turns out it was a problem on their end. This is what they had to say:
"This was caused by an IPS rule inspecting the network packets coming into the infrastructure, which helps identify brute force attacks."
Very strange, but after they made the change NppFTP can now connect successfully.