I am have to develop an application based on Spring AOP that adds trace Id and loggers to existing application in live production.
The new aop application needs to be packaged onto jars and is to be deployed on code in production. But the production code is running on weblogic server and I don't have option to stop the already running weblogic servers.
Can any body help or give me the clue on how to introduce this new jar to the running application on weblogic.
Thanks in advance.
It's a bit late , but i found this question while searching for the same thing.
The nostage mode can help you with this,I tried it for JSP's and it works great , not sure about the jars though
These links are useful , they might help --
http://docs.oracle.com/cd/E11035_01/wls100/deployment/deploy.html#wp1024366
How do I refresh jsp's on weblogic
Related
I have created a war application and it was tested both in weblogic 12c and Jboss EAP 6.2 successfully.
I changed application server, i moved to JBoss EAP 6.3 and the application could not work properly. Suddenly Jboss stopped to serve any requests and the existing requests were waiting for ever.
I have started Jboss in debug mode from netbeans and i run my application in debug mode.
I have noticed that every time the server was stopping at the System.out.println(); command.
After server's crush/stuck, i interrupt the last thread which was at the log file and upon the interruption i see at the netbean's debugging console a notice:"stopped at AppenderSkeleton.java:231" The previous call at the code is a the line that calls system.out.println.
When i removed all the system.out.println from my code and i left only my log4j the application did not stuck again. I am still testing because i don't know for sure if this is the problem.
Does anyone else had the same problem? When the System.out.println was called one a time it seems that there is no problem, but when this method is called from multiple methods then it seems to stuck.
You probably use a custom log4j configuration in your deployment. It requires a special care as explained by the JBoss logging developer James Perkins in this JBoss forum comment.
Your problem could be related to changes between EAP 6.2 and EAP 6.3 introduced by following bugfix:
Bugzilla: System.out.println() doesn't work when using per-deployment logging
Other users experience similar issue as described in
Bugzilla: ConsoleAppenders can deadlock if included in application log4j configs
If you have some additional info, feel free to comment on existing bugzillas or create a new one where you describe your application (mainly logging) configuration.
I couldn't find an answer to this in any other questions and I wanted to see if anyone knew. I'm using JBoss AS 7.1 on Kepler eclipse, and I was wondering if there is a way to change your standalone.xml while the server is running and have Jboss push the change. Would just cleaning the server do this?
You can't edit the raw XML files and see runtime changes. In fact there is a good chance any changes will be overwritten by the server.
The best way to make runtime changes is either via the web console or the CLI environment. I don't know if JBoss Tools has any kind of CLI type of client that can be used.
What is the best strategy to deploy the latest build to the AppHarbor live site without users seeing any error while the deployment is in progress. Worker process will always be restarted when you deploy a fresh build though. What is the recommended strategy here.
How does StackOverflow deploy builds or bug-fixes to the live site.
If you're currently getting errors when deploying new versions using AppHarbor, then please get in touch so that we can take a look.
Worker restarts should not cause errors as such, just some initial slowness for the first users accessing the site after a deploy. We're also working on hot-swaps so that we only switch over to the new version once the workers are all warmed up and running.
(3/15/2010) Hi
I am trying to test web services using axis2-1.5.1 (latest version) alone without Tomcat.
Is it possible? If so, can someone point me how to do that?
Appreciate your time and help.
You need to have a web server at any way to test a web application. If you want to ease the development, testing and mocking, consider using an embedded server like Eclipse Jetty. You can configure/execute it programmatically.
Sorry for my ignorance here, but when I hear the word webserver, I immediately imagine Apache, although I know people use Microsoft's IIS too. However since I've been hanging out here at Stackoverflow I've noticed lots of people use Glassfish.
Which made me wonder, why would I want to use Glassfish (in the sense that I'm interested, but I don't really understand why it might make my life easier). From what I read it's Sun's open-source derivate of Apache's Tomcat, thus I imagine it's a good (or great) quality product. But since I don't know its strengths and weaknesses, I don't know when it would be wise to choose Glassfish over another server. Could anyone elaborate ?
GlassFish is an Application Server which can also be used as a Web Server (Http Server).
A web Server means: Handling HTTP requests (usually from browsers).
A Servlet Container (e.g. Tomcat) means: It can handle servlets & JSP.
An Application Server (e.g. GlassFish) means: It can manage Java EE applications (usually both servlet/JSP and EJBs).
You should use GlassFish for Java EE enterprise applications.
The need for a seperate Web server is mostly needed in a production environment. You would normally find a Application server to be suffice most of your development needs. A web server is capable of holding larger number of active sessions and connections, thus providing the necessary balance without performance costs.
Stick to a simple web server if you are only working with servlets/jsps. It is also to be noted that in a netbeans environment, glassfish has better support than other App servers. In the context of eclipse though, WSAD and JBoss seem to the preferred options.
Glassfish will soon release the modular kernel.
This means that the containers you need start up and shutdown as you need them. I.e no EAR deployed, EJB container won;t start up. This seems to have made it very good for development as it can start and stop very quickly. This takes it a lot closer to development environments like Rails (where redeployment is a massive part of your development)
I have used GlassFish server for developing Web Services.
It provides a very interactive Admin Console where admin can test the Web Services.
I really find it helpful while developing Web Services