1 of 1 people found this helpful
If that doesn't help, post the error you are getting in the console log when starting the second instance.
As per the document my configuration was correct. Only thing is that i have changed the port also and one more thing i did was the way i have started the AS
nohup ./run.sh -Djboss.bind.address=xxx.x.x.xxx &
This i have changed to
nohup ./run.sh -c default -b xxx.x.x.xxx &
I guess node1 and node2 should be what configuration setup you are making, in my case it is deafult.
And it is not giving any error. But only one issue i found is there when i started the same as a single instance ( that means in the first instance). As a single instance it is working perfectly.
I am posting the error here
[EARDeployer] Started J2EE application: file:/usr1/jboss-with-security/jboss-4.2.3.GA/server/default/deploy/jmyapps.ear/
11:23:04,274 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
we are using JORAM as the JMS provider.
If i made anything wrong please point out.
I am very confused. First you say:
And it is not giving any error.
and then you say:
rasa wrote:I am posting the error here
Also, the "error" you posted is not the full error, rather it is just the heading for a list of errors.
By the way, I hope that you did not use -"c default" for both instances. The first step to running multiple instances is to create a second configuration (for example, copy 'default' as 'node2') and then run each separately:
run -c default -b xxx.xxx.xxx.xxx
run -c node2 -b yyy.yyy.yyy.yyy
Actually why i said there is no error because in single instance also it is giving the same error description but it is working fine. Then i posted it because i am not sure whether that is creating the issue.
I have two jboss instance and i started both by using the above mentioned command but diff ip. But one thing i did was in from second instance i have deleted jboss-web deployer folder since i am using that configuration for handling my messaging part.
Then let me ask you whatr you mean by "it is not working"
By the way, by removing jboss-web.deployer, you will not be able to open a browser and connect to that instance.
Actually for the version 3.2.5 we did that way, we deleted jboss.web deployer from second instance and we are not deployed any jsp pages in that jboss, it contain only mdb and the supporing java class. We have deployed our application in first jboss and it contains jsp pages.
I did this based on 3.2.5, i got the document from my sysadmin. If anything wrong i did please guide me to solve those issues.
You still did no mention what you mean by: "it is not working"
I think i explained about the configuration, when i give http://ip:port/myapps/Jsp/index.jsp in browser then i am getting unable to connect error. That shows appserver is not started , and nothing unusual in log also.
Of course it doesn't work. You said you remove the jboss web deployer and without it no web apps get deployed thus http requests like the one you mentioned will not be processed.
No, that was not the issue. Solved the issue now. Actually two ips are there in my server and http request is send through the second ip that was the issue. My second instance is used as an ejb container so no need to put webserver. Hope it is fine.
Yes, it is working but one issue is there the messaging which is confgured in the second instance is not working. So i need to debug. I have started both instance in debug mode. The first instance is working fine but when i am trying to connect the second instance from my eclipse i am getting following error.
Launching xx' has encountered a problem.
Failed to connect to remote VM. Connection refused
i have tried address=ip:port also.
following are the entry in my sh file
JAVA_OPTS="-Dprogram.name=$PROGNAME $JAVA_OPTS -Dsalmon.props.path=/usr1/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/salmonprops -Djasper.reports.compile.class.path=/usr1/jboss-4.2.3.GA/server/default/lib/itext-1.3.1.jar:/usr1/jboss-4.2.3.GA/server/default/lib/jasperreports-1.3.3.jar -Djava.awt.headless=true -verbosegc -XX:+PrintGCDetails -Xms840m -Xmx840m -XX:NewSize=300m -XX:MaxNewSize=300m -XX:SurvivorRatio=6 -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=188.8.131.52:4142,suspend=n";
And i noticed one thing i am not able to do ftp for that ip, is that is an issue ???
Message was edited by: Rasa Here
This will not work. Eclipse uses some global information to identify the key ports (JNDI, RMI, JMX) which JBoss AS is using. Obviously the first instance of JBoss AS is using the ports Eclipse expects. But there is no way I know of to configure Eclipse to use the port for the second JBoss AS instance without preventing Eclipse from attaching to the first instance.
but when i am trying to connect the second instance from my eclipse i am getting following error.
Launching xx' has encountered a problem.
Failed to connect to remote VM. Connection refuse
Why this *&^%$#@#$ editor deleted half of my response!!!! (Sorry, the new editor just make me crazy.)
Anyway, here is the rest of my reply:
but one issue is there the messaging which is confgured in the second instance is not working.
Finally, the reason behing "it is not working." Based on various posts that I have seen, sending messages from one instance of JBoss AS to another is a fairly tricky business. So the problem might not at all be with the second instance, but rather with how your code in the first instance goes about sending messages. I would write a standalone client that sends messages to the second isnatcne and see if that works. If it does, we can then look into what is wrong with your code that sends messages. If it does not work, we can look into what is wrong with the configuration in iunstance 2.
ok and thanks to the great effort. I will try from my side also.