I am trying to set up workspace using Websphere 7.0 application server on RAD IDE. I am using Java 1.6
When ever i try to start my server it throws following error:
Exception in thread "main" java.lang.NoClassDefFoundError: Files
Caused by: java.lang.ClassNotFoundException: Files
at java.net.URLClassLoader.findClass(URLClassLoader.java:434)
at java.lang.ClassLoader.loadClass(ClassLoader.java:660)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:358)
at java.lang.ClassLoader.loadClass(ClassLoader.java:626)
Could not find the main class: Files. Program will exit.
What would be reason for this? Did anyone get this kind of error before.
Note: I tried googling out and people suggest try changing classpath, which i tried and didn't work.
It looks like something, somewhere is failing to quote an argument containing C:\Program Files, probably due to custom JVM configuration. If you use the -script option to bin\startServer.bat, you might be able to determine where things are going wrong. This might be a product issue, so if you can't figure it out (or you don't think your configuration is to blame), then you might consider opening a PMR with IBM.
If you are facing this issue when trying to start the server from RAD console , this might be a product issue , a quick way to solve this might be to start the server using command line see below example on how to start the server
C:\WorkFolder\WASV8.5_Install\profiles\AppSrv03\bin>startServer.bat server1 -profileName AppSrv02
Try to start in an command prompt you would see the servers starting in your RAD console as well.
C:\WorkFolder\WASV8.5_Install\profiles\AppSrv02\logs\server1\startServer.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 20484
Related
I host Spring Boot web applications as Azure App Services, however one of the seems to be stuck in a loop on startup. The application is not accessible and it looks like it restarts every half a minute. There are no errors in the logs and restarting the App Service didn't help either.
Does someone have an idea why it is happening or how I could fix it?
Thanks in advance.
Sometimes the jar will take more time to start with the default startup command. It could be because it scannes the file system for configuration files since it uses -cp command to start the jar.
java -cp app.jar org.springframework.boot.loader.JarLauncher
I fixed this issue by providing a startup command in the AppService->Configuration->General Settings->Startup command
java -jar <path_of_jar>
Altenatevely you can check the container logs also Please refer the link below.
[https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-diagnostic-logs]
If you are logging into a file, then you can SSH[Azure portal->AppService-> left side there is an SSH option ] to the container and tail the logs directly, but sometimes it is very hard to get into a container using ssh since it is not starting properly.
Your application.properties should have:
logging.level=DEBUG
logging.level.org.springframework=DEBUG
logging.file=/home/LogFiles/boot.log
boot.log should give you more on what to hunt down next.
I finally managed to fix the problem. On default the App Service configuration was set up to use Jetty as web container instead of Tomcat. Probably the service tried to validate that the Jetty is up and running and since it wasn't the service kept restarting.
Once I set the configuration to Tomcat the issue was solved.
I have installed the ccnet 1.6.798 on Windows 7 Ent.
After fews time is run correctly, now its just load some line and then go to hang .
Nothing happen anymore,
Can somebody help me to solve this matter,
I have this problem on windows server 2k8 too.
[CCnet Server:INFO] Starting Cruisecontrol.Net Server
[CCnet Server:INFO] Initialising security
Here is screenshot:
http://postimg.org/image/irgl0kbpd/
It does not hang. As you can see in the debug log you have not configured any projects. So there is nothing todo for CCNet.
Please read the documentation about how to add projects to your configuration.
Also the Scenarios are a very helpful source to get startet.
I am trying to create an instance using the Configuration Manager of WCS 7. I am working on a Win 7 x64 machine with DB2 9.5 64 bit version.
I am struck with this Massloading error when the instance creation happens :
In createInstanceANT.log file :
[Massload] Massloading
C:\IBM\WebSphere\CommerceServer\schema\xml\wcs.keys.xml Error in
MassLoading, please check logs for details.
The error log shows the following error :
[jcc][10165][10044][4.3.111] Invalid database URL syntax:
jdbc:db2://:0/WCSDEMO. ERRORCODE=-4461, SQLSTATE=42815
C:\IBM\WEBSPH~1\COMMER~2\config\DEPLOY~1\xml\createBaseSchema.xml:185:
Error in massloading
WCSDEMO is the database name. The Massloader is not able to get the URL and port to connect. It is supposedly getting them from createInstance.properties file but it is not working. The createInstance.properties file has all the details of the DB to connect.
What could be the reason for this error and how to resolve it ? Is there any configuration change that I am missing ?
Can you provide some more details.
look inside the messages.txt file located in WC_install_dir/instances/instance_name/logs
and confirm what the exact issue is. If it is related to jdbc driver being wrong I may be able to help you.
I've been running into massloading problems with external systems. Eg. databases not on the same machine as the WAS installation.
In these cases I look for the
As you can see setting the loaderDBName to just the name of the database would look on the local machine. But by changing this statement so you load with the syntax
loaderDBName=[DATABASE_SERVER_NAME]:[PORT]/[DATABASE_NAME]
You'll be able to massload using the commerce standard scripts. These changes needs to be done in many scripts. Both for updating fixpacks and enabling features. If you run database updates without the changes it will crash at first and have done all the schema changes to the database that you then need to comment out before trying again.
IBM Software Support is your friend. They'll help you fix it.
I am facing a problem while starting the websphere message engine for one of the application deployed on websphere. This application is getting deployed automatically as a part of the installation of Websphere Lombardi 7.2 express edition. It's using websphere 7 internally to deploy it. When I try to start the message engine from the administrative console of websphere I am getting following error:
The messaging engine ProcessCenter01.twperfsvr-twperfsvr_bus cannot be started as there is no runtime initialized for it yet, retry the operation once it has initialized. For the runtime to successfully initialize the hosting server must be started, have its 'SIB service' already enabled, and dynamic configuration reload enabled. If this is a newly configured messaging engine and it is the first messaging engine to be hosted on this server, then it is most likely the 'SIB service' was not previously enabled and thus the server will need to be restarted. The messaging engine runtime might not be initializing because of an error while trying to start, examine the SystemOut.log of the hosting server to check for error messages indicating the problem.
After restarting the server, the same error shows. Can anyone help me to to find what gets loaded as a part of "initialization of runtime"? Are there any config files etc. that I need to check to solve this issue? I am suspecting some missing configuration causing error to load the runtime for this particular application.
I too faced this issue today had to delete all the files under the message store
check the directory-file path mentioned in
Application servers > server1 > Messaging engines > XXX.server1-primaryBus > File store
Just Enable the SIB Services For the particular Server.
Example:Server-->Application Server-->click on Server Name-->right hand side we can see SIB services-->Check box the Enable services.
This will solve your problem
Recently I have faced the same issue when I rebuilt the jvms in UAT envt. After searching on web I found that because of the old messages saved in the message store(flat files in my envt) the messaging engines was not getting initiated. After deleting the old messaging store and restarting the servers it got initialized.
I have struggled with this problem too.
In our situation the problem was that the file message store location was used that was already created for a different (or old) message-engine.
If you add a busmember to the service-bus and use a file store implementation, then you need to supply the path for the store and log folder. Make sure these locations don't exist yet, other wise you will run in the problem above. The message-engine for this member will use these folders.
If you have a script for creating the message-bus infrastructure, make sure that when you delete the bus or remove message-engines, that you remove the file store/log folders for these, before you re-run your script.
Another possibility is that you are using a external database as a data store, and the user that is used for the connection is not allowed to create a database. You might find a ffdc entry like this:
DB2 SQL Error: SQLCODE=-552, SQLSTATE=42502, SQLERRMC=DB2ADMIN;CREATE
SCHEMA, DRIVER=3.61.65
Then you have to go to your database administration tool and give DB2ADMIN the proper privileges. Then restart the server or cluster.
Finally this issue is been resolved. I did not create the schema in SQL Server with same name as that of the username I gave to connect SQL Server during the installation of WLE 7.2
Please find details about this at below link:
http://www.ibm.com/developerworks/forums/message.jspa?messageID=14795282
I really hope someone who is a CC.NET expert can help with this, because this problem is painful!
I have a remote build machine with CruiseControl.NET and CCTray running (version 1.5.7256.1)
On the local machine I have CCtray connecting through HTTP not .NET remoting.
When I configure the projects, I add a server through HTTP and use the following URL:
http://localhost/ccnet
If I leave [Set to pre-1.5.0 server] UNCHECKED, then it fails to connect with this error:
Failed to connect to server: The remote server returned an error: (500) Internal Server Error.
If I set to [Set to pre-1.5.0. server] CHECKED, then it succeeds and I can kick builds off from CCtray on the local machine fine.
Now, if I go back to another machine which I want to connect remotely, I follow same steps. Again, only pre-1.5.0 setting works. WHY?! CruiseControl.NET and CCTray are at 1.5.7256.1?!?
The 2nd problem and main problem which I think may be related to the previous; if I then use the pre-1.5.0 setting the pojects show up but when I force a build I now get this error:
An unexpected error has occurred while trying to force a build.
The method or operation is not implemented.
What am I doing wrong, I'm really struggling with this. I previously was using 1.4 versions and this worked fine, so has something broken? I'm using IIS7 too so don't know if this could be something to do with it.
I had a look at the tray app's source code for the 1.5 release (as well as the current trunk.) When connected to a pre-1.5 server, regardless of whether you specified the connection as remoting or HTTP, you will receive the unimplemented exception message when attempting to force build a project.
Looks like your options at the moment are to wait for a new release or pull down the code and modify (and I have no idea how easy backwards compatibility was maintained between versions...)
It sounds like you may have configuration options that are part of a breaking change perhaps? can you post more of your configuration so we can check it?
Also after you save changes have you looked at the server log? it often has information about what broke. Especially the part that happens right after you change a config file and save.
I'd be interested in seeing log file information. Also, why are you using http rather than remoting? Perhaps show us some of your settings in ccnet.exe.config? here's my remoting setup which I believe is the default:
<system.runtime.remoting>
<application>
<channels>
<channel ref="tcp" port="21234">
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full"/>
</serverProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
also you may want to check security issues and firewall settings on that server. (windows event log for security audit failures, etc...)