I am using Weblogic 10.3.I created a managed server along with machine.It is running well.
I try to deploy the application in weblogic I deployed which points to running managed Server but the deployment gets fails.
I am getting error has "" org/antlr/runtime/RecognitionException "".
Please help me to resolve this issue.
Thanks in advance.
Related
i'm currently maintaining a struts / spring java webapp running on weblogic 10.3.6 . I use eclipse neon for development, gradle 2.14 and git to do so.
Our customer wants to incorporate weblogic's clustering features so i'm trying to get my head around that.
I managed to set up a cluster with two servers and to deploy the application to it via weblogic administration console.
Now i'm trying to access the cluster in eclipse but it is not visible as a target. I tried restarting weblogic and re-adding the server.
In Oracle's tutorial there is no hint on what else i should configure on either side: http://www.oracle.com/webfolder/technetwork/tutorials/obe/cloud/javaservice/JCS/eclipse_jcs/eclipse_jcs.html#section2
Has any of you seen such behavior ? What else could i do ?
Thanks in advance for any hint !
Somehow, magically, all of a sudden all clusters appeared in eclipse server list... Probably after one or two restarts of weblogic...
I developed a web application using spring version 3.2.6 and as long as I am deploying it on my tomcat server everything works fine.
Now, if I try to deploy this same application on a weblogic application server I get the following:
java.lang.IncompatibleClassChangeError: org/objectweb/asm/AnnotationVisitor
I think it is related to the spring version installed on the remote weblogic server.
I know I can force the server to use my classes by the following directive in the configuration xml:
<prefer-application-packages>
<package-name>
what do I put here?
</package-name>
Anyway I really don't know what to set there...can you help me out?
Generally IncompatibleClassChangeError means that you have code changes without a recompile.
Use:
<wls:prefer-application-packages>
<wls:package-name>org.springframework.*</wls:package-name>
</wls:prefer-application-packages>
Or prefer-web-inf-classes
This will force weblogic to use the jar packaged in your app. If it still doesn't work, you have a separate issue.
Also check this link about JRF versions
Hi I Want to deploy two copies of same java web application over Weblogic Application Server with some little changes.but i am not getting how to deploy two war file of application over server,and use it simaltaneously..plz help me out..
thanks in advance..
you have to use different context-root in weblogic.xml
Please see
I have a java application which I was running using tomcat server. Now I need to run the same application in jboss server.I am new to jboss, I tried deploying war file in jboss but not able to do so.
I don't know what changes needs to be done for application to run on jboss.
Any one please guide me.
Thank you.
An obvious answer would be Read The Friendly Manual.
You can configure JBoss to autodeploy files in the standalone/deployed/ directory for example, you can also use the maven-jboss7 plugin to handle deployment from maven.
I'm sure the jboss community forums have plenty of examples.
When I deploy my WAR generated with Ant on my local system (copy/paste under /webapps), everything works fine.
The thing is, when I deploy the WAR on a remote server for test purposes, I got this error message:
There was an error thrown by Tomcat during deployment: "Error invoking method check". This however may not mean that you application failed to deploy. Please check the status in the application list
But the application is not deployed at all.
I have to use Probe (lambaprobe.org) to manage and deploy applications on Tomcat on the remote server I'm talking. And I don't have access to the filesystem, only probe.
Any idea would be much appreciated!
Thanks
I often encountered this problem and after checking the log this was caused by an OutOfMemoryError with tomcat
Impossible to check the log... We managed to restart tomcat and it works now.
Weird.
Thank you anyway!
Check the log files of tomcat; they contain the full error message.
If you can't access them easily, write a small webapp which allows you to browse and/or download the logs and deploy that.