Deployment in WebLogic - quick question

Hi All
We have 2 web apps deployed to our standalone WLS.
Each UI project has a different context root.
However for unclear reason, both web apps cannot be run at the same time.
Is there a setting in JDEV that's used by the 2 web apps that causing this issue (both apps cant run at the same time) ?
Like UI project id in JDev ?
We believe there's a string in the JDev setting that's used by both applications to create their own respective ear files.
Tnak

Hi Frank
thanks for the response.
Each app has its own ear.
Standalone WLS couldnt start - 10.3.6
I wish I had noted down the error - but the pressure to get work done first - I left the error, spending time to find workaround as my priority then.

Similar Messages

Estimate ADF web app use size in Weblogic - quick question

Hi
1- Is there a good way to estimate or get a better accurate measurement of the amount of memory required/used by a running ADF app within Weblogic Server ?
Eg How much memory footprint does a deployed ADF app uses (not including those apps that comes with weblogic installs in the deployment section of WLS UI) ?
2- Because we have ADF as a web app, is there a usually a big increase in memory usages of ADF web app when more people are logged in ?
Any memory tool as a quick way to get the memory sizes ?
Thanks

AFAIK,You need to first calculate the live data size for your application with the help of the GC logs to find out the ideal memory for your app to run :)
You can enable the GC logs -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -Xloggc:<Filename> to find out the live data size for your application
Tools to monitor the applications:
JConsole/VisualVM/JRMC
http://docs.oracle.com/javase/6/docs/technotes/guides/visualvm/index.html

Application Logging in Standalone weblogic - quick questions

Hi
In JDeveloper, we could write our application logging to logs for debugging and viewable from JDeveloper.
When we deploy to Standalone weblogic server, we cant find our logging.
Of the 3 loggers (Msg Catalog, nonCatalog, Commons log API),
Which logging mechanism is the best practice used logging for development environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
Which logging mechanism is the best practice used logging for production environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
Thanks

hi,
people commonly Log4J for their logging,Like Commons Logging, SLF4J, or the default Java Logging API. But if you're working with Oracle's Application Development Framework, there is another option as well: ADF Logging.
ADF Logging is a logging mechanism, embedded in the ADF framework. It wraps the Java Logging API, but throws in a few extra methods and some JDeveloper and (Weblogic) Enterprise Manager features.
the following one demo video from oracle site its very useful.
http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/ADF_Insider_Essentials/debug_part1/debug_part1.html
regards
siva

How to host html files on Weblogic - quick question

Hi All
We have an ADF web app already running with WLS.
We have another static html app to host on this WLS. (as a web server)
1- how do we deploy from Hudson to the standalone WLS for the static html web app (step-by-step simple process we need)
2- how to host this static html app (step-by-step simple process we need)
Thanks
Edited by: 898644 on Sep 13, 2012 4:02 PM

this is what it say.
Transfers the specified deployment files, including deployment plans and alternate deployment descriptors, to the Administration Server. Use this option when you are on a remote machine and you cannot copy the deployment files to the Administration Server by other means. The application files are uploaded to the WebLogic Server Administration Server's upload directory prior to distribution and deployment.
Regards,
kal

Deploy war file - quick question

Hi
using weblogic.Deployer, is that deployment command line options for deploying a war file the same as deploying an ear file ?
Will it deploy to the remote directory WLS of upload directory ?
Thanks

Hi,
using weblogic.Deployer, is that deployment command line options for deploying a war file the same as deploying an ear file ?Yes,
Example
java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password weblogic123 -deploy -name Fabian_Ear -appversion VesionA -targets <Managed_Server_name> -source /apps/Original/Fabian.ear
More details about Weblogic.deployer can be found under below link
http://docs.oracle.com/cd/E13222_01/wls/docs90/deployment/wldeployer.html
Regards
Fabian

Workshop Weblogic config questions

I'm using Oracle Workshop for WebLogic 10.3 and I'm hoping someone can answer some setup/config questions.
When I double click on the server (WebLogic Server v10.3 at localhost) a window opens with various settings that manage how workshop and weblogic work together.
Under "Startup & Deployment" I have the following turned on:
Launch WebLogic server in Eclipse console
Always start WebLogic Server in debug mode
Ignore project compilation errors when publishing (I have this turned on because of errors in a portal project, the errors aren't inmportant, and don't prevent the project form running)
Run stand-alone web module directly from workspace
So, first question, with these settings I was able to quickly switch to debug mode, with out restarting the server, now the server restarts whenever I turn debugging on. What have I done that has stopped this working correctly? How can I get it to start debugging without a full restart?
next question, what happens if I turn on "Start WebLogic Server in Express Mode"? As far as I can tell nothing happens.
Lastly, under "Automatic Publishing" I have it set to "Never publish automatically", if I choose another setting workshop essentially freezes because it's constantly publishing. So whenever I make a change, even in a jsp, I need to remove the project, then re-add it to see my changes in the browser. This is frustrating, not just because it takes 8 or 9 minutes (8 or 9 MINUTES!!!), but because the project doesn't run properly until it is redeployed. You'd think that if it needs to be re-deployed, then none of my changes should matter on the server until it is re-deployed.
So, my question is, Is there any way to get this re-deployment to happen faster?
Thanks for any and all help

Well, in my experience performance is not bad as you experienced. Is it locally connected server or remotely connected server? If it is a remote server, network issue could cause this latency issue.
Is performance better if you run the server without enabling debug mode? If yes, probably you can also review any break points set.
You could also try out the following options
1) Run workshop with -clean option, by opening command prompt and navigating to workshop_home\'workshop.exe -clean'
2) Untick the option 'Launch WebLogic server in Eclipse console' and start server which would enable server to start on command prompt
3) This would enable you to take multiple thread dumps (cutl +Break) on the server console output, while performance is very bad, to see where threads are halt.

Jdeveloper WS proxy error while invoking web service deployed on weblogic

Hello experts, can you please help me. I have web service deployed on weblogic server.
I have not set any credential for this web service. I can test the service from SOAPUI without providing any credentials.
Then I generated WS proxy client using Jdeveloper. When I try to run the client, I do not know why I get security execption (shown below) eventhough I have not secured the web service deployed on weblogic server.
java.lang.SecurityException: keyStoreFilename is either null or empty string
     at weblogic.wsee.security.util.CertUtils.getCertificate(CertUtils.java:87)
     at pilot1.ContactWSPortTypePortClient.getBSTCredentialProvider(ContactWSPortTypePortClient.java:104)
     at pilot1.ContactWSPortTypePortClient.setPortCredentialProviderList(ContactWSPortTypePortClient.java:78)
     at pilot1.ContactWSPortTypePortClient.main(ContactWSPortTypePortClient.java:46)
Process exited with exit code 0.
Here is my client class :
public static void main(String[] args) {
try {
contactWSService = new ContactWSService();
ContactWSPortType contactWSPortType = contactWSService.getContactWSPortTypePort();
Map<String, Object> requestContext = ((BindingProvider) contactWSPortType).getRequestContext();
setPortCredentialProviderList(requestContext);
// Add your code to call the desired methods.
// QueryPageInputSecondPage qpisp= new QueryPageInputSecondPage(); //I have commented it in order to resolve security issue
System.out.println("Inside the client class");
} catch (Exception ex) {
ex.printStackTrace();
Inside the method setPortCredentialProviderList(), I have not provided any credentials, keystores etc. Because weblogic is not setup with SSL and also I have not set up any authorization or authentication for the web service. I do not know why I am able to test it through SOAPUI and why not using WS proxy.
Appreciate your quick response.
thanks a lot
jyothi

Hello experts, can you please help me. I have web service deployed on weblogic server.
I have not set any credential for this web service. I can test the service from SOAPUI without providing any credentials.
Then I generated WS proxy client using Jdeveloper. When I try to run the client, I do not know why I get security execption (shown below) eventhough I have not secured the web service deployed on weblogic server.
java.lang.SecurityException: keyStoreFilename is either null or empty string
     at weblogic.wsee.security.util.CertUtils.getCertificate(CertUtils.java:87)
     at pilot1.ContactWSPortTypePortClient.getBSTCredentialProvider(ContactWSPortTypePortClient.java:104)
     at pilot1.ContactWSPortTypePortClient.setPortCredentialProviderList(ContactWSPortTypePortClient.java:78)
     at pilot1.ContactWSPortTypePortClient.main(ContactWSPortTypePortClient.java:46)
Process exited with exit code 0.
Here is my client class :
public static void main(String[] args) {
try {
contactWSService = new ContactWSService();
ContactWSPortType contactWSPortType = contactWSService.getContactWSPortTypePort();
Map<String, Object> requestContext = ((BindingProvider) contactWSPortType).getRequestContext();
setPortCredentialProviderList(requestContext);
// Add your code to call the desired methods.
// QueryPageInputSecondPage qpisp= new QueryPageInputSecondPage(); //I have commented it in order to resolve security issue
System.out.println("Inside the client class");
} catch (Exception ex) {
ex.printStackTrace();
Inside the method setPortCredentialProviderList(), I have not provided any credentials, keystores etc. Because weblogic is not setup with SSL and also I have not set up any authorization or authentication for the web service. I do not know why I am able to test it through SOAPUI and why not using WS proxy.
Appreciate your quick response.
thanks a lot
jyothi

Deployment descriptor "weblogic.xml" is malformed. in managed server

Hi All,
          Appreciate if anyone can help.
          I have set up a cluster containing two nodes - one local and other
          remote machine on weblogic 8.1.4
          then i install my application this cluster setup its working fine.
          for my requirement i upgrade the the weblogic version from 8.1.4 to
          8.1.6 .
          i upgrade through the smart update from the bea site . i upgraded both
          the node.
          i started the admin server.it started with no issue.
          my problem comes when i start the my managed server on the cluster .it
          gives me this exception.
          <HTTP> <BEA-101296> <Unable to load the default compiler class
          "com.sun.tools.javac.Main". Using the default javac compiler to compile
          JSPs.>
          i checked the classpath it has the same jdk that i used for 8.1.4
          (jdk1.4.05 from sun.)
          should i used new jdk that comes with the upgrade package of 8.1.6 like
          (jdk1.4.11)
          my class path having the weblogic jar also.
          this is my class path.:
          E:\bea\weblogic81\server\lib\weblogic.jar and other my application
          jars.
          complete exception it is shown like :
          <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
          <Application:
          'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
          Module: 'Nexaweb': Public ID references the old version of the Servlet
          DTD. You must change the public ID in web.xml file to "-//Sun
          Microsystems, Inc.//DTD Web Application 2.3//EN".>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
          <[Application:
          'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?br>Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
          Check against the DTD: org.xml.sax.SAXParseException: The content of
          element type "weblogic-web-app" must match
          "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?t*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?ontainer-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?ap?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
          (line 26, column 20).>
          Compiler class: 'com.sun.tools.javac.Main', not found
          java.lang.ClassNotFoundException: com.sun.tools.javac.Main
          at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
          at java.security.AccessController.doPrivileged(Native Method)
          at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
          at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
          at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
          at java.lang.Class.forName0(Native Method)
          at java.lang.Class.forName(Class.java:141)
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?6)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
          <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
          will have better performance if it is enabled. To enable
          call-by-reference, set the enable-call-by-reference element to True in
          the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
          <Failed to initialize the application Xellerate due to error
          weblogic.management.ApplicationException: prepare failed for
          xlBackOfficeBeans.jar
          Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
          EJBModule(xlBackOfficeBeans.jar,status=NEW)
          Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
          Compiler class: 'com.sun.tools.javac.Main', not found
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
          found
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          weblogic.management.ApplicationException: prepare failed for
          xlBackOfficeBeans.jar
          Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
          EJBModule(xlBackOfficeBeans.jar,status=NEW)
          Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
          Compiler class: 'com.sun.tools.javac.Main', not found
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
          found
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1658)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          ><Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
          <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
          to initialize due to failed deployments.>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
          <The deployment framework was unable to resume accepting requests.>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
          <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
          deployment framework was unable to resume accepting
          requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
          is unable to initialize due to failed deployments.>
          hope the scope of the questions is not too broad. Kindly let me know
          if you need more information.
          Thanks a lot.

ram ram <> wrote:
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
Add tools.jar from your Java installation to the classpath.
Bart
Schelstraete Bart
http://www.schelstraete.org
http://www.mqseries.be

Implementing X509 installed in web server for service deployed in weblogic

I need some advise on what I am doing is the right way of implementing one way x509 certificate.
1.JWS file is created using wsdlc ant task and deployed in weblogic 10.3.0 with no security policy annotations.
2.Installed Verisign certificate in Sun One Java server and enabled SSL and added some configurations to redirect webservices request to weblogic server
3.Created client and added -Djavax.net.debug=all as VM argument and verified the Sun One Java server verisign certificate details in the logs.
So far there is no issue but today I was reading about security policy file and I don’t know whether I am missing that in the webservice class or not. But because I can verify the certificate data from webserver I am thinking x509 certificate is installed and my webservice is using that certificate. Am I right?
Can someone point out if I am missing something and let me know the details on the same? Thanks

I meant @Policy(uri = "policy:Wssp1.2-2007-Https.xml") Also I read this article which is talking about the policy file http://chrismuir.sys-con.com/node/1075471/mobile
Couple of questions:
1. As I said in my last thread, since Verisign certificate is installed in the web server, I can view the certificate details in the browser for any https requests to that server instead of just for this webservice request. How to block/filter other requests from using the certificate when involed using https?
2. When do we need policy files?
Edited by: user8115570 on Feb 6, 2012 2:55 PM

Calling EJB deployed on Weblogic 10.3 from WebSphere Application Server 6

Hi,
We are trying to call an EJB(2.1) deployed in Weblogic 10.3 from WebSphere Application Server 6.
The problem is that the jars containing Weblogic's initial context factory are compiled with JDK5. (Client jar was built as per [http://download.oracle.com/docs/cd/E15051_01/wls/docs103/client/jarbuilder.html] .)
WebSphere is still running on JDK1.4.
Therefore when trying to get the InitialContext to lookup up the bean we get major/minor version errors because of the compiler level mismatch.
Has anyone faced a scenario like this and come up with a solution?
Are there 1.4 jars for Weblogic 10.3 out there?
Any help?
Thanks

Hi Dan,
Yes I am using EJB 3. I saw this thread earlier also but :
1. In my case I am not calling the EJB 3.0 methods directly. I am using a java client (Cataloged as a Java Class Library) which does the lookup and calls the EJB methods. (I am not cataloging and calling the EJB 3.0 methods directly).
2. It is working perfectly fine when the EJB is deployed in Weblogic 10.0 or 10.2.
I am very much new to this so please bear with my small and silly questions! Thanks a lot for you help !
Cheers !
Rajat

Mbeans not visibel when deployed to weblogic

I am getting started with jmx I am using spring jmx server , I tried deploying in jetty and used jconsole I could see all my mbenas , when deployed to weblogic none of my mbeans are visible , do I need to do anything more ?
please advice me .

Hi Timo,
Thanks for your quick reaction. deleting the application first solved my issue.
I never had this issue before, but good to know how to fix it :)

Deployment descriptor "weblogic.xml" is malformed.

Hi All,
Appreciate if anyone can help.
I have set up a cluster containing two nodes - one local and other
remote machine on weblogic 8.1.4
then i install my application this cluster setup its working fine.
for my requirement i upgrade the the weblogic version from 8.1.4 to
8.1.6 .
i upgrade through the smart update from the bea site . i upgraded both
the node.
i started the admin server.it started with no issue.
my problem comes when i start the my managed server on the cluster .it
gives me this exception.
<HTTP> <BEA-101296> <Unable to load the default compiler class
"com.sun.tools.javac.Main". Using the default javac compiler to compile
JSPs.>
i checked the classpath it has the same jdk that i used for 8.1.4
(jdk1.4.05 from sun.)
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
complete exception it is shown like :
<Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
<Application:
'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
Module: 'Nexaweb': Public ID references the old version of the Servlet
DTD. You must change the public ID in web.xml file to "-//Sun
Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
<[Application:
'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?r',
Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
Check against the DTD: org.xml.sax.SAXParseException: The content of
element type "weblogic-web-app" must match
"(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?gnment*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?er?,container-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?tch-map?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?oot?,wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
(line 26, column 20).>
Compiler class: 'com.sun.tools.javac.Main', not found
java.lang.ClassNotFoundException: com.sun.tools.javac.Main
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:406)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
<Call-by-reference is not enabled for the EJB 'JMSBean'. The server
will have better performance if it is enabled. To enable
call-by-reference, set the enable-call-by-reference element to True in
the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
<Failed to initialize the application Xellerate due to error
weblogic.management.ApplicationException: prepare failed for
xlBackOfficeBeans.jar
Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
EJBModule(xlBackOfficeBeans.jar,status=NEW)
Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
Compiler class: 'com.sun.tools.javac.Main', not found
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
found
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for
xlBackOfficeBeans.jar
Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
EJBModule(xlBackOfficeBeans.jar,status=NEW)
Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
Compiler class: 'com.sun.tools.javac.Main', not found
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
found
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1658)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
<BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
to initialize due to failed deployments.>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
<The deployment framework was unable to resume accepting requests.>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
<BEA-000342> <Unable to initialize the server: [Deployer:149601]The
deployment framework was unable to resume accepting
requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
is unable to initialize due to failed deployments.>
hope the scope of the questions is not too broad. Kindly let me know
if you need more information.
Thanks a lot.

ram ram <> wrote:
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
Add tools.jar from your Java installation to the classpath.
Bart
Schelstraete Bart
http://www.schelstraete.org
http://www.mqseries.be

Quick Question **PLEASE HELP** .jar file?

Hey everyone, im pretty new to the java scene but I have a really quick question that hopefully someone can help me with.
I'm really interested in making a .jar file out of my code. And basically I just want to make one. but i understand there are certain things like main class's, etc. that need to be made in order to make a .jar file.
So basically Say I opened up a new project in blueJ. I made 1 new class called "main." Inside of it I had nothing for conductors and no variables declaired untill the bottom part where i write my code.
say i write...
System.out.println("hello");
and that is it.
What steps from there do i do to make a jar file and have it be able to be executed and SEE the "hello" printed somewhere NOT in blueJ??
(I understand there is something about a "static" method? Im not really sure but if somoene could enlighten me on how to make a .jar file that would be great.)
Thanks a lot everyone!
Tom

I don't know anything about BlueJ, but this section of Sun's tutorial explains how to
write a program that outputs a single line of text to the console:
http://java.sun.com/docs/books/tutorial/getStarted/cupojava/win32.html
Deploying an application as an executable .jar file is covered here:
http://java.sun.com/docs/books/tutorial/deployment/jar/index.html
The first two sections - "Using JAR Files: The Basics" and "Working with Manifest
Files: The Basics" - contain the information you need to understand this process.

Unable to deploy to weblogic server

I had created an hello world bpel process and it was build successful but the deployment to weblogic server was incomplete,
Environment : 11.1.1.5.0 soa suite,11.1.1.5.0 Jdeveloper, 10.3.5 WLS
I had configured admin and soa in a single server(developer mode)
Deployment log was
[02:35:18 PM] Problem in sending HTTP request to the server. Please make sure the server is up and/or check standard HTTP response code for 504
[02:35:18 PM] Error deploying archive sca_HelloWorld_rev1.0.jar to partition "default" on server AdminServer [http://SMD-0890.kpt.com:7001]
[02:35:18 PM] HTTP error code returned [504]
[02:35:18 PM] No error message is returned from the server.
[02:35:18 PM] Error deploying archive sca_HelloWorld_rev1.0.jar to partition "default" on server AdminServer [http://SMD-0890.kpt.com:7001]
[02:35:18 PM] #### Deployment incomplete. ####
[02:35:18 PM] Error deploying archive file:/C:/JDeveloper/mywork/HelloWorld/HelloWorld/deploy/sca_HelloWorld_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)

Thanks fro the quick reply, i am deploying using jdeveloper,
I had selected the check box 'Overwrite any existing composites with the same revision ID' but the same error occurs,
[03:29:46 PM] ---- Deployment started. ----
[03:29:46 PM] Target platform is (Weblogic 10.3).
[03:29:46 PM] Running dependency analysis...
[03:29:46 PM] Building...
[03:29:51 PM] Deploying profile...
[03:29:51 PM] Updating revision id for the SOA Project 'HelloWorld.jpr' to '1.0'..
[03:29:51 PM] Wrote Archive Module to C:\JDeveloper\mywork\HelloWorld\HelloWorld\deploy\sca_HelloWorld_rev1.0.jar
[03:29:51 PM] Deploying sca_HelloWorld_rev1.0.jar to partition "default" on server AdminServer [http://SMD-0890.kpt.com:7001]
[03:29:51 PM] Processing sar=/C:/JDeveloper/mywork/HelloWorld/HelloWorld/deploy/sca_HelloWorld_rev1.0.jar
[03:29:51 PM] Adding sar file - C:\JDeveloper\mywork\HelloWorld\HelloWorld\deploy\sca_HelloWorld_rev1.0.jar
[03:29:51 PM] Preparing to send HTTP request for deployment
[03:29:51 PM] Creating HTTP connection to host:SMD-0890.kpt.com, port:7001
[03:29:51 PM] Sending internal deployment descriptor
[03:29:51 PM] Sending archive - sca_HelloWorld_rev1.0.jar
[03:29:51 PM] Received HTTP response from the server, response code=504
[03:29:51 PM] Problem in sending HTTP request to the server. Please make sure the server is up and/or check standard HTTP response code for 504
[03:29:51 PM] Error deploying archive sca_HelloWorld_rev1.0.jar to partition "default" on server AdminServer [http://SMD-0890.kpt.com:7001]
[03:29:51 PM] HTTP error code returned [504]
[03:29:51 PM] No error message is returned from the server.
[03:29:51 PM] Error deploying archive sca_HelloWorld_rev1.0.jar to partition "default" on server AdminServer [http://SMD-0890.kpt.com:7001]
[03:29:51 PM] #### Deployment incomplete. ####
[03:29:51 PM] Error deploying archive file:/C:/JDeveloper/mywork/HelloWorld/HelloWorld/deploy/sca_HelloWorld_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)

What are the application can able to deploy in Weblogic

What are the application can able to deploy in Weblogic Server ?
We have one desktop application which developed by .net and its database in SQL Server.
My Question is
Is it Possible to Deploy this application in Weblogic Server ?
Or kindly advice me what technologies can helpful for me to access via PDA
Thanks in Advance
Hameed
Edited by: Hameed on Mar 10, 2013 12:44 AM

User, this question is better asked on the {forum:id=570} forum.
This more depends on the specification of your app and has nothing to do with jdev or adf.
Timo

Deployment in WebLogic - quick question

Similar Messages

Maybe you are looking for