jboss 7 standalon-full.xml as config - jboss

I want to start JBoss AS v7 and set standalone-full.xml as default config. In my standalone.conf I put this line:
JAVA_OPTS="$JAVA_OPTS -Djboss.server.default.config=standalone-full.xml".
But when I start server, it take standalone.xml as config. My OS is Win7

You can configure JBoss to start using standalone-full.xml from Eclipse using below steps :-
Locate JBoss Server from Eclipse Server Tab :-
Double click on server to open JBoss Runtime Server Configuration :-
Now, Click on Runtime Environment link to open below dialog which allows to edit Jboss Server Runtime Configuration :-
Click on Browse button to locate standalone-full.xml & save the configuration. Start JBoss server from Eclipse, it will use full profile defined in standalone-full.xml to start.

Edit jboss-as-7.1.1.Final\bin\standalone.conf.bat and change
From
set "JAVA_OPTS=%JAVA_OPTS% -Djboss.server.default.config=standalone.xml"
To
set "JAVA_OPTS=%JAVA_OPTS% -Djboss.server.default.config=standalone-full.xml"
OR
Once can simply use below command to start the server form command prompt.
jboss-as-7.1.1.Final\bin>standalone.bat -c standalone-full.xml

For windows, you need to edit standalone.conf.bat. standalone.conf is for linux/unix environments.

Related

JBoss developer, wildfly standalone configuration

Can you help me starting wildfy in JBoss Developer Studio with configuration from standalone config file.
I need to use IPv6 so i set
JAVA_OPTS="-Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=false"
When i run my server as standalone from cmd everything is ok
standalone.sh -c standalone-full.xml
but eclipse don't see this change.
jboss config
The op commented: I found a solution here:
http://www.nailedtothex.org/roller/kyle/entry/articles-wildfly-jvmparams

Glassfish3 cant start cause bootstrap jar not found

i installed the glassfish3 tools for eclipse juno and i installed
glassfish3 on my computer under C:\glassfish3.
I created a new server with glassfish3 tools for eclipse and everything
was setup correctly.
When i now want to start the galssfish server i get the error:
bootstrap jar not found
nothing else. No more details and no log output.
how can i get my glassfish running?
I had the same problem, check if folder where glassfish is the same configurated in eclipse.
Preferences > Server > Runtime Environments
double click on the server. it will open the server Overview.
Under general information you will find two link. runtime envionment and open launch configuration.
click on runtime environment, you will see some error mark there.
eclipse is not updatind the path when you create a new server or change the server domain path.
I provided the correct path there. however I am using glassfish 4.
it fixed error for me - bootstrap jar not found.

Automatic start of jconsole from eclipse

I wondered if there is a plugin or someone has a script to start jconsole automatically when I run or debug an application from eclipse. Maybe adding the classpath too. I googled but didnt find anything. In most cases this is a sign that it doesnt work or its to easy to ask :D
There is a plugin for VisualVM (http://visualvm.java.net/eclipse-launcher.html) which does exactly this.
Given that VisualVM is a superset of the jConsole and it also supports jConsole plugins natively you can safely use VisualVM instead of jConsole.
This is not about automatic start, but it is about connecting the program running in eclipse through jvisualvm.
In eclipse, in the Main class java file do the below, then run as java application.
Right click --> Run As --> Run Configuration --> Arguments --> VM argumanets --> Add the below
-Djava.rmi.server.hostname=hostname -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=10001
Then open java visaul vm from JDK bin directory. In that
File --> Add JMX Connection --> In connection text box --> localhost:10001
This will start your profiling now.

Starting tomcat in eclipse vs command line

I am using tomcat 6 and when I start it from the command line the application it's running works fine, but when I start tomcat from eclipse (I added it as a server in eclipse) I get a 404 error when I try to run the application in my browser. Any ideas why this is?
By default, when you reference an existing Tomcat instance in Eclipse, only its engine is been used. All already-deployed webapps in Tomcat's /webapps folder are ignored. You seem to expect that they are also accessible when you start Tomcat from inside Eclipse.
You need to configure the Tomcat server reference in Eclipse to set Server Locations to Use Tomcat installation instead of (default) Use workspace metadata. Double click the Tomcat server entry in Servers view to edit it.
This way, everything which is deployed to Tomcat, outside control of Eclipse, will also be available when you start Tomcat from inside Eclipse.

Connecting Eclipse to Weblogic server hosted on UNIX machine

I have weblogic installed on a UNIX machine and my source code is in SVN.
I am trying to use the source code in Eclipse and want to know how I can integrate/connect the weblogic server hosted on UNIX machine so that I can develop/modify my application on Windows machine.
Try using remote debugging. There is a question on StackOverflow about it here: Weblogic remote debugging using eclipse.
This is more detail from Oracle:
In the startWebLogic.cmd script, specify the JAVA OPTIONS with:
set JAVA_OPTIONS=-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=4000,server=y,suspend=n
The -XDebug parameter enables debugging. The -Xnoagent parameter disables the default sun.tools.debug debug agent. The -Xrunjdwp parameter loads the JPDA reference implementation of JDWP. Debugging is enabled on port 4000. The JDWP protocol is the protocol used to debug with a remote debugger.
Source: Remote Debugging on WebLogic Server
And how to set up the configuration in Eclipse:
Next, configure a debug configuration for the Eclipse project. Select the Debug option in the Debug option list. The Debug frame gets displayed. In the Debug frame select the Remote Java Application node. Right-click on the node and select New. In the Debug configuration frame specify a name for the Debug configuration. Select the project that is to be debugged. Select the EclipseWebLogic project previously created in the Eclipse IDE. Select the default value for Connection Type. In the Connection Properties, specify localhost as the Host and specify the Port as the port that was specified in the startWebLogic batch script of the WebLogic server, [4000]. Click on the Apply button. A remote Java application debug configuration gets added.
Source: Configuring Eclipse for Remote Debugging a WebLogic Java Application