I want to ask you about building red5 application on centos
I prepare all the files and configurations
APP_NAME
=> WEB-INF
=>lib
=>src
=> Application.java
=>classes
=> Application.class
=>build.xml
=>red5-web.xml
=>web.xml
=>red5-web.properties
=>log4j.properties
=>build.properties
all is ok the building also ok and make jar file is ok
ant build
ant build
BUILD SUCCESSFUL
but when I restart my red5 server all demos applications and my new application not work
if I make new netConnection I receive this error message :
netconnection.connect.failed
netconnection.connect.closed
Please help me
Thanks
You should first check the log files produces by Red5 in the folder "log" if there are startup or runtime exceptions.
it will be required that you have a minimum knowledge of Java and how to read Java log files in order to be able to implement a solution with Red5.
Red5 can be installed as stand alone server or as a war deployment.
The procedure is to create war deployment of red5 version 0.8(old version). (Lengthy, please bear with me).
Download and install jdk1.6, glassfish2.1 and netbeans 6.5 on linux.
Download "Red5War_0.8.0.war".
I am sharing in the hope that the following may help the community to create a deployable war red5 version 0.8 on glassfish2.1 by following the steps using in Netbeans 6.5:
Step 1: Un-Zip the Red5War_0.8.0.war
Step 2: Create a web project named "red5" in Netbeans
Step 3: Copy the content of "/WEB-INF/classes" of inflated war folder and paste it in "Source Packages" of Netbeans Project.
Step 4: Right Click "Libraries", add "JAR/Folder", navigate to "/WEB-INF/lib" of inflated war folder, select all the dependency jars and Click On "Open" of Netbeans Project.
Step 5: Delete WEB-INF of Netbeans Project (Note : Ignore Warning/Error).
Step 6: Delete META-INF of the inflated folder.
Step 7: Copy the remaining content ("/WEB-INF/classes" and "/WEB-INF/lib") of the inflated folder to "Web Pages" of Netbeans Project.
Step 8: Open the following ports in the firewall TCP/843,TCP/1935,TCP/5229,TCP/5080
Step 9: Run the project
Step 10: Deployable war file "red.war" is created in the Netbeans Project Folder(../NetBeansProjects/red5/dist/)
Similarly, you can create new projects...
Best wishes!
Arumugam A.V
p.s:Please share your findings in creating new version(1.0, 1.0.1, 1.02) war deployments using new version netbeans, jdk on new version glassfish server(3.x).
Related
I want to use JavaMelody to monitor the SQL requested by a Glassfish Application Server. There are step-by-step instructions on https://github.com/javamelody/javamelody/wiki/UserGuideAdvanced#monitoring-of-sql-requests-and-of-jdbc-connections-in-glassfish-v3
I followed the instructions (I didn't download javamelody-objectfactory.jar but used javamelody-core-1.54.0.jar instead) and I get this error when clicking on the refresh button (javamelody web page) :
server.log :
exception while collecting data
java.lang.NoClassDefFoundError: org/jrobin/core/RrdException
at net.bull.javamelody.Collector.getCounterJRobin(Collector.java:836)
at net.bull.javamelody.Collector.collectJRobinValues(Collector.java:489)
...
any idea how to resolve this ?
jrobin-1.5.9.1.jar is installed in the lib folder of glassfish (and in my ear project).
thanks !
javamelody-objectfactory.jar (java source included in the jar) and javamelody-core jar file are absolutely different things. The first is to make the datasource monitorable in Glassfish and the second is the monitoring tool itself.
First fix the exception. You should probably put javamelody-core jar and jrobin jar files in your ear project (and not one in lib folder of Glassfish and one in ear).
Then if the monitoring reports don't include SQL monitoring for the datasource declared in Glassfish, use the javamelody-objectfactory.jar including all steps as said in the doc.
I tried to follow the war generation instructions by changing the warName in build.gradle to moqui-plus-runtime.war and running gradle addRuntime and then gradle deployTomcat. There were no errors in the war build and I checked to see that the war file got installed as ROOT. I did not make any other changes (still using MoquiDevConf and I already had other system parameters in MoquiInit.properties.)
When I startup tomcat8, I don't see any errors in the log file and it says that it is loading moqui-plus-runtime, but when I make any request in the browser, the localhost_access... log shows 404 for any request.
Can you tell me what things I might of missed or how I would go about debugging this - there is very little info in the log files other than the 404 messages.
I followed the following steps to deploy to a Tomcat instance on the same machine. This is from memory as my production machine is currently offline for the next couple of weeks.
Edit tomcatHome to point to correct location
I personally run a gradle cleanAll first to remove old WARs etc
Run gradle build
Optionally run gradle loadProduction to load the production database, alternatively you can run java -Dmoqui.conf=conf/MoquiProductionConf.xml -jar moqui-1.5.3.war -load -types=seed,seed-initial so that you can pick which data types you want to load into production etc.
Stop Tomcat from running, probably optional but the next step deletes files & folders from a deployed tomcat instance.
Run gradle addRuntimeTomcat this task adds your runtime and also copies over the completed WAR into the Tomcat webapps directory if you set the location correctly in step 1.
Start Tomcat
Check Tomcat logs for any startup errors
Hope this helps
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.
I am trying to get our Mavenized web application up and running in a freshly installed IDEA 11.1.4 Ultimate (Windows 7) under a freshly unzipped Glassfish 3.1.2.2. I have done this many times in Eclipse, but am not familiar with IDEA.
I can build and deploy it just fine, but when I try to access pages with JSP-content I get:
PWC6345: There is an error in invoking javac. A full JDK (not just JRE) is required
The Glassfish Application Servers entry adds the javax.ejb.jar, javax.servlet-api.jar and javax.servlet.jsp-api.jar as libraries.
I have set the project SDK to point to a full JDK resulting in:
(which does not seem to include a jar with javac)
The IntelliJ tutorials I've found so far, does not mention this problem. My guess would be that the "please start using this JDK" information is not passed on to Glassfish, so it just picks up the system JRE.
What configuration step have I missed? I do not want to edit configuration files - I expect the IntelliJ plugin to do this if I know how to tell it to.
I got the same notification and just changed in admin port -> Configurations -> server-config -> JVM Settings -> Java Home as "C:\Program Files\Java\jdk1.8.0_72", and it started working.
PWC6345: There is an error in invoking javac. A full JDK (not just JRE) is required.
I was getting same error after restarting my glassfish 4 server.When I am trying to access my deployed application it was saying to mention full JDK.
login to Glassfish admin console.(http://localhost:4848).
Go to Configuration---->server-config--->JVM Settings
Set the java home with your correct jdk home (ex:C:\Program Files (x86)\Java\jdk1.8.0_121).
Restart the server.
It will work fine.
Next solution helped me
source: http://alvinalexander.com/blog/post/java/fixing-glassfish-jdk-path-problem-solved
Find your asenv.bat file. C:\Program Files\glassfish-4.0\glassfish\config\asenv.bat
Open it in text editor and find strings like "set AS_ = blahblah"
Add this string there "set AS_JAVA=C:\Program Files\Java\jdk1.7.0_60" (print your own JDK path here). If string "set AS_JAVA= blahblah" already exists then just fix the path.
Add JDK_HOME\lib\tools.jar file to the JDK configuration Classpath.
However, the problem in your case may be different as Glassfish JDK is not taken from IntelliJ IDEA settings, this question may help:
How do I specify the jdk for a glassfish domain?
I have downloaded solr from :
http://svn.apache.org/repos/asf/lucene/dev/trunk/
and when i try to start solr by :
/solr/example/java -jar start.jar &
and try to open in browser at 8983 port it is not opening saying ?
HTTP ERROR: 404
Problem accessing /solr/admin/schema.jsp. Reason:
NOT_FOUND
Powered by Jetty://
how to start by developer trunk actually want to use solr 4.0
If you have downloaded the source code from trunk, it does not come bundled with the solr.war.
Can execute ant command from the base directory OR
Build the artifacts for solr by executing ant dist from the solr folder
Once the artifacts is built, you will find a dist folder with the apache-solr-xx.war
You would need to copy the war (and rename to solr.war) into the /solr/example/webapps/ for solr to be available.
This should get you started.
Example steps -
1. svn checkout http://svn.apache.org/repos/asf/lucene/dev/trunk/ solr_trunk
2. cd solr_trunk
3. ant or ant dist (from solr folder)
4. Copy the war file (and rename to solr.war) from solr/dist folder to /solr/example/webapps/
5. /solr/example/java -jar start.jar
See the README.txt:
To compile the sources run 'ant compile'
This will compile you the solr.war.