I installed Jboss server in windows xp . When I try to execute "run.bat" I got an error as
" To start JBoss Application Server please see C:\Program Files\jboss-as-7.1.1.Fin al\bin..\README.txt"
Before executing "run.bat" I set the environment variable
JBOSS_HOME = C:\Program Files\jboss-as-7.1.1.Final;
After getting an error I saw that "readme.txt", it says that "This jar should be used
with standalone clients only, not with deployments are that deployed to an AS7 instance."
What is the problem? What should I do?
Don't use run.bat. Use either %JBOSS_HOME%\bin\standanlone.bat or %JBOSS_HOME%\bin\domain.bat. I would start with standalone as that's probably the one you want. Domain is for running multiple instances and wanting one management interface to interact with each server.
Related
Am using Windows Server machine 2012 R2 machine to take a setup (exe) and using Wix v3.10.
When i run the burn executable taken from Windows Server 2012 R2 machine in any machine, setup crashed with the error as "System.IO.DirectoryNotFound" not found.
On further investigating this, this exception was occurred during the retrieval of burn and bootstrapper related files(.ba folders from temp location) using WixBundleProviderkey. Because, the .ba folder was existing in some other (some Guild(folder name)} name instead of the required directory in temp location. This issue is occurred only when the setup taken from Windows Server 2012 R2 machine and this is not occurred in some other windows machine if we took setup from it.
Actual path in which .ba folders exists: C:\Users\server\AppData\Local\Temp\2{32DB2298-79D9-4816-9BD6-ABA4271CCA2F}
Application Searching path of .ba folder : C:\Users\server\AppData\Local\Temp\2{36823a7e-b6d2-4db1-b0d1-212cdf7bd669}\
Could anyone please let us know why this issue occurring in Windows server machine?
What is the main function of WixBundleProviderkey?
Below is my code where am facing issue while launching the setup
string baFolder = System.IO.Path.GetTempPath() + SyncBA.Model.Bootstrapper.Engine.StringVariables["WixBundleProviderKey"] + "\";
This is due to the security mitigations added in v3.10.3. That temp folder is no longer created using the bundle's id, it's a random guid. You should get the location of your BA in a different way, such as AppDomain.CurrentDomain.BaseDirectory.
i know this can be very simple but i am not able to do so.
I am trying to start integrated weblogic server in jdeveloper(v11.1.1.7.0). But it always says the following error :
*** Using port 7101 ***
C:\Users\595452\AppData\Roaming\JDeveloper\system11.1.1.7.40.64.93\DefaultDomain\bin\startWebLogic.cmd
[waiting for the server to complete its initialization...]
The system cannot find the path specified.
The JRE was not found in directory C:\Oracle\MIDDLE~1\jdk160_29. (JAVA_HOME)
Please edit your environment and set the JAVA_HOME
variable to point to the root directory of your Java installation.
Press any key to continue . . . [Server Instance IntegratedWebLogicServer is shutting down. All applications currently running will be terminated and undeployed.]
My Java_home is set to the jdk i have installed and also have an entry in PATH of system variable.
**User variable:**
C:\Program Files\Java\jdk1.7.0_45;C:\Program Files\Java\jre7
**System Variable :**
C:\Program Files\Java\jdk1.7.0_45\bin;C:\Program Files\Java\jre7\bin
Please assist me in this regard.
I fixed mine by editing the setDomainEnv.cmd in my weblogic installation.
In my installation D:\srv\wls12120\user_projects\domains\mydomain\bin my installation pointed to:
set SUN_JAVA_HOME=D:\Java\jdk\jdk8u40 changed to
set DEFAULT_SUN_JAVA_HOME=C:\PROGRA~1\Java\JDK17~1.0_2
set DEFAULT_SUN_JAVA_HOME=D:\Java\jdk\jdk8u40 changed to
set JAVA_HOME=C:\PROGRA~1\Java\JDK17~1.0_2
as well as here:
if "%VM_TYPE%"=="JRockit" (
set JAVA_HOME=%BEA_JAVA_HOME%
) else (
if "%JAVA_VENDOR%"=="Sun" (
set JAVA_HOME=%SUN_JAVA_HOME%
) else (
set JAVA_VENDOR=Oracle
set JAVA_HOME=D:\Java\jdk\jdk8u40
set VM_TYPE=HotSpot
)
)
This has solved my issue.
Apparently the install routine thinks that your JAVA_HOME is set to the wrong jre. First test is to open a command shell and type in "java -version"
Verify that you see Java 1.7.0 and not 1.6.0
One this had been checked check the ide.conf file or jdev.conf file which java version is configured there. There you should see jdk 1.7.0 configured.
Then you remove the DefaultDomain folder out of the system 11.1.1.x.x.x folder.
Then start jdev again and try to start the integrated server again.
Solution: Windows 7
Delete the C:\Users\\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36 folder and then restart your JDeveloper.
Delete the C:\Users\"username"\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36 folder and then restart your JDeveloper
While upgrading Java version, remove all the files available in the below path
C:\Users\\AppData\Roaming\JDeveloper
Hello worklight team and devs!
We are done working on our development project and everything works fine in the local dev server (Tomcat).
Now we are trying to build the project to be deployed to a testing WAS ND 8.0.3 server.
We've been following the manual in the infocenter and modified each required file as needed (worklight.properties and application-descriptor.xml)
We made this changes to the worklight.properties file:
publicWorkLightHostname=working.hostname.com
# http or https
publicWorkLightProtocol=http
# For default port leave empty
publicWorkLightPort=ourport
publicWorkLightContext=/worklight
wl.db.jndi.name=jdbc/WorklightDS
wl.db.type=DB2
wl.db.url=jdbc:db2:Worklight
wl.db.username=wluser
wl.db.password=passwd
We tested the jdbc source in the WAS console and it works perfectly.
We proceed to build the war, adapter and wlapp (ALL) and we get this error:
[2013-05-21 12:48:44] FWLSE4001W: Failed to resolve JNDI name: "jdbc/WorklightDS".
Application may fail to access the database in runtime. If building for remote server - ignore this warning.
[2013-05-21 12:48:44] FWLST0011E: ====== Worklight Project BPMWorklight-project-customization failed to start: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
[2013-05-21 12:48:44] Activation failed. Bundle didn't start:C:pathto\BPMWorklight-customization.jar
This happens in the developer workstation and if we install Studio in the server, where the jdbc source is created, the same happens.
I guess that Worklight is trying to "obtain" a JDBC source in TOMCAT not WAS, but we are building for WAS, so the build fails and NO files are changed after the error. NO BUILD is executed.
We also tried to execute the build.xml with ANT in studio but we get this error:
Buildfile: C:\Users\Primary User\IBM\Worklight\LIS_SampleCollection\BPMWorklight\build.xml
BUILD FAILED
C:\Pathtofile\BPMWorklight\build.xml:3: Cannot find ../../common.xml imported from
C:\Pathtofile\BPMWorklight\build.xml
Total time: 62 milliseconds
You're help is greatly appreciated!
Thanks a lot!!
Best,
Nicolas E.
If all you require is to deploy the updated-for-WAS .war file in WebSphere, you don't need to do any build operation in Worklight. After updating any file under the server\ folder in Worklight Studio (the Eclipse plug-in), the .war file is automatically being re-created.
The build operation is mainly for creating the binaries and deploying to Worklight Server (database) (again, when using the Eclipse plug-in).
So what I suggest is to:
First update application-descriptor.xml with your context root value in worklightServerRootURL, and keep your .wlapps on the side
Update worklight.properties and save them.
Now you have your app ready to deploy and the .war file ready to deploy.
Move to WAS, deploy the .war file
Hopefully things will work now, so you can load Worklight Console and deploy the .wlapp and .adapter files.
I don't know what you've read in the IBM Information Center, but you can also try going over the following training module from IBM Worklight Getting Started.
Moving from development environment to stand-alone QA and production servers
Notes:
The above is not so convenient, but it is A way to move from your
development environment to another staging environment, or
application server...
The issue might also happen even after following my steps above, and this will indicate that the real issue is in your DB2 declaration in worklight.properties.
I will update this answer tomorrow with some insight regarding the possible DB2 declaration issue.
Background:
I have several builds running on a Windows Server 2003 R2 machine via TFS2010. All of these build definitions have the Path to Publish Symbols set to "\\server\SymbolStore" and the builds run fine.
(Note - I have inherited this set up from a former employee, and I also have other builds running on a separate 2K8 machine that also run without issue)
I am now migrating these builds to a new Windows 2008 R2 build server using the same settings.
Problem:
When running the builds on the new build machine, everything is working fine until the build tries to run the "Publish Symbols" activity in the workflow, at which point I get the error
SYMSTORE ERROR: Class: Server. Desc: Couldn't connect to server.
Error 5: Access is denied. TF270015: 'symstore.exe' returned an
unexpected exit code. Expected '0'; actual '5'.
which also sets the build status to Partially Succeeded.
I have searched the web for these error messages to no avail so far, so does anyone know what might be causing this and how to get it working again?
As always, thanks in advance
Did you check the folder has the right permissions for the service account that is used by Team Build to create/write files ?
Turns out that after I had set up the new build machine, I had left the Credentials for the Build Service Properties (found in the Team Foundation Server Administration Console/Build Configuration) to its default setting which is "NT AUTHORITY\NetworkService". Once I had changed this to use the build service account, the builds are able to write to the symbol store properly
I tried everything I could think of, but I always get this error when I try to start the Apache FtpServer service.
Windows could not start the Apache FtpServer on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 0.
Has anyone got Apache FtpServer to function as a Windows service in Windows 7 or even Windows Vista?
Note:
My Java_HOME environment variable is set as c:\java and I have a symbolic link, linking this directory to the longer C:\Program Files\Java\jdk1.6.0_17.
I also have another symbolic link pointing c:\ftp to the longer C:\Program Files (x86)\Apache Software Foundation\apache-ftpserver-1.0.3.
The only reason I did any of this in the first place is because I was reading that some people were having problems with spaces or long path names, but I tried physically moving the directories as well, all with the same error.
I had the same issue today using apache ftpser 1.0.5., the error message was "Failed installing 'ftpd' service".
The solution was to start the DOS command shell as "Administrator".