Upgrade options for WebLogic server 6.1

Is it better to upgrade from WebLogic server 6.1 to 7.0 first then go
to 8.1 or just go straight to 8.1? Has anyone ran into issues with
8.1 already and would have been better off staying with 7.0 until the
service pack for 8.0 comes out this July?

I'm biased since I work on the product, but I'd highly recommend going
straight to 8.1. We spent most of our time in WLS-land between 7.0 and
8.1 working on usability and stability of the server. I think you'll
find it's a very nice and solid upgrade, and it gets you to JDK 1.4.
I migrated several customer applications during our beta period. The
migration from 6.x or later to 8.1 is pretty straightforward.
-- Rob
mlap wrote:
Is it better to upgrade from WebLogic server 6.1 to 7.0 first then go
to 8.1 or just go straight to 8.1? Has anyone ran into issues with
8.1 already and would have been better off staying with 7.0 until the
service pack for 8.0 comes out this July?

Similar Messages

Examples.cluster.rmi for WebLogic Server 11g

How can I get package examples.cluster.rmi for WebLogic Server 11g?
I would like to perform a similiar test like the following:
https://freepaper.taichung.gov.tw/examplesWebApp/examples/src/examples/cluster/rmi/package-summary.html
Thanks a lot

Hi,
I have just now installed WLS via the net installer, and the default examples server password of welcome1 does indeed work for me.
However, I note from your post that you are using port 7101, not 7001. Could that be the issue?
http://localhost:7101/console/login/LoginForm.jspKevin

Is OIM 10.x available for WebLogic Server?

Is OIM 10.x available for WebLogic server? The only download I see on the site for OIM 10.x is the fully bundled suite with OracleAS.

If by OIM you mean Oracle Identity Manager, then OIM 9.1 is supported on Weblogic 10.x. OIM 9.1 is NOT part of or the same thing as Oracle Identity Management 10g. The latter is a set of services tightly coupled with Oracle's app server (OC4J). Identity Management 10g does not run on Weblogic. Some people like to say that Identity Management 10g includes all Oracle identity management products which adds to the confusion.
Look here: http://www.oracle.com/technology/documentation/oim1014.html

Failed to start Admin Server for Weblogic Server Domain

I Created a domain named mydomain in weblogic server 10.3 in server 2003.But when i start Admin Server for Weblogic Server Domain from startmenu, it failed.
I examined the log under domains\mydomain\servers\AdminServer\logs\AdminServer.log and got the following information:
java.lang.NoClassDefFoundError:weblogic/ldap/EmbeddedLDAPChange
at weblogic.ldap.EntryChangeListenerImpl.receiveEntryChanges(EntryChangeListenerImpl.java:28)
Caused by :java.lang.ClassNotFoundException: weblogic.ldap.EmbeddedLDAPChange
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
Caused by :java.util.zip.ZipException: error reading zip file
at java.util.zip.ZipFile.read(Native Method)
at java.util.zip.ZipFile.access$1200(ZipFile.java:29)
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attemping to load LDIF for provider RoleMapper from file ...\domains\mydomain\security\XACMLRoleMapperInit.ldift.
at ...(CommonSecurityServiceManagerDelegateImpl.java:465)
Caused by: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attemping to load LDIF for provider RoleMapper from file ...\domains\mydomain\security\XACMLRoleMapperInit.ldift.
at .. (ServiceEngineImpl.java:365)
Caused by: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: A failure occurred attemping to load LDIF for provider RoleMapper from file ...\domains\mydomain\security\XACMLRoleMapperInit.ldift.
at .. (BootStrapServiceImpl.java:910)
Caused by: <openjpa-1.1.1-SNAPSHOT-r422266:891341 nofatal user error>kodo.jdo.UserException: This operation cannot be perfomed while a Transaction is active.
at org.apache.openjpa.kernel.BrokerImpl.close(BrokerImpl.java:4087)
####<Critical><WebLogicServer><SOA><Adminserver><main><<WLS Kernel>><><><1282012271468><BEA-000362><Server failed. Reason:
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399] Security Services Unavailable
at weblogic.security.service.CommonSecurityserviceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
I ignored some detailed error message.The runtime environment is server 2003 Enterprise Edition sp2.
Thx in advance for any reply.

Hello Djam,
Please review the following:
The FMW WebLogic Server (WLS) installation has been configured to use a non-default Java temporary files directory,
i.e. the following has been set in the WebLogic startup or setDomainEnv.sh script:
EXTRA_JAVA_PROPERTIES="-Djava.io.tmpdir=/appl/oracle/temp_java_files ${EXTRA_JAVA_PROPERTIES}"
Reference: How to Change the WebLogic Server Location for Temporary Files (Doc ID 1336002.1)
When the Middleware home was restored the directory specified by java.io.tmpdir parameter was missing,
Therefore an IOException occurred when opening the wallet and WLS was unable to initialize the OPSS successfully.
To resolve the issue re-create the directory specified by the java.io.tmp dir parameter, and make sure the owner and group access are the same as for the FMW installation.
Unable Start AdminServer: JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException (Doc ID 1923395.1)
Bogdan

No login command was found for 'WebLogic Server 10.3.5.0 - in managed serve

i am getting following warning when i run my web logic managed server
No login command was found for 'WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 Oracle WebLogic Server Module Dependencies 10.3 Thu Mar 3 14:37:52 PST 2011 Oracle WebLogic Server on JRockit Virtual Edition Module Dependencies 10.3 Thu Feb 3 1.
Would appreciate suggestions to resolve.
Thanks.

Hi,
Add -Dweblogic.StdoutDebugEnabled flag while starting the managed server and then post the verbose error message in your next post
For setting the flag follow the below steps
If your using Linux box and not using node manager to start the managed server,add the below line startManagedWebLogic.sh file
JAVA_OPTIONS="-Dweblogic.StdoutDebugEnabled=true ${JAVA_OPTIONS}"
echo "JAVA_OPTIONS=${JAVA_OPTIONS}"
If your using Windows box and not using node manager to start the managed server,add the below line startManagedWebLogic.cmd file
set JAVA_OPTIONS=-Dweblogic.StdoutDebugEnabled=true %JAVA_OPTIONS%
echo JAVA_OPTIONS=%JAVA_OPTIONS%
If you are starting the Managed server through the node manager then use these flags From Admin console : servers >>>. MS1 >>>> server start >>>> Arguments :-Dweblogic.StdoutDebugEnabled=true
Regards,
Fabian

Missing license file for : WebLogic Server 6.1

Hi there,I just installed the weblogic server and want to test the mssqlserver4 driver. I run the example.jdbc.mssqlserver4.ThreadTests.java. I met this kind of erro message:ThreadsTests - exception java.sql.SQLException: java.sql.SQLException: $$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$Missing license file for: WebLogic Server 6.1$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$I do not know why.Philip

Check to make sure that the directory in which you have a valid license file
"license.bea" is included in your CLASSPATH.
-Utpal
"Philip" <[email protected]> wrote in message
news:3ba8e9be$[email protected]..
Hi there,I just installed the weblogic server and want to test themssqlserver4 driver. I run the example.jdbc.mssqlserver4.ThreadTests.java. I
met this kind of erro message:ThreadsTests - exception
java.sql.SQLException: java.sql.SQLException: $$$$$$$$$$$$$$$$ License
Exception $$$$$$$$$$$$$$$$Missing license file for: WebLogic Server
6.1$$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$I do not know
why.Philip

How to install license for Weblogic Server 6.1

Hi,
I downloaded WebLogic Server 6.1, it works fine.
but I want to change the JDBC to Oracle (the default is Cloudscape). I follow the
instructions in page "Installing WebLogic jDriver for Oracle". it looks fine until
"java utils.dbping ORACLE james 1234 DBServer"
it says: Missing license file for: Weblogic Server 6.1.
I found the licese.bea is in c:\bea, I use "updatelicense.cmd" to do it several times,
it still doesn't work.
I am using Win2k and Oracle 8.1.7
Thanks.
James

Hi.
http://edocs.bea.com/wls/docs61/jcom.html
or do you have a more specific issue?
Regards,
Michael
Raymond Cheng wrote:
Anybody know how to prepare JCOM environment for developer to intetrate their windows client.
Thanks a lot.
Raymond Cheng.--
Michael Young
Developer Relations Engineer
BEA Support

Can anyone tell me Why?Missing license file for: WebLogic Server 6.1

Thank you for take a look and give me solution!
Missing license file for: WebLogic Server 6.1
Error encountered:
java.sql.SQLException: Fail to load jDriver/Oracle due to license checking failed!

make sure the folder in which the license file exists, is in the classpath
sree
"Robert" <[email protected]> wrote in message
news:3b57da5e$[email protected]..
>
"Roberto" <[email protected]> wrote:
Thank you for take a look and give me solution!
Missing license file for: WebLogic Server 6.1
Error encountered:
java.sql.SQLException: Fail to load jDriver/Oracle due to license
checking
failed!

Are there different licensing schemes for WebLogic Server?

Is there different licensing schemes for WebLogic server?
For example,
Is there a licensing scheme to purchase a runtime WLS license so we can run only ADF and BIP?
Is there a licensing scheme to purchase a runtime WLS license so we can run only ADF and Oracle Reports?
Edited by: 957072 on Jan 28, 2013 5:43 AM

Please go through below metalink id for weblogic licensing.
Master Note on WebLogic Server (WLS) Licensing and License Files [ID 1076283.1]
Thanks,
Kishore

How can i build application using Jdeveloper 10g for Weblogic server 10.3

Hi,
We have a requirement where in we want to build an SOA application using Jdeveloper 10g for Weblogic Server 10.3.
Is there any way to make a connection to Weblogic Server 10.3 from JDeveloper 10g? If there is any way please share it with me.
Thanks,
Amit Kumar

Amit,
SOA Suite is not yet certified for WLS 10.3. You have to wait for the certification of it.
At the moment you can't install the SOA Suite on WLS 10.3 nor connect from JDev 10.1.3 to it.
--olaf

Upgrade Options for ENVY dv6-7366ez

Hello.
I bought an ENVY dv6-7366ez notebook and I like to know the upgrade options for it (GPU, CPU, Display, Optical Drive). Here in Hungary I tried to contact with the official Hungarian HP support but they didn't have any information.... They said that the HP HQ don't share any information about it with them, but as i saw that's not true because i see many topics in the forum... Just not for my new/old notebook... So like to know which CPUs and GPUs are compatible with my notebook and what are the display and optical drive upgrade possibilities.
Product Number: D5m07EA#UUZ
BIOS Type   Insyde EFI
BIOS Version   F.29
System BIOS Date   10/03/2013
Video BIOS Date   11/18/11

Hi,
The following link shows specs of your machine:
    http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&dlc=en&docname=c03666370
and the following link shows manuals, guides for your machine:
   http://h10025.www1.hp.com/ewfrf/wc/manualCategory?cc=us&lc=en&product=5361167
Page #1 of manusl #1 shows a list of CPU's supported.
You can upgrade RAM to 16Gb and MAY BE able to upgrade CPU. Other than that you may consider buying a new machine, could be cheaper.
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Where You can create a support case for weblogic server?

Hi all,
I would like to know where I can create a support case for weblogic server?
I logged me in metalink3 but I did not found a way to create a service request for WLS.
Thanks in Advance.

I believe you still need to use BEA's support resources at this point: http://www.oracle.com/bea/support.html

Query about the steps for Weblogic Server Upgrade from 8.1 to 10.3

Hi!
We have planned to upgrade our Weblogic Server from 8.1 to 10.3. Could anyone advise me:
1. How to upgrade the Weblogic Server from 8.1 to 10.3? Can the Weblogic Server 10.3 coexist with the Weblogic Server 8.1 in one physical server?
2. Where can the upgrade software be downloaded?
3. We have a web service currently running under Weblogic Workshop as the Weblogic Server is started via the workshop. Can this web service be run under Weblogic Server 10.3?
4. Are there any foreseeable issues/problems that will happen?
Please kindly help me. Thanks a lot.
Best Regards
May

Download location: http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
You can upgrade the domain after you install wls 10.3 using QuickStart.
When we migrated we have moved from windows to linux. We have installed, created domain, created managed servers, configured, etc. from scratch. We didn't face any 'show stopper' issues.

Admin training for WebLogic Server - just the Forms and Reports parts

We will be upgrading our Forms & Reports application from 10gR2 to 11g. Our customers (well their DBAs) will need to install and manage WebLogic Server. So I'm looking for a training course where they can learn how to do that. The WebLogic Server admin course is 5 days, and another 4 for Advanced System Admin, which seems a lot as they are only going to use the parts required for Forms and Reports.
I have read through the tutorial Using Oracle Enterprise Manager to Administer Forms Services. Is this the extent of what they need to know, or is there another chunk of the iceberg under the water? Can you recommend a training course please.

Hi,
After installing forms, the installer itself configures the WLS with the domains etc and also deploys the forms. Once after this, it is similar to that of 10g Application Server. All the maintenance of the forms is done using Enterprise Manager (EM Console). So, the section you mentioned should suffice.
-Arun

EJB deployment error for Weblogic server 9.2 mp4

Hi,
While trying to deploy a small EJB jar file which uses EJB 2.1 CMP beans with relationships, getting the following error from Weblogic server 9.2 MP4:
=================================================================================================
<Error> <EJB> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988333> <BEA-012036> <Compiling generated EJB classes produced the following Java compiler error message:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
>
####<Nov 1, 2011 4:09:48 PM IST> <Error> <Deployer> <VinodThinkPad> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1320143988380> <BEA-149265> <Failure occured in the execution of deployment request with ID '1320143984947' for task '1'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
weblogic.application.ModuleException: Exception preparing module: EJBModule(EJBTest)
Unable to deploy EJB: EJBTest.jar from EJBTest.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:382)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.io.IOException: Compiler failed executable.exec:
C:\bea\user_projects\domains\base_domain\servers\AdminServer\cache\EJBCompilerCache\19ivqhpr6jvsc\Test1\Order_cpl9bk__WebLogic_CMP_RDBMS.java:570: incompatible types
found : <nulltype>
required: int
shipmentId = null;
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:340)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:432)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:754)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:657)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1201)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:355)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:189)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
     at weblogic.deploy.internal.targetserver.DeploymentManager.configPrepareCompleted(DeploymentManager.java:594)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepareCompleted(DeploymentServiceDispatcher.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCompletedCallback(DeploymentReceiverCallbackDeliverer.java:228)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$300(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$4.run(DeploymentReceiverCallbackDeliverer.java:95)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
=================================================================================================
While I'm able to deploy without the CMP 1-1 relationship, the moment I introduce the 1-1 relationship, I get this error. Database used is Oracle 10g XE.
I have been battling this error for more than a day now. Kindly help me fix this.
Thanks in advance!
Regards,
Vinod

Hi,
I was able to figure out the root cause. I was using the primitive data type "int" for primary key and foreign key for one of the beans in the relationship. After I changed it to "Integer" wrapper type, the issue got resolved.
-Vinod

Upgrade options for WebLogic server 6.1

Similar Messages

Maybe you are looking for