ICEfaces WebMC running on WLS 10.0

Did anyone succeed to deploy the open source WebMC on WLS 10.0?
http://www.icefaces.org/main/community/projects-webmc.iface
I was able to compiled the src code and run it on Tomcat 6, but there were error while running on WLS 10.0:
- it did not work if the war file contain xercesImpl.jar and xml-apis.jar
- removing these files then the main UI showed but when logging as moderator and upload a new presentation zip file did not work. The upload button just do nothing, no error occurred in the log file.
But I was able to run the showcase sample from ICEfaces 1.6.1distribution on WLS 10.0, so library conflict should not be the reason.
Thanks in advance for any suggestion how to deploy it on WLS 10.0

I struggled with the same problem for weeks and found that a very likely solution was running <wlst> from within ant.
We got this problem when our deploy scripts changed from shell scripts (windows cmd files) into a single ant script where wlst was called repeatedly using the <wlst>supplied target.
Our scripts are used to create the domain and all resources from scratch and invokes wlst several times during the process.
When the ant script was changed into <exec> .. where wlst was invoked in a forked process, the problem disappeared.
I would think that the problem is wlst ant target not performing a proper cleanup.
Or, if you have another external jvm that opens an rjvm connection to the server, you might want to turn this program off during domain creation and configuration.
Hope this helps
Niels Gylling, IT Practice

Similar Messages

Getting PetStore to run in WLS 6.1sp3 on Mac OS X 10.2.6?

Hi all!
I've read with great interest all the articles relating to WLS running on OS X.
It's great to read this as I am pretty much the only guy in the entire organisation
here trying to keep using his Mac.
I was able to get WLS admin server to run on my PowerBook running OS X 10.2.6.
However, after stopping the admin server and trying to start the PetStore demo
server, I've got a few exceptions that prevent the server from starting.
So, I was wondering how you people, running WLS 6.1 on OS X have configured your
start scripts. When trying to use the standard jdk that comes with WLS, I'm getting
an exception. When using the Apple 1.3.1 jdk, I'm getting another exception about
a missing 'libmuxer' library. Basically, what set of libraries are you using?
Thanks in advance!
-Laurent.

Thanks for the reply, Mark. I finally figured it out by replacing all references
to the WebLogic provided 1.3.1 jdk by the one provided by Apple and all is well
now!
Thanks!
-Laurent.
"Mark Griffith" <[email protected]> wrote:
All you should need (with 7.0 and 8.1) to start WLS is
"java weblogic.Server"
As long as your have your classpath set.
export CLASSPATH=$WLHOME:$WLHOME/server/lib/weblogic.jar
On my windoze box WLHOME=C:/bea/wls81/weblogic81
Libmuxer is our native socket muxing code, you don't need it to run you'll
just use java muxing.
Sam just posted the libs on another thread.
Any other exceptions?
cheers
mbg
"Laurent Daudelin" <[email protected]> wrote in message
news:3eccefbe$[email protected]..
Hi all!
I've read with great interest all the articles relating to WLS runningon
OS X.
It's great to read this as I am pretty much the only guy in the entireorganisation
here trying to keep using his Mac.
I was able to get WLS admin server to run on my PowerBook running OSX
10.2.6.
However, after stopping the admin server and trying to start the PetStoredemo
server, I've got a few exceptions that prevent the server from starting.
So, I was wondering how you people, running WLS 6.1 on OS X haveconfigured your
start scripts. When trying to use the standard jdk that comes withWLS,
I'm getting
an exception. When using the Apple 1.3.1 jdk, I'm getting anotherexception about
a missing 'libmuxer' library. Basically, what set of libraries areyou
using?
Thanks in advance!
-Laurent.

Trying to run code to talk to OIM9102 running on WLS 10.3

Hello OIM Experts,
I have a setup where I can communication with OIM 9.1 on Jboss using some some sample API with no issues when I try to replicate the similar setup to OIM 9102 on WLS I have the following error from my jdev console nothing shows up in the wls access.log
Thor.API.Exceptions.tcUserAccountInvalidException
at Thor.API.tcUtilityFactory.createLoginException(Unknown Source)
at Thor.API.tcUtilityFactory.<init>(Unknown Source)
at com.customer.oim.test.provision.ProvisionManagerTester.setUp(ProvisionManagerTester.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Although the account is valid when logging in through OIM GUI, so why would i get this error when running it through code....?
The code I am using is the generic one from the OIM API Samples:
ConfigurationClient.ComplexSetting config = ConfigurationClient
.getComplexSettingByPath(Constant.OimSettings.CORE_SERVER);
Hashtable env = config.getAllSettings()
ioUtilityFactory = new tcUtilityFactory(env, "xelsysadm", "xelsysadm"); - line 70
I have made sure of the following arguments and permissions to the xl.policy file. All the correct jar files are loaded as well,
Is there any catch to setting this up specifically for OIM on WLS....?
I have seen the online documentation, but if someone could share samples and more detailed documentation that would be great, thanks
Regards,

Hi,
Here is my xlconfig.xml
<?xml version="1.0" encoding="utf-8"?>
<xl-configuration>
     
     <appServerName>WebLogic</appServerName>
     
     <ApplicationURL>http://localhost:7001/xlWebApp/loginWorkflowRenderer.do</ApplicationURL>

<Discovery>
          <CoreServer>
               <java.naming.provider.url>t3://host:7001</java.naming.provider.url>
               <java.naming.factory.initial>weblogic.jndi.WLInitialContextFactory</java.naming.factory.initial>
          </CoreServer>
</Discovery>

<Cache>
     <XLCacheProvider>
               <MultiCastAddress>231.121.212.133</MultiCastAddress>
          </XLCacheProvider>
     </Cache>
</xl-configuration>
Regards,

WebLogic Server 9.2.2 & running WLS 9.1 generated WLST config.py

Hello everybody,
I am running a WLS 9.1 WLST ConfigToScript config.py in a blank new WLS 9.2 installation to recreate a WLS Server domain.
The original script generated reflects the Administration Server residing on one machine while the Application Server, applications, and node manager reside on another machine. I've edited the script for the new target machine. In this case they want to everything to reside in a single Solaris 10 Zone. The Administration Server resides on one virtual IP address while the nodemanger, application server, and applications all reside on another virtual IP address. Both these addresses are defined in the zone, which has it's own IP address in which WLS 9.2 is installed.
When the script runs it tries to connect to the Administration Server I've defined and when it fails to connect it proceeds to create a brand new administration server. This proceeds as expected and finally when WLST attempts to connect to the now running Administration Server I get the following errors:
WLST-WLS-1207767457017: <Apr 9, 2008 2:58:49 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
WLST-WLS-1207767457017: <Apr 9, 2008 2:58:49 PM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Server started successfully.
Started Server. Trying to connect to the server ...
Connecting to t3://10.99.99.99:8082 with userid system ...
WLST-WLS-1207767457017: Exception in thread "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
WLST-WLS-1207767457017: Exception in thread "Timer-1" java.lang.OutOfMemoryError: PermGen space
WLST-WLS-1207767457017: Exception in thread "[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
I've tried adding "-XX:MaxPermSize=256m" when I invoke java to run WLST but of course after I got the error again I realized that it is the newly created WLS Administration Server that is getting this error.
I would have thought the WLST configToScript would have exported any special JVM flags used by the original Administration Server, nodemangers, and such.
Could you please explain how I fix this?
Do I need to lookup in the original 9.1 environment all of these JVM flags and integrate them somehow in the ConfigToScript config.py script?
Thanks very much.

Try changing the config.py script:
And server for the line "startServer", and there add that MaxPermSize.
For example:
startServer("AdminServer", "Domain", t3://XXXX, "weblogic","weblogic","/opt/BEA/user_projects/domains/Domain", timeout=90000, jvmArgs='-XX:MaxPermSize=256m, -Xms512m, -Xmx512m')
Schelstraete Bart
[email protected]
http://www.schelstraete.org
http://www.linkedin.com/in/bschelst

Change Host Name and IP Address on machine running WLS 9.2

Hello,
I am new to this community, so please forgive any unintended missteps.
I have an installation of BEA WebLogic Server 9.2 running on Windows 2003 Server SP2. This installation is running on a virtual server, which was created using some VMware product that copies or clones production environments. The purpose of this new, cloned environment is to act as a development environment. This new DEV server has a different host name and IP address from the source PROD server.
WLS is not starting up properly. It complains about the license.bea file not being valid. To try to fix that, I manually changed the IP address listed within that file, from that of the original system to that of the current system, but that did not change the error message I get during startup.
I imagine that this instance of WLS needs to be re-licensed to account for the change in IP address. Besides that, are there any other configuration parameters in text files, registry settings, etc., that need to be modified in order to allow the new instance of WLS to work the same as the old instance?
Please note that we want both DEV and PROD to run simultaneously, so we need to take steps to ensure they (and the applications running on WLS) don't talk to each other.
I tried to search the BEA sites and found a few resources, but related to some other products (ALES?), not WLS.
Thoughts, suggestions, feedback, or pointers to documentation would be greatly appreciated.
Thanks,
JPG.

Hi JPG,
The BEA license files are tied to IP address. Editing the license.bea to change the IP address file will not work.
Any reason why you cannot use a 5 user dev license for your environment?
If you break the 5 user limit then use IIS or Apache to front-end the the WLS instance.
Cheers
Mike

Run Reports Builder with a remote WLS

Hi all,
Can somebody know if Oracle Reports Builder 11g can connect with a remote WebLogic 10 server Reports instance?
How can I do that?
Best regards!!!

- not sure what you mean by this .
- builder will not connect to wls. for jsp reports development, it copies jsps to wls jsp deployment folder in same domain and runs (ie jsp runs in the wls container).
- yes, rwclient,rwservlet can connect to remote inprocess servers running in wls and can run reports in those reports servers.

HP-UX Kernel Params for WLS 6.0SP2 Cluster to Avoid java.lang.outofmemory and/or thread death

          I'm running a WLS 6.0 SP2 clustered application on HP-UX 11i. I'm seeing heap and
          thread issues on start-up or invocation of my application as I deploy EJB's and create
          DB connection pools. These are fairly trivial tasks that don't give me any issues
          when starting the first node. It's only when I invoke the second node.
          I'm pretty sure that my issue is tied to the following kernel areas:
          1. Thread allocation
          2. Heap allocation
          3. Max Processes per user
          Can anyone make some kernel recommendations that might be beneficial to my deployment?
          My app runs on NT/2000 and Sun as well, and I haven't seen these issues. I typically
          allocate 50 to 100 threads per node (3 nodes on a 4 CPU machine) and allocate about
          1GB of RAM per node on a 4GB machine...
          Regards,
          Steve


I'm running a WLS 6.0 SP2 clustered application on HP-UX 11i. I'm seeing          heap and
          > thread issues on start-up or invocation of my application as I deploy
          EJB's and create
          > DB connection pools. These are fairly trivial tasks that don't give me any
          issues
          > when starting the first node. It's only when I invoke the second node.
          >
          > I'm pretty sure that my issue is tied to the following kernel areas:
          >
          > 1. Thread allocation
          > 2. Heap allocation
          > 3. Max Processes per user
          >
          > Can anyone make some kernel recommendations that might be beneficial to my
          deployment?
          > My app runs on NT/2000 and Sun as well, and I haven't seen these issues. I
          typically
          > allocate 50 to 100 threads per node (3 nodes on a 4 CPU machine) and
          allocate about
          > 1GB of RAM per node on a 4GB machine...
          HP has some kernel tuning guidelines for Java server apps on their web site,
          and BEA has some notes as well in their platform support page.
          What issues specifically are you seeing?
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          Clustering Weblogic? You're either using Coherence, or you should be!
          Download a Tangosol Coherence eval today at http://www.tangosol.com/
          "Steve Feldman" <[email protected]> wrote in message
          news:3cdc046e$[email protected]..
          >

Can't run JDeveloper 11.1.2.1 app on Weblogic 10.3.6

I'm trying to migrate my application developed in JDeveloper 11.1.1.4 (ADF BC, ADF Faces stack) to JDeveloper 11.1.2.1.
This app was previously deployed to Weblogic 10.3.4.
When I generate .ear file and try to deploy it with Enterprise Manger to Weblogic 10.3.6 I keep getting an error that I can't deploy it because in weblogic.xml my app reference library JSF 2.0.
I can see that by default Weblogic 10.3.6 comes with JSF 1.2. If I replace it with jsf 2.0 (from: weblogic_home\wlserver_10.3\common\deployable-libraries\jsf-2.0.war) still can't get it to work. And EM stops working because it depends on JSF 1.2.
I've tried several different approaches (removing all references to JSF 2.0; adding jsf-api.jar, jsf-api.jar directly to project and deploying it with .ear,...) but none has shown right.
What should I do to run ADF application developed with JDeveloper 11.1.2.1 on Weblogic server 10.3.6
Thanks,
Nebojsa

JDev 11.1.2.1 need wls 10.3.5 with sherman patches applied to run. WLS 10.3.6. is for jdev 11.1.1.6.0.
Timo
Edited by: Timo Hahn on 29.03.2012 20:28
Check http://tompeez.wordpress.com/2011/09/14/jdeveloper-versions-vs-weblogic-server-versions/
or https://blogs.oracle.com/onesizedoesntfitall/entry/adf_runtimes_vs_wls_versions
For some note on how to set up wls 10.3.5 for jdev 10.3.5 check http://tompeez.wordpress.com/2011/06/29/follow-up-upgrading-wls-10-3-5-with-adf-runtime-11-1-2-0-0-sherman-patch/

Wls 6.0sp1, xerces 1.1

I'm in the process of upgrading to weblogic 6.0sp1 from 5.1. My app uses
xerces 1.1 for all xml parsing. My original configuration was jbuilder 4.0,
weblogic 5.1, jdk1.2.2 and xerces 1.1. This configuration worked and all
xml parsed fine. After upgrading to wls 6.0 my new configuration is jb4,
wls 6.0, xerces 1.1 and jdk130. In this configuration i always get
exceptions when i call the parse method on DOMParser. I've tried swapping
out jdk's, and using the xerces that is bundled with wls 6.0 but have had no
success. Any help would be much appreciated.
Below are some code snippets to indicate my usage of DOMParser:
import org.apache.xerces.parsers.DOMParser;
import org.apache.xerces.dom.DocumentImpl;
import org.apache.xml.serialize.OutputFormat;
import org.apache.xml.serialize.XMLSerializer;
import org.xml.sax.InputSource;
import org.xml.sax.SAXParseException;
import org.w3c.dom.Document;
public class XMLModel {
try {
String loadXmlFileName = new String("whatever.xml");
if(useDOM) {
// If possible, parse the file
DOMParser parser = new DOMParser();
if (loadXmlFileName != null) {
parser.parse(loadXmlFileName);
Document loadDoc = parser.getDocument();
Document loadDoc = XMLParser.parse(loadXmlFileName);
catch (Exception e) {
Log.writeError(e);
return;
Again...This worked with jdk1.2.2, wls 5.1, xerces 1.1....but does not
with jdk130, wls 6.0, xerces 1.1 (or xerces 1.2 bundled with wls 6).
Thanks for any help.
By the way...the exception i get indicates the file can not be found. But i
create an instance of File and ensure that i can read it before calling
parse on the DOMParser.

Is there any plan to support backward compatibility in future ?
Due to above restriction we have to use lowest common BEA version.
I guess BEA must learn how real world application work. I guess compatability
should be like ORACLE RDBMS.
Thanks
Kumar Allamraju <[email protected]> wrote:
No.
As of 6.0 release, the client & server should be on the same version.
Kumar
Rakesh wrote:
Hello,
Can my client running on WLS 5.1.0.9 can connect/work with applicationdeployed
on WLS 6.0.0.1 ?
Thanks

WLS server upgrading problems from 8.1 to 9.2

We had our application running on WLS 8.1.
Trying to upgrade to 9.2 using teh upgrade.sh script ( which uses 'java weblogic.Upgrade' inside ).
Even after it has reported that it has successfully upgraded the domain, when I login using the admin console, I see that the managed servrs are missing. So are all the resources ( JMS, connectionpool etc ) and all our EJBs.
Essentially we end up with a new admin server with nothing in it.
Has somebody else experienced this problem ?
If yes, are there any work arounds.
--sony

I'll make this simple for you, from one point of view. You've ported your application from one major release to another major release of the application server. Are you actually considering NOT testing some aspect of your application after that major a change? You should retest every aspect of your application.

Cluster with WLS 5.1 and WLS 8.1 servers?

hi all,
we are planning to upgrade our application running on WLS 5.1 to WLS 8.1. We
have configuraed a WLS 5.1 cluster with 4 servers joining this cluster. What
I'm now thinking of is: is it possible to run a WLS cluster that has 2
Servers running on WLS 5.1 and another 2 servers running on WLS 8.1?
Reason of thinking so, is that want to have the most failsafe configration
as possible during our upgrade.
I searched the BEA docs, but didn't find anything.
any help would be fine.
thanks
Alexander

You can have it but not for fail-safe configuration.
It is not possible to have clusters with different
WLS versions especially between 5.1 & 8.1
Kumar
Alexander von Alkier wrote:
hi all,
we are planning to upgrade our application running on WLS 5.1 to WLS 8.1. We
have configuraed a WLS 5.1 cluster with 4 servers joining this cluster. What
I'm now thinking of is: is it possible to run a WLS cluster that has 2
Servers running on WLS 5.1 and another 2 servers running on WLS 8.1?
Reason of thinking so, is that want to have the most failsafe configration
as possible during our upgrade.
I searched the BEA docs, but didn't find anything.
any help would be fine.
thanks
Alexander

Updating FMW 11gR1 11.1.1.5.0 and WLS 10.3.6, SOA compatibility?

I'm planning updates for a Fusion Middleware 11g Release 1 (11.1.1.5.0) installation with the following setup:
application domain: WebLogic Server 10.3.5.0
portal domain: WebCenter 11.1.1.5.0 on WLS 10.3.5.0
process domain: SOA Suite 11g (PS5) 11.1.1.6.0 on WLS 10.3.5.0 (process domain will not be updated)
The WLS 10.3.5 seems to be a dead end for patches so I'd like to go to WLS 10.3.6. That version is no longer compatible with FMW 11.1.1.5.0 so I'd have to update the rest of the FMW too to 11.1.1.6.0 - but we won't be updating the SOA Suite (for technical and other reasons).
If the SOA Suite 11g (PS5) 11.1.1.6.0 is running on WLS 10.3.5 would it be compatible with applications and portal (the rest of the environment) running on WLS 10.3.6? The apps and process instances communicate through web service interfaces. The WLS installations have domain trust set up. Are there other considerations?

Thank you HDeiby,
I have already done that but the thing is that now I want to open .bpel files with BP Designer but I can see it just as a regular xml file.
Do you have an idea of what could be done? I tried to install SOA into the same FMW home directory but that just ruined JDev. It reports now some errors and closes. I also tried to find an extension module for JDev but there is no extension for 11.1.2
I'm kinda stuck now so any help will be highly appreciated!

Looking for clarification on ADF 12.1.2 WLS support

What versions of WLS supports ADF 12.1.2? If there is support for 11g, are there any documentation on how to install the ADF 12 Runtime?
Oracle JDeveloper 12c Support</title><meta name="Title" content="Oracle JDeveloper 12c Support&q…
Application Servers
The following table shows application servers supported by JDeveloper and ADF. Application Server support for JDeveloper is provided for connecting and deploying directly to the server as well as debugging. For ADF, it refers to servers that ADF applications can be deployed to.
Application Server
JDeveloper
ADF
Oracle Fusion Middleware (WLS)
10.3.5+, 12.1.2
12.1.2
GlassFish
3.1+
3.1 (ADF Essentials)
WebSphere
8.x
JBoss
5
Tomcat
7
Oracle Cloud
13.1

I'm not hearing any oracle responses, thus I can only assume what Timo said is the closest to that fact.
Here is what I know about what a production ready standalone WLS 12c with ADF Runtime 12.1.2 entails:
-a domain running on WLS 12.1.2 needs JRF & Coherence to be installed in order to run ADF 12.1.2 https://forums.oracle.com/thread/2559381
-JRF & Coherence on WLS 12.1.2 needs a RCU database repository JDeveloper 12c & Standalone WLS w/ADF Runtime 12.1.2
-WLS 12.1.2 is only certified to run on Oracle DB 11.1.0.7+ http://www.oracle.com/technetwork/middleware/ias/downloads/wls-1211x-certmatrix-1395408.xls
Does that sound about right?
I hope I'm wrong and someone can guide me to easier setup. It seems that getting a standalone WLS server to run ADF has gotten harder with every new release!
I can get a standalone WLS 10.3.5 up with ADF 11.1.2.4 in ~3mins
http://www.youtube.com/watch?v=TG6wqrFVY00
WLS 10.3.6 with ADF 11.1.2.4 requires 2 additional console applied patches ontop of the 11.1.1.6 runtime installer. (Corrected from false version of 11.1.1.7)
WLS 12.1.2 with ADF 12.1.2 - I have not attempted but it seems to be even more involved than the previous.

JSTL WLS 7 to WLS 8.1 Upgrade Issues

We have a web app that currently runs on WLS 7. We have been asked to upgrade the app to WLS 8.1 recently. Most of the screen have ported fine, but there are a couple of screens that seem to be throwing fits. It could be a JDK/JRE issue, but here is the scenario
          jstl looks up a string variable property which is set to either "Y" or "N". Using WLS 7, it comes back as either "Y" or "N". But when I run the same code with WLS81, it comes back as "true" or "false".
          Looking at the property right before it returns always shows the correct value. When I look into the parameters and values, they seem to match the above statements as well (Y,N,true,false).
          Here is an interesting twist though. If I switch the JDK to 1.4 on WLS7, it also changes to "true" and "false". I have tried both sun and jrockit jvms to no avail.
          Has anyone seen this behavior?
          Thanks,
          Ashar

That's almost what I said but not quite, you should not have any trouble, but this is the real world hence my suggestion to backup properly first.
As for Yosemite I don't know the answer yet, I would expect it to be a no but we'll have to wait and see.

WLS 6.1 SP4- SP5/SP6

Good morning,
I tried re-running weblogic.ejbc on my ejb-jar files and it failed with the same
error. I am using Javlin for a transactional cache with WebLogic and I don't think
it knows anything about the getLoadUser and setLoadUser methods. I had the same
problem when I went to WS 6.1 SP4 with the methods __WL_needsRemove and __WL_setNeedsRemove
but I was able to implement those inside my bean code and everything worked. I
figured I could just implement the __WL_getLoadUser and __WL_setLoadUser and I
would be okay. I implemented them with an empty setLoadUser and tried various
returns for getLoadUser. After implementing them, I am able to access from the
database with no problem, but when I try to create beans, the program throws a
NullPointerException. I have not seen any information on what these two methods
are supposed to do but it seems they first show up in SP5.
Thanks,
Dan
Rob Woollen <[email protected]> wrote:
Does re-running weblogic.ejbc on your ejb-jar fix the problem?
-- Rob
Dan Shelton wrote:
Hello All,
I am trying to deploy some EJBs from a system with WS 6.1 SP4 ontoa system with
SP5/SP6 and get an error stating that the bean has to be declared abstractbecause
the methods __WL_getLoadUser() and __WL_setLoadUser(..) are not implemented.These
two methods are listed in the WLEnterpriseBean interface in weblogic.ejb20.interfaces
for SP5/SP6 but not in SP4. Anybody know what these methods are supposedto do?
I have found no information at all on these. I have a case in but figuredsomeone
might already know.
Have a good one,
Dan

Keith,
This message gives you exact reason. Double-check classpaths
used the start weblogic and to run ejbc. There may be something
left from previous installations.
Regards,
Slava Imeshev
"Keith" <[email protected]> wrote in message news:3fb0337c$[email protected]..
>
Hi,
We run version WLS 6.1 SP4 (I never noticed this when we were using
WLS 6.1) on each of development, system test, and production machines.
When I compile and deploy my web app to our devlopment machine
everything is fine. It is always compiled on our devlopment machine.
However when I deploy the same web app to our system test machine it
gives the following error:
####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
<myserver> <main> <system> <> <010004
<The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
This has always happened on our development machine but not on our
production machine, so it has never really been a problem because it
just recompiles it and everything is fine.
But now I have added some EJBs to the web app and now when I
recompiles it at startup it never compiles the new EJBs, and thus
never deployes them.
I have check the following on each machine to compare WLS versions.
wlgenerated file in the app jar file
java weblogic.ejbc -version
java weblogic.version
and java -version
They all report to be the exactly the same version.
Are there any suggestions to stop the WLS recompiling my app or to
make it compile my new EJBs when the server starts up.
Any suggestions would be very much appricited.
Cheers
Keith

ICEfaces WebMC running on WLS 10.0

Similar Messages

Maybe you are looking for