I have the Oracle Weblogic 12.1.3 and the installation went well and the server was starting successfully. But now It fails to start for some unknown reason. It had problems with the base domain that I created in the setup. So now I'm trying to set up a new domain. But the problem is that the configuration wizard fails to start. I've tried running it with Run as Administrator but the cmd just pops up and disappears. I tried to reinstall the Weblogic server from start and even that didn't solve the problem. The part where the configuration wizard starts I got the same issue. I've also tried running it from command prompt itself but the same thing happens. I have also tried this:
config.cmd -mode=console
and in the cmd it says
Files/Microsoft went wrong this time
and also running it in "text" mode like this
config.sh -mode=console
but it fails to start. and shows the following:
What could be the problem and the fix for this? I'm running Windows 7
There was some discrepancy in the path variable of the environmental variables. Re-arranged the path values and inserted/removed quotes from some values and added that path value containing Files/Microsoft int the end(which was added by Microsoft VS Code). This solved the problem.
Related
I cannot get Apache Tomcat to start. I followed the instructions for installing Tomcat on the Mac found at https://www.dev2qa.com/how-to-install-tomcat-in-macos/.
After I type the command to start Tomcat, the response from the command line is that Tomcat has started.
However, when I go to the browser, the default page is not showing up. I further checked to see if the port was being used by using the command
lsof -nP -i4TCP:8080 | grep LISTEN
which showed that no program is using the port. I also read the 'RUNNING.txt' that instructed me on setting the environmental variables, which I did. Any suggestions on why Tomcat is not starting up.
I'm using jdk 1.8.0_202 and Apache Tomcat 9.0.14 that is running of Mac OS High Sierra.
BatChmod
After downloading a fresh version of Tomcat, I use the BatChmod app to alter the file permissions. Tomcat will not launch properly without altering the permissions.
I do not know the command-line equivalent, but here is a screenshot of the settings I have used for years successfully.
Plea for help
If anyone can write the equivalent as a shell script for macOS, please post!
Even better, explain how to wrap such a script as an AppleScript for drag-and-drop execution in Finder.
The problem turned out to be a permissions problem. When I installed Tomcat, I put the folder in the '/Library/Tomcat' directory. Even though the Tomcat files were changed to be executable, the user and group ownership remained the same. To get Tomcat to run, I moved the directory to 'Users/MyUserName/Tomcat'. Once I did that, the default Tomcat page ran.
I haven't been able to find a specific answer to what could be causing this issue though I am hoping it is something quite simple.
Issue.
I have installed version 10.0.0.Final from the Wildfly website and extracted into C:\Program Files\wildfly-10.0.0.Final.
I then navigate to C:\Program Files\wildfly-10.0.0.Final\bin directory via windows command prompt and execute the standalone.bat command.
Wildfly doesn't start and I get the following exception:
java.lang.IllegalArgumentException: Failed to instantiate class "org.jboss.logmanager.handlers.PeriodicRotatingFileHandler" for handler "FILE"
If anyone has encountered this error message before, then your guidance would be greatly appreciated.
Thanks!
Ben
The error appears to be a result of either file permissions on the JBoss home directory, lack of space available, or a missing directory.
Relevant posts include:
Starting WildFly 8.2 under a user with limited permissions
Which suggests setting the JBOSS_BASE_DIR property to the root folder of the JBoss installation.
https://github.com/jboss-dockerfiles/wildfly/issues/24
Suggests this can occur if the root folder does not have enough space allocated for the user (typically running in Unix environments).
Error in starting Wildfly 8.0 server with JDK 1.8
The logs/boot.log didn't exist. The author manually created the file which then revealed a permission issue on the log file (more likely on the entire Jboss installation folder).
The issue was caused due to the command prompt. As I am using windows 10, I needed to be using Command Prompt (Admin),rather than just the normal cmd hence the permission issues alluded to previously by pczeus.
After using Command Prompt (Admin), I was able to start the server.
When a try to start glassfish from within Eclipse the following error occurs:
Unable to start server on time. java.util.concurrent.TimeoutException
And when a try to start via asadmin start-domain or asadmin start-domain domain1 it remains loading and never stops.
Anyone can help me?
Perform the following two steps:
Go to the folder where you store the Glasfish.
Example: My folder is C:\Program Files (x86)\glassfish-4.0\glassfish\bin.
Double click on startserv.bat and wait a few seconds and it will work.
I had the same problem and I solved it like the following :
try to update the GlassFish tools from the Eclipse MarketPlace, and
get the latest update , and check eclipse for any updates .
restart Eclipse , "I don't know why , but it works " .
I was facing the same issue with my Glassfish 4.0 server, I did googled but didn't worked out for me.
You can manually deploy your web application by exporting your project as .war file and then using Glassfish GUI (http://localhost:4848) deploy your application and then access it.
Open the GlassFish Server configuration by double clicking on your server instance in your server windows. You shall find a Timeout section. Expand it and increase the time limit to complete server operations in the Start section. This should work.
I followed the instructions on the Datomic site: http://docs.datomic.com/getting-started.html, but I'm getting this error when trying to start up the datomic shell prompt. I'm using a windows machine. Any suggestions? I tried the same thing on my linux box and did not get this error.
Edit: moved to a different windows machine and it's working. If I have time to troubleshoot this problem and I find a solution I'll report back
I noticed that you cannot run the shell.cmd from within the bin directory, you need to call it with bin\shell.cmd from the parent directory... hope that helps.
In case you are using cygwin/bash and call bin/shell :
The java runtime on windows does not understand classpath with a ":"
but this is what you get from bin/classpath.
Either correct this or use DOS-CMD shell and call bin/shell.cmd inside.
Regards
Some tips for running datomic on Windows (7 at least):
Do not download datomic into Program Files. On startup, it creates logging directories and temp files into its own directories, so unless you run the command prompt as Administrator, you're gonna have screens full of Unable to write to file... errors.
You need to run datomic as such (assuming you extracted the download to C:)
c:\datomic-free-0.x.xxxx>bin\shell.cmd
Note the backslash. Tripped me up forever coming from *nix world.
After that, return to your regularly scheduled datomic tutorials.
I am a noob. I just downloaded the liferay with jboss 7.0.2. I had it installed on mt laptop by watching the youtube. I got it started by just using command line console. I successfully got it setup and running on the localhost. I turned off the command line console after I got it done.
Then I tried to open it one the browser by the localhost and it is not working now. Now I cant go back to the platform.
I tried to go under the cmd again and enter
{the folder}\jboss-7.0.2\bin\standalone.bat
It shows me that it was calling another file called "standalone.conf.bat"
Now my environmental variables are
JAVA_HOME C:\Program Files\Java\jdk1.7.0_04\bin
JAVA C:\Program Files\Java\jdk1.7.0_04\bin
I need to start the thing start.. please help me
If you working with Tomcat (as per your last comment), then you should go to bin/startup.bat file (windows) or startup.sh (linux).
Now :
1) If your console does not start, that means, either some problem with tomcat configuration (CATALINA_HOME variable) or java configuration (JAVA_HOME)
2) If it starts, but hangs when configuration of data (default sql scripts), then there is a problem with database configuration that you did in portal.properties file, or default HS SQL DB.
3) If it hangs somewhere else, there must be some issue with the default port of the server.
Hope this helps.