We have a server with BI Publisher deployed on it, the server keeps hanging on daily basis at fixed time because of which even the weblogic console is not responding that time. We need to manually kill the weblogic processes and then again start nodemanager and weblogic to access console.
Can anyone help on how can I diagnose the cause for this as I'm not too good with server.
Related
I am running a web application on DigitalOcean VPS(CentOS 7) from almost 7-8 months and has never rebooted the VPS. I haven't seen any problem in the working or web application or database or mail server. Do I really need to reboot it?
you need to reboot your server after kernel upgrades or some security patches but generally you will never need to reboot any linux distribution.
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
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 am Unix java developer trying to help a datastage developer, so out of my aquarium.
The datastage process connects to a database hosting financial transactions on a unix server. there is a datastage process for migrating financial transactions to the ACCOUNTING system. The ETL developers for one reason or another have specified they cannot run one or more specific ETL while in-taking new financial transactions and have specified the process that inserts transactions into the DB be stopped.
me java geek thinks have some process checking a service running at port 55555 would be perfect. But we cannot find a way for datastage to create a socket connection to a port to check. I don't do datastage so I don't know how to work around it's limitations.
The ETL developer thinks a cron script running every minute that inserts an up/down status for the process into a special table would be perfect. I think it is a waste of cpu.
I cannot be the only company that cannot run an ETL when some process is running on a remote system.
How did you solve this issue? Is there a way to connect to a remote servers socket and run the service from datastage???
thanks
after a bunch of discussion.
options we found
Add a step to the start stop server scripts that writes process status to a table. pro: easy to implement. con: not turely accurate (some geek like me is likely to bypass the start/stop script and run only build/run the executable bypassing the start stop script and bypassing the step that inserts the status.) No network and InfoSec paperwork
Cron based script that updates the table with the status on a minute by minute basis. what a pain!!!! No network and InfoSec paperwork.
A script made available to the network through inet or xinet. Problem is datastage ETL developer does not know how to connect to a socket via C or java program. Creates Infosec and network paperwork issues.
New web service (there is a tomcat server serving up a number of web services) Problem is datastage ETL developer does not know how to connect to a socket via C or java program. Creates Infosec and network paperwork issues.
options 3 and 4 are accurate and realtime. options 1 and 2 opens up the possibility of inaccuracies by bypassing process, but that opens up a different can of worms.
We are probably going to implement option 1
I have just created zend project on my local machine. but when I try to run it in the browser, it just loads for at least a minute and then shows this error.
Fatal error: Maximum execution time of 30 seconds exceeded in /opt/lampp/htdocs/launchmind/library/Zend/Db/Adapter/Abstract.php on line 815
It displays the same error with some other line number on some other file every time I reload the page.
Please help. Thank you.
Most likely you have some firewall issue that causes the script to timeout. Check connections from you local machine to all the database hosts in the config and/or webservices and/or other involved servers.
Here are few tips:
Monitor xampp error_log and /var/log/messages...
Since it's local server, disable the firewall temporarily to see if the problem is with your local firewall (preventing outgoing connection) or remote server firewall (preventing incoming connection). On RHEL use sudo service iptables stop or /etc/init.d/iptables stop
if you have very time consuming tasks in your app (very unlikely) then you can try to bump up the max execution time either by modifying /opt/lampp/etc/php.ini (somewhere there) or set max execution time in your app config phpSettings.max_execution_time = 60 or use ini_set in bootstrap
Hope this helps.