After deploying contacts-portlet in jboss (changes in main.js), css of contacts-portlet is not loaded because of an error regarding compass.
The same portlet exists also on a staging environment with jboss also running as application server. I copied the exact same contacts-portlet.war from staging to production, after deleting the existing on production. After the new deployment, the compass not found error is still displayed on firebug console.
Has anybody met something similar?
The 6.1 compass issue is not the case in Liferay 6.2.
Any help would be appreciated.
Related
I have ran into something interesting. We are upgrading our SAP BO from 4.2 SP2 to 4.2 SP5. So we have a java application which runs on JBoss connects to the BO reports.
So as part of upgrade I have updated all my SAP jars and tried connecting to the new CMS. To test out initially i used the below code and ran it using main method I was able to connect to the CMS and get the Session.
ITrustedPrincipal trustedPrincipal = sessionMgr.createTrustedPrincipal("user1", "myCMS:6400");
session = sessionMgr.logon(trustedPrincipal);
But when I run the same code on JBoss, I get
Could not reach CMS 'myCMS:6400'. Specify the correct host and port
and check for network issues
Can some one please suggest what I am doing wrong?
We are using Wildfly 8.2.0 Server and sometimes the hot deployment doesn't work, it says EAR/WAR module has been deployed but changes are not reflecting until we restart our Application Server. Please let me know if anyone has faced this issue and how to resolve this. Thanks.
I am trying to get the Apache DayTrader benchmarking app on OpenShift quickstart working see link https://openshift.redhat.com/app/console/application_type/quickstart!17609
I have a free 3 gear openshift online account and the quickstart starts up but then after a while posts the message
"Application creation is taking longer than expected. Please wait a few minutes, then refresh this page."
Waiting and refreshing the page shows the whole application rolled back and removed from the gear.
I suspected it might need a larger gear but I can build an openshift gear manually with JBoss Enterprise Application Platform 6 and PostgreSQL 9.2 as per requirements in a small gear
I tried manually building the application via jboss developer studio and downloaded the git locally, imported it as a general project,converted to Mavern project, started openshift application wizard and choose the jbosseap-6 app type with postgresql-9.2 cartridge and went through using the existing daytrader project.
That all seemed to work and the app was created in my openshift online gear
Cartridges
JBoss Enterprise Application Platform 6
Status: Started
Gears
1 small, Storage 1 GB PostgreSQL 9.2
the account webpage then displays
"Welcome to your JBoss EAP application on OpenShift"
but I cant seem to access the daytrader index.jsp or app from there.
If anyone has successfully built Daytrader on openshift either manually or via quickstart could they please post the steps.
I am just starting with jboss and the solution may be an absurdly simple oversight on my part.
Much appreciated John
I am assuming this is not your cartridge. If that is the case, you should try logging an issue on the github project that feeds into that quickstart here: https://github.com/gvijayar/daytrader
The creator of the cartridge should be able to help you out.
I posted ( some time ago ) the issue in github for gvijayar but there has been no reponse. I have managed to build via command line as per "Deploying from Source" making allowance for the error.
The application name needs to change in the create command to be consistent across all the commands you list.
ex:
rhc app create -a daytradereap -t jbosseap-6 -g large
but the quickstart still fails consistently.
My setup is as following:
Production web server with Glassfish 3.1.1 wrapped into a windows service.
Developing environment with Netbeans 7.1 with the included Glassfish server.
I thought a valid way to deploy updates to production server was to copy the content of the Netbeans /build directory and it worked well many times.
Unfortunately I experienced a major problem, described in the link below, where new roles were not recognized because glassfish had cached data somewhere else.
Glassfish: how to investigate roles/groups problems
I checked the Glassfish configuration a lot but couldn't find any parameters like 'rebuild cached data at the server start'. So my question is how can I deploy updates in my production server being sure that my changes will not be invalidated by pre-compiled cached data ?
Thanks
Filippo
Any time I try to publish my Portal project on a Websphere Portal 6.1 Server, I get the following error message:
Portal project publishing is not supported on WebSphere Portal v6.1 Server
Is that really true or have I done something wrong?
I'm trying to deploy a portal project, with the underlying goal of publishing a new theme.
Unfortunately, any time I try to deploy, I get the error message listed above from the IDE and no errors in the console.
The RAD version is 7.0.0.7.
Not sure this will help, but:
Limitation: Although the WebSphere
Portal installer contains an advanced
option to install an empty portal,
Portal Designer relies on
administration portlets for setting
access control; therefore, publishing
a portal project to an empty portal is
not supported.
Are you trying to deploy a portlet or an entire portal project? What version of RAD are you using? Any other information in the error log? (Both within RAD & on WP server) Is the error message posted verbatim?
It is possible to deploy such a project to a WebSphere Portal. I use v6.2 and deploy portlets, which are parts of a big Portal project, every day. I'm only a starter in such a stuff, but I can say that WebSphere is really buggy. You know, it is a big difference to run a deployed app "locally, in a workspace" or "on a server". I suggest you to work out with server options - administrative console.