xcp 2.1 after app deploy blank page

Darmin_M

Hi,

I have just "successfully" deployed an app from xcp designer on xcp 2.1.

After I try to open the application http redirects to signin.jsp but page is blank (no errors).

I tried opening from different web browsers, locations, but same error.

Any ideas?

Find more posts tagged with

Comments

Malthi

Please check if there is enough space in the app server. You may want to clear the temp folder and logs and m2 cache.

sometimes restarting the app server also helps.

Henk_Kruger

I had this same problem and clearing the cache, redeploying from scratch etc. didn't work for me at all, and in the end I realised this wasn't the issue either.

I then discovered a JavaScript error in the "expressions.js" file that is generated by xCP. My problem was caused by a non-terminating string from one of the value formulas for a Value Display widget. I accidentally had a carriage return in my string formula, which xCP didn't pick up as an error - or which xCP didn't translate correctly in the expressions.js file, depending on how you look at it. After deployment, the expressions.js file didn't like the carriage return, thinking it was a non-terminating string. I removed the carriage return and I was able to redeploy successfully.

The problem actually comes in with how the browser reads the expressions.js file. I would recommend inspecting all formulas (or as xCP calls them, expressions) since the last successful deployment, and see if this might be the case for you as well. Check carefully though, as you might not see the carriage return unless you actually hit a 'del' or 'backspace' in the right place in your formula.

Darmin_M

Hi,

I played around with this a little bit more.

When I run the page directly on my tomcat instances it works.

On my apache load balancer I get the login page, after that it is blank.

My other sample application works fine on load balancer...

Henk_Kruger

If it works in 1 instance and not the other, I would suspect a possible cache issue either on load balancer where it's not working, or on other instance where it is still working while it actually shouldn't. Hit F12 in your browser and see if you have any errors. If so, try to figure out where the error originates from. Alternatively, create a new version of your app and try to do a full deployment instead of an incremental deployment, and then see where things stand with your app.