-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
invoke command does not invoke on jboss 4.2.2.GA #25
Comments
Certain deployers can only deploy JSP files and not WAR packages. Have you tried accessing /cmd/cmd.jsp on the remote host? It appears to have deployed successfully. |
I can, My mistake I was under the impression that jboss delt with WAR
|
It's still curious that [edit]: actually, invoke wouldn't do much in these cases because you're running it with the default cmd.jsp. It should work fine with jmx_deploy or some other deployer that handles WAR files. |
For DFS:
[2014-06-27 06:06PM] Started at 2014-06-27 06:06PM \n<%\nif\n\n'), ('arg4', True)]), 'timeout': 5.0} [2014-06-27 06:06PM] Successfully deployed '/cmd/cmd.jsp' [2014-06-27 06:06PM] Failed to find a JSP in the deployed WAR [2014-06-27 06:06PM] Finished at 2014-06-27 06:06PM for EJB: ./clusterd.py -i 192.168.56.102 -p 8080 --deployer ejbinvokerservlet --deploy ~/test.war --invoke
[2014-06-27 06:07PM] Started at 2014-06-27 06:07PM On Fri, 2014-06-27 at 15:04 -0700, bryan alexander wrote:
|
Scratch the ejb output here it is:
[2014-06-27 06:09PM] Started at 2014-06-27 06:09PM On Fri, 2014-06-27 at 15:04 -0700, bryan alexander wrote:
|
* src/module/invoke_payload.py -- Fixed correctly parsing the file if a JSP is being invoked -- I was mistakenly appending the random_int to the payload if an ejb/jmx invoker was found, meaning the URL was totally wrong -- This was failing in the bug report, thirdly, because of the DFS deployer. On various JBoss instances, it takes a couple seconds for the server to fully deploy the payload. We now probe the URL 5 times over 10 seconds to give the server adequate time to get it set up.
Thanks a bunch for this bug report; three issues were uncovered with the Cheers! |
I have tried both:
./clusterd.py -i 192.168.56.102 -p 8080 --deployer dfs_deploy --deploy ~/test.war --invoke which gives the following output and deploys the jsp command shell but does not invoke or deploy my war file
[2014-06-27 05:42PM] Started at 2014-06-27 05:42PM
[2014-06-27 05:42PM] Servers' OS hinted at windows
[2014-06-27 05:42PM] Fingerprinting host '192.168.56.102'
[2014-06-27 05:42PM] Checking jboss version 3.2 JBoss JMX Console...
[2014-06-27 05:42PM] Checking jboss version 3.2 JBoss Web Console...
[2014-06-27 05:42PM] Checking jboss version 3.0 JBoss JMX Console...
[2014-06-27 05:42PM] Checking jboss version 4.2 JBoss JMX Console...
[2014-06-27 05:42PM] Checking jboss version 4.2 JBoss Web Console...
[2014-06-27 05:42PM] Checking jboss version 4.0 JBoss JMX Console...
[2014-06-27 05:42PM] Checking jboss version 4.0 JBoss Web Console...
[2014-06-27 05:42PM] Checking jboss version 5.1 JBoss Web Manager...
[2014-06-27 05:42PM] Checking jboss version 5.1 JBoss JMX Console...
[2014-06-27 05:42PM] Checking jboss version 5.1 JBoss Web Console...
[2014-06-27 05:42PM] Checking jboss version 5.0 JBoss JMX Console...
[2014-06-27 05:42PM] Checking jboss version 5.0 JBoss Web Console...
[2014-06-27 05:42PM] Checking jboss version 6.0 JBoss Web Manager...
[2014-06-27 05:42PM] Checking jboss version 6.1 JBoss Web Manager...
[2014-06-27 05:42PM] Checking jboss version 6.1 JBoss JMX Console...
[2014-06-27 05:42PM] Checking jboss version 6.0 JBoss JMX Console...
[2014-06-27 05:42PM] Checking jboss version 7.1 JBoss Management...
[2014-06-27 05:42PM] Checking jboss version 7.0 JBoss Management...
[2014-06-27 05:42PM] Checking jboss version 8.1 JBoss Management...
[2014-06-27 05:42PM] Checking jboss version 8.0 JBoss Management...
[2014-06-27 05:42PM] Checking jboss version Any JBoss EJB Invoker Servlet...
[2014-06-27 05:42PM] Checking jboss version Any JBoss HTTP Headers (Unreliable)...
[2014-06-27 05:42PM] Checking jboss version Any JBoss JMX Invoker Servlet...
[2014-06-27 05:42PM] Checking jboss version Any JBoss RMI Interface...
[2014-06-27 05:42PM] Checking jboss version Any JBoss Status Page...
[2014-06-27 05:42PM] Matched 7 fingerprints for service jboss
[2014-06-27 05:42PM] JBoss JMX Console (version 4.2)
[2014-06-27 05:42PM] JBoss Web Console (version 4.2)
[2014-06-27 05:42PM] JBoss EJB Invoker Servlet (version Any)
[2014-06-27 05:42PM] JBoss HTTP Headers (Unreliable) (version 4.2)
[2014-06-27 05:42PM] JBoss JMX Invoker Servlet (version Any)
[2014-06-27 05:42PM] JBoss RMI Interface (version Any)
[2014-06-27 05:42PM] JBoss Status Page (version Any)
[2014-06-27 05:42PM] Fingerprinting completed.
[2014-06-27 05:42PM] This deployer requires a JSP, default to cmd.jsp? [Y/n] > y
[2014-06-27 05:42PM] Preparing to deploy cmd...
[2014-06-27 05:42PM] Successfully deployed '/cmd/cmd.jsp'
[2014-06-27 05:42PM] Finished at 2014-06-27 05:42PM
I also tried using EJB: ./clusterd.py -i 192.168.56.102 -p 8080 --deployer ejbinvokerservlet --deploy ~/test.war --invoke
[2014-06-27 05:36PM] Started at 2014-06-27 05:36PM
[2014-06-27 05:36PM] Servers' OS hinted at windows
[2014-06-27 05:36PM] Fingerprinting host '192.168.56.102'
[2014-06-27 05:36PM] Checking jboss version 3.2 JBoss JMX Console...
[2014-06-27 05:36PM] Checking jboss version 3.2 JBoss Web Console...
[2014-06-27 05:36PM] Checking jboss version 3.0 JBoss JMX Console...
[2014-06-27 05:36PM] Checking jboss version 4.2 JBoss JMX Console...
[2014-06-27 05:36PM] Checking jboss version 4.2 JBoss Web Console...
[2014-06-27 05:36PM] Checking jboss version 4.0 JBoss JMX Console...
[2014-06-27 05:36PM] Checking jboss version 4.0 JBoss Web Console...
[2014-06-27 05:36PM] Checking jboss version 5.1 JBoss Web Manager...
[2014-06-27 05:36PM] Checking jboss version 5.1 JBoss JMX Console...
[2014-06-27 05:36PM] Checking jboss version 5.1 JBoss Web Console...
[2014-06-27 05:36PM] Checking jboss version 5.0 JBoss JMX Console...
[2014-06-27 05:36PM] Checking jboss version 5.0 JBoss Web Console...
[2014-06-27 05:36PM] Checking jboss version 6.0 JBoss Web Manager...
[2014-06-27 05:36PM] Checking jboss version 6.1 JBoss Web Manager...
[2014-06-27 05:36PM] Checking jboss version 6.1 JBoss JMX Console...
[2014-06-27 05:36PM] Checking jboss version 6.0 JBoss JMX Console...
[2014-06-27 05:36PM] Checking jboss version 7.1 JBoss Management...
[2014-06-27 05:36PM] Checking jboss version 7.0 JBoss Management...
[2014-06-27 05:36PM] Checking jboss version 8.1 JBoss Management...
[2014-06-27 05:36PM] Checking jboss version 8.0 JBoss Management...
[2014-06-27 05:36PM] Checking jboss version Any JBoss EJB Invoker Servlet...
[2014-06-27 05:36PM] Checking jboss version Any JBoss HTTP Headers (Unreliable)...
[2014-06-27 05:36PM] Checking jboss version Any JBoss JMX Invoker Servlet...
[2014-06-27 05:36PM] Checking jboss version Any JBoss RMI Interface...
[2014-06-27 05:36PM] Checking jboss version Any JBoss Status Page...
[2014-06-27 05:36PM] Matched 7 fingerprints for service jboss
[2014-06-27 05:36PM] JBoss JMX Console (version 4.2)
[2014-06-27 05:36PM] JBoss Web Console (version 4.2)
[2014-06-27 05:36PM] JBoss EJB Invoker Servlet (version Any)
[2014-06-27 05:36PM] JBoss HTTP Headers (Unreliable) (version 4.2)
[2014-06-27 05:36PM] JBoss JMX Invoker Servlet (version Any)
[2014-06-27 05:36PM] JBoss RMI Interface (version Any)
[2014-06-27 05:36PM] JBoss Status Page (version Any)
[2014-06-27 05:36PM] Fingerprinting completed.
[2014-06-27 05:36PM] Preparing to deploy /home/bob/test.war...
[2014-06-27 05:36PM] This deployer requires a JSP, default to cmd.jsp? [Y/n] > y
[2014-06-27 05:36PM] cmd deployed to 192.168.56.102 (/cmd160)
[2014-06-27 05:36PM] Finished at 2014-06-27 05:36PM
Neither works in executing the war file.
The text was updated successfully, but these errors were encountered: