JBoss 6.1 App server startup problems:Module not found exception - jboss6.x

My JBoss Application server is throwing a Module not found exception when starting it.I unzipped Jboss and started it. Could you please tell if i have to make any configuration setting to make it start.
org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:224)
at org.jboss.modules.Main.main(Main.java:341)
Press any key to continue . . .
Thanks,
-Vijay

A possible reason is your jboss runtime is corrupt. Reason for
**org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:224)
at org.jboss.modules.Main.main(Main.java:341)**
is that jboss-eap-6.2\modules\system\layers\base\org\jboss\as\server\main package is missing inside your jboss directory. This package contains jboss-as-server-7.3.0.Final-redhat-14.jar and module.xml which are essential to run jboss server.

I managed to finally solve it with some help from someone from the Jboss community.
You can see the answer here: https://community.jboss.org/message/737218#737218
Basically I turned on TRACE logging on the modules and saw that I'm actually missing javax.jms.Destination, so I just added dependency to that module.

Related

Can I run Node.js on cPanel without CloudLinux?

I'm trying to deploy a node.js app on my server.
I've followed the instructions laid out by cPanel in their documentation here: Guide to Node.js Installations and here: How to Install a Node.js Application. I want to do this without CloudLinux and given Apache's Node.js module it seemed to be possible.
However, even though deploying the app in the backend seems fine, I'm getting this error when trying to access the app in my browser:
The Phusion Passenger application server tried to start the web application through a Passenger-internal helper tool called the SpawnEnvSetupper. But that helper tool encountered an internal error.
Error Details: Failed to initialize LVE library: : init_lve error [2]
The stdout/stderr output of the subprocess so far is: Error: Failed to initialize LVE library: : init_lve error [2]
I don't know much about LVE but I do know that it's a part of CloudLinux. So, do I still need to have CloudLinux installed after all? Thanks.
Update:
Tried deploying the same node.js app on a subdomain and had the same error. Then I tried to deploy it on another server that I manage (following the same steps) and was able to do so successfully. My hosting company seems to think there was an issue when I uninstalled CloudLinux from my server. (I had previously set it up to run Node and then had it removed once I discovered that I wouldn't need it.)
To answer my own question ...
Yes, Node.js can run on cPanel without CloudLinux.
By following the instructions in the cPanel documentation here (Guide to Node.js Installations) and here (How to Install a Node.js Application), a Node.js app can be deployed successfully.
In my particular situation above, I had installed CloudLinux on my server originally to deploy Node.js apps before cPanel came out with their own module for Apache. Given that I was paying extra for the CloudLinux software, I wanted to remove it from my hosting account and leverage the Apache module. During the uninstall, it turns out that LVE and other libraries related to CloudLinux were not removed correctly causing the error (not sure why yet). By simply removing those and restarting my server the Node app started functioning properly again.

Intellij Idea run configuration with ember.js on ubuntu

I am having a problem with the run configuration of ember on intellij idea on ubuntu 14.
I have installed ember using npm and I have followed a tutorial on my teacher's site on how to correctly configure intellij to use both maven and ember. I had no problem configuring the first part (maven), however at the second part, which was basically the same, I couldn't find the file he was refering to. Here is the picture:
tutorial
And here is the error:
[error]
Error: No ember-cli-build.js found. Please see the transition guide: https://github.com/ember-cli/ember-cli/blob/master/TRANSITION.md#user-content-brocfile-transition.
at CoreObject.module.exports.Task.extend.setupBroccoliBuilder (/home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/lib/models/builder.js:56:13)
at CoreObject.module.exports.Task.extend.init (/home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/lib/models/builder.js:89:10)
at CoreObject.superWrapper [as init] (/home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/node_modules/core-object/lib/assign-properties.js:32:18)
at CoreObject.Class (/home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/node_modules/core-object/core-object.js:32:33)
at CoreObject.module.exports.Task.extend.run (/home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/lib/tasks/build.js:15:19)
at /home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/lib/commands/build.js:32:24
at lib$rsvp$$internal$$tryCatch (/home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1036:16)
at lib$rsvp$$internal$$invokeCallback (/home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1048:17)
at /home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:331:11
at lib$rsvp$asap$$flush (/home/user/.nvm/versions/node/v5.0.0/lib/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1198:9)
Could you please help me find the file he was referring to in the tutorial (since "usr/bin" doesn't have any "ember" files)?
New error about permissions:
error
Do you have a brocfile.js in your project? If so, rename it to ember-cli-build... Apparently you installed a newer version of ember... You might want to re-run ember init
Have a look at https://github.com/ember-cli/ember-cli/blob/master/TRANSITION.md#user-content-brocfile-transition as well for more information.
Depending on how you installed ember/ember-cli it would lie under (if you don't use nvm):
~/.npm/
or
in your project structure:
<project_dir>/node_modules and <project_dir>/bower_components
Maybe you didn't initialize ember project. Run ember init in webapp directory

Encountering errors of obtaining dependencies when starting grails application

I'm new to Grails web framework. I got this error when running my first grails app from the terminal. Below is the error I got.
> | Downloading:
> org/apache/commons/commons-parent/17/commons-parent-17.pom | Error
> Resolve error obtaining dependencies: Failed to read artifact
> descriptor for org.hamcrest:hamcrest-core:jar:1.3 (Use --stacktrace
> to see the full trace)
>
> | Error Required Grails build dependencies were not found. This is
> normally due to internet connectivity issues (such as a misconfigured
> proxy) or missing repos itories in grails-app/conf/BuildConfig.groovy.
> Please verify your configuration to continue.
I'm running this app with the internet connection but this error still occurs. How can I fix this error?
are u sure you are using a the correct download for grails, it seems that your trying to connect to the internet and your grails can't ? may be check your proxy settings? or what you are really trying to do in the command line ?
Your console log says, you can not connect to internet for downloading dependencies.
But its not the case. Maven has stopped http repositories and that is the root cause.
You have to use https. If you could not connect to https for some reason, here is workaround to that:
mavenRepo "http://insecure.repo1.maven.org/maven2/"
Putting above line in BuildConfig.groovy will resolve your issue and start downloading dependencies.
What mavenRepo's do you have in your BuildConfig.groovy. I found that I had to add a few, here's mine:
repositories {
inherits true // Whether to inherit repository definitions from plugins
grailsPlugins()
grailsHome()
mavenLocal()
grailsCentral()
mavenCentral()
// uncomment these (or add new ones) to enable remote dependency resolution from public Maven repositories
mavenRepo "http://repository.codehaus.org"
mavenRepo "http://download.java.net/maven/2/"
mavenRepo "http://repository.jboss.com/maven2/"
mavenRepo 'http://repo.spring.io/milestone'
}
Have you tried running:
grails refresh-dependencies
before you try to run your app?
What version of Grails, SO and JDK do you have?, in Windows 8 with JDK Java SE 7u45 and Grails 2.3.1 i have a lot of problems; I had to make a downgrade to JDK

Webstorm: debugging node.js sails app

I'm having a hard time finding the right combination of settings to allow me to debug my node.js sails application in webstorm.
These are the settings I've tried using, both configurations work (as in sails starts) but none is stopping at breakpoints.
If I go to the breakpoints menu and turn on 'Any exception enabled' - it does stop for exceptions, but never hits my breakpoints.
Any ideas? I'm on webstorm 7.0.1 and Node 0.10.18 / Sails 0.9.7
You don't need the --debug in node parameters. Here is my config and i am on 7.0.1 and node 0.10.4
Let me know if it helped. Also, you are hitting the bug to run debug right?
Also, can you please invalidate caches/ restart? That helps sometimes. Here is a snapshot in the file menu.
I had the same problem and simply installed sails local to the project and everything worked fine. Not sure why the configuration can't resolve the globally installed sails as that is the error I was getting, but the local install works fine. I should investigate further, but I'm lazy :)
When you open a new project on WebStorm, it detects the package.json file and it will ask you to install the dependencies locally. After that, by using the configuration mentioned before (not necessarily by using sails lift but using app.js directly instead), you can debug you application from WebStorm. Another way to do it, is by using this tool, that works like a charm: https://github.com/node-inspector/node-inspector :)

Jelly module throwing internal server error

The Jelly module throws a 500 internal error. I have no idea why it does this and how to solve this.
When I remove jelly module folder from the server or simply rename any of the Jelly module files, the error disappears (Kohana throws an error because Jelly Class is not found which is normal).
I don't understand why Jelly would throw an internal error, it just does not make any sense!
(The error does not come from the folders and files permissions. I made sure that they're all 755 and 644).
(Everything works fine locally - WAMP server)
Thank you.
Check you're on the latest version of Jelly.
Check all your files for syntax errors. If you don't get an error page returned from Kohana it's probably because you've crashed php in some way.
Sorry if this doesn't help, please post more code/debug info.
Thank your for your answers. The problem was solved somehow. I have no idea what happened.
It seemed to work when I removed send_headers() in the bootstrap but it really annoyed me because I needed it.
Then I replaced Request::instance($_SERVER['PATH_INFO']) by Request::instance() in the echo in the bootstrap and it worked...
More info about the error logs there: http://forum.kohanaframework.org/comments.php?DiscussionID=6322&page=1

Resources