Background
I am using the Oracle JDeveloper Studio with SOA installed as my IDE. In JDeveloper I want to create a connection to a remote Weblogic server.
The remote server is running on my local machine, and I refer to it as remote to distinguish it from the Integrated Weblogic Server that comes with JDeveloper.
After reading this answer I attempted to add the following lines to the Windows 10 host file:
#
127.0.0.10 localhost2
::1 localhost2
These two pictures show the Application Server setup in JDeveloper: Picture 1, Picture 2
However I still receive the following error:
Server excetion is :
Connection refused from server
When create new server on random port such as 7013 and 7014 for ssl, test connection return:
Testing HTTP Authentication ... failed
Connection refused: connect
Testing JSR-160 Runtime ... failed
Cannot establish connection.
Testing JSR-160 DomainRuntime ... skipped
Testing JSR-88 ... skipped
Testing JSR-88-LOCAL ... skipped
Testing Server MBeans Model ... skipped
Testing App Controller ... skipped
Testing JSR-88-DEP-MGR ... skipped
Testing JSR-88-DEP-MGR-LOCAL ... skipped
Testing JNDI ... skipped
Testing JSR-160 Edit ... skipped
Testing HTTP ... failed
Connection refused: connect
0 of 12 tests successful.
Can anyone suggest some troubleshooting steps here?
Clarification
I need to clarify a few points to guide you to the correct answer.
Are you sure this is a separate Weblogic server running on localhost, not the Integrated Weblogic Server?
Are you sure the Integrated Weblogic server is not running?
Are you sure the Weblogic server you are attempting to connect to is running?
Troubleshooting
General Recommendations
Always run JDeveloper as Administrator
Located an utilize the *-diagnostic.log file and the standard out file
Utilize the JPS utility to see if the WLS process is running
Utilize the EM console to see what interface your server is listening on
Integrated Weblogic or Standalone Weblogic
Firstly, because you are new to Oracle SOA I need you to clarify if you have a Weblogic server installed locally separate from your Oracle BPM Studio ( JDeveloper ) IDE.
When creating a local SOA environment, JDeveloper comes with an Integrated Weblogic Server pre-installed. You don't need to install the Weblogic server separately.
To determine if you have a standalone Weblogic server installed on your local machine you could do a few things.
Do a search for startWebLogic.cmd. If that file is somewhere other than beneath %APPDATA% you likely have a standalone server
Secondly, with 11g ( maybe 12c ) you can check Add or Remove Programs to see if the installation is listed
You could also check to see if it's running by running a jps command in command prompt. This shows all Java processes currently running, and your Weblogic server runs as as a Java process. It will look something like the following
If you see a suspicious process you can run a jinfo <pid> to get more information about the process
You can also check Windows Services to see if you have a Weblogic service.
Most likely you don't even have a local Weblogic installed separate from JDeveloper's Integrated Server. In that case, please read the following section.
Integrated Weblogic Server
As stated before when you download Oracle BPM Studio ( JDeveloper with all the SOA plugins ) it comes with an Integrated server.
You first need to create a default domain and connection to this server.
First, open the Application Server panel.
You should now see the Application Server panel to the left side of your IDE
Remember, generally you are not installing the server here, you are just connecting to a server that is already installed from your IDE. The purpose being that you can deploy composites directly to the server from JDeveloper. Configuring the Integrated Server is a bit different, but the difference doesn't need to be explained here.
Right click on "Application Servers" and click New Application Server. This will display the following popup
Now walk through the steps of creating the default domain and server connection
Then test and finish. You should not have an integrated weblogic server running. To start the server you simply run -> Start Integrated Weblogic Server
If you Windows -> log you can see the server stdout and stderr rolling.
On windows you can also find these logs on Windows 10 by navigating to %APPDATA%\Roaming\JDeveloper\system12.2.1.3.42.170820.0914\DefaultDomain\servers\DefaultServer\logs in your system's file explorer.
Standalone Server
If for whatever reason you aren't using the Integrated Weblogic Server and instead have a standalone installation of Weblogic on your local machine you would first need to find where your Middleware Home directory is.
The environment variable is MW_HOME or ORACLE_HOME
Navigate to that directory and run startWeblogic.cmd. Then tail the out file to see if if it starts successful. From there, the process of creating a connection to the server in JDeveloper is no different than the steps listed above, except that you want to select "standalone" not "integrated".
Final Thoughts
If you want to create the Integrated Server and have already failed several times I would try the following
Stop the Integrated Server (if its running) and delete the default domain
Starting the server again (see above) will recreate the domain.
If that doesn't work delete the entire server connection and recreate. You may also want to delete the DefaultDomain folder in your %APPDATA%\JDeveloper folder
Related
I installed Eclipse and the Jboss Tools plugin with Wildfly.
I can run Wildfly in Eclipse in non-debug mode with no problems. But when I start Wildfly in debug, I can use it for a few minutes, and then it suddenly stops processing, the server ends.
I checked the log and there's nothing. What could be wrong?
Please note the JBoss Tools 4.9.0 is validated against 2018-09 but not against 2018-12.
Do you see something in the server log when the server dies ?
We had this issue and it was because we changed our config to close the management port, which had been used to detect that the server had started. Eclipse could no longer detect that the server had started, so it shut down the process after a set time (450 seconds)
To resolve the issue, we did the following in the Eclipse's Overview panel for our JBoss Server:
Changed the Start Timeout to 30, so it would only fail if it actually couldn't start in 30 seconds rather than waiting for 450
Changed our "Server State Detectors" to detect a Web Port for Startup Poller and Process Terminated for Shutdown Poller.
Changed the Server Ports to match our new configuration
Excerpt from JBoss Community Archive
The tooling was unable to verify your server started. Our tooling has several methods to see if your server is up or not. The two most-often used methods are either "Web Port Poller" or "Management Poller".
You can see which your server is using by opening the server object (In Servers view, double-click your server) and on the right side you'll see a section on polling.
If your server adapter (fancy word for the tooling's representation of your server) is using the Management Port Poller, you should make sure your server is actually exposing the management port. For local servers this shouldn't be an issue, since local servers should automatically expose the management port. You may want to verify in the Ports section (also in the server editor) that the management port is correct. To check if the server is up, we run a management command against the server. If the server responds properly, we declare the server to be started.
If you're using the web port poller, then you may want to verify your web port is correct. To verify the server is up, the Web Port Poller opens a URL connection on {serverHost}:{webPort} and sees if we get a valid connection.
I'm developing a website on a server using NetBean's HTML5, CSS3, JavaScript and PHP support. I am trying to set up the remote connection so I don't have to use something like Filezilla every time to transfer my files to the server. However, NetBeans is unable to connect to my server over SFTP.
I'm unable to share screenshots with the actual information because this is for work and must be kept confidential.
Host Name is in the form: subdomain.domain.com
Username is just the plain username, it's NOT in the form username#subdomain.domain.com.
I am using a password, not a key.
I am behind my work's proxy but I don't think that could be the cause because NetBeans connecting to my server is the only thing that isn't working.
Filezilla works, Putty (SSH) works, Aptana remote connections (SFTP) works, all my browsers work. Even testing the proxy settings in the NetBeans general options works in NetBeans:
Anyway...
After entering in all of the server's information, I click "Test Connection". After 30 seconds (the timeout), this error pops up:
I tried looking in the NetBeans log to gather more information but it doesn't appear to be logging this error. Is there a certain debug flag I need to enable?
Like I said earlier, Filezilla and Aptana Studio can both connect to my server using the same login credentials.
Any suggestions?
Thanks for reading.
It turns out my system proxy settings (which were configured for my work's proxy) were preventing me from connecting to a server on my work's local intranet.
I had to add a proxy exception for the server and everything worked after that.
I am a newbie to working with jboss 7 as- I recently set it up on my server, and am able to start it as well.
However after starting it, when I access
http://IP_ADDRESS:8080
or
http://IP_ADDRESS:9990
Google Chrome gives an error that the page is unavailable.
How can such access be enabled? Also, I am using the startup-shutdown script for /etc/init.d as provided with jboss, do I have to modify the startup and shutdown commands in it, for enabling remote web access to the server interface?
Have you tried http://localhost:8080? If you're using the IP address of your PC it's probably the firewall that is blocking the access to it.
I'm trying to write a Servlet in eclipse configured to use Tomcat 5.5 and I get the following error when I try to run it:
Several ports (8080, 8009) required by Tomcat v5.5 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop the other process or change the port number(s)
As far as I know, Tomcat 5.5 is the one using port 8080, and when I go to http://localhost:8080 I do get the Tomcat success page, so it looks like eclipse tries to run another instance of Tomcat without shutting down the original and fails. How do I solve this?
like it says, something is using the port.
there are two solutions for your problem.
identify (on windows with netstat command) what is using the port (e.g. skype, ...) and stop it
change the port of your tomcat runtime in eclipse -> http://techteam.wordpress.com/2009/02/13/changing-the-tomcat-port-settings-in-eclipse/
hope this helps
I have previously installed WAMP on my windows, and now I am trying to install Zend Server 5 CE 5.3.1 Win x86.
During the installation of Zend Server, there is a step asking about:
web server port : 80
zend server interface port : 10081
I kept to the default. After the installation, I tried to access http://localhost,and is able to see zend test page. But I am unable to access http://localhost:10081/ZendServer, it was stated as page not found.
Is it a conflict of my WAMP and the Zend Server? I remembered stopping the apache for WAMP, before trying to access ZS. Could anyone please advise me how to fix it?
Thank you.
I'm having the same problem. It looked like another application was already using the port 10081.
To find out which application was using the port 10081 I used the following command (in a terminal). This will give you the PID (last column) of the application:
netstat -ano |find /i "established"
Then, I used the Windows Task Manager (Ctrl+Alt+Del). Go to the "Processes" tab. Then View/Columns menu and tick PID. You should be able to locate the application with the PID.
Personally, it was my antivirus, McAfee, who was using that port.
The easiest solution will probably be to cleanly uninstall both WAMP and Zend Server and afterwards just install Zend Server. On the other hand, it could be that another (unrelated) process is already using port 10081, so you might check that as well (using netstat for example) - checking the log files could help in finding this out as well.