SP10 for WebLogic Server 5.1

Does anybody know when SP10 will be released.
Thanks,
Peter

Francesco,
Thank you for pointing out the incosistency. WLCS 3.2 sp2 was tested and designed
for WLS 5.1 SP10, not SP8. I have logged a CR against the documentation to update
this.
As for the "async" error that is showing up, this is caused by a change in the
WLS cache tag in between WLS service packs. You must replace any preexisting weblogic.tld
files with the version that is included in 3.2 sp2.
You will find the weblogic.tld in the WEB-INF folder of your web-apps.
Post back if you have more problems,
PJL
[email protected] (francesco costa) wrote:
Hello.
We are running WLCS3.2sp2 with WLSsp10.
We have problems in openining the tools, we get a problem because of
a
missing "async" attribute in wl:cache jsp tag.
We have also found the following two sentences in the product docs:
1. WLCS 3.2 SP2 requires WebLogic Server 5.1 with Service Pack 10
(SP10).
2. WebLogic Server 5.1 SP 8 is required for development and production
deployments.
What does it mean ? Do we need 10 or 8 ? Is this the cause of our
problem ?
Thanks.
Franco

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

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

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

Requesting links for Weblogic Server 8.1 (sp5) binaries for all platforms.

This might seem like a brazen request, but could someone provide me a link for Weblogic 8.1 (sp5) binaries. . .It seems unreasonable to spend $2,000 just to download a product version no longer supported by Oracle. The fact of the matter is that my client and my client's third-party staging server deploys their application in Weblogic 8.1 (sp5); believe me, if I had the authority and range of control to update my client's staging server and production server I would.
Regards,
Chuck
Edited by: user11226438 on Jun 3, 2009 7:33 AM
Ok, I found a majority of Weblogic's 8.1 (sp6) links. . .do you think developing on sp6 and deploying to sp5 will cause some issues? I'm supposing it won't and while the client has yet to deliver the application, the app server, documentation, or any other required materials, I'd at least like to get an environment that is compliant with their staging server's environment before-hand.
Edited by: user11226438 on Jun 3, 2009 9:38 AM
If anyone thinks that I will need to acquire a license for running (a sanboxed) version of Weblogic please let me know so I can inform my employer accordingly.

If MQ V5 clients cannot interoperate with MQ V7 servers, then perhaps MQ V6 clients support the 1.4 JVM? If so, I suppose you can use an MQ V6 client to communicate with V7.
Alternatively, perhaps MQ's "extended transactional client" provides more flexibility in interoperability than the client you're using.
Tom

Solaris 10 64 bit and 64 bit JVM support for Weblogic Server 9.1

Does the following configuration supported:
Weblogic Server 9.1
Sun Solaris 10 (64 bit)
Sun JVM 5.0 (64 bit)
I could only find reference to 32 bit JVM on bea site.
Any help is appreciated.
Thanks

Hi.
answers inline:
sanjay wrote:
Hi,
Can Weblogic Express (Cluster edition)6.1J sp2 be installed on Sun Solaris(Sparc)
8(64 bit) ?Yes - http://edocs.bea.com/wls/platforms/index.html#solaris8
>
>
Can Weblogic Express (Cluster edition)6.1J sp2 JDBC driver be used for Oracle 8.1.7(Solaris
64 bit) ?
Yes - http://edocs.bea.com/wls/platforms/index.html#jdbc
Michael Young
Developer Relations Engineer
BEA Support

Enterprise Manager For WebLogic Server 10.3

Hi,
I have a weblogic server version 10.3.
I want to access the Enterprise Manager for the same.I believe standalone version of weblogic server 10.3 doesnt come with
Enterprise Manager.
I believe we can have EM if we download Application Development Runtime.
I tried doing the same ,but I am unable to launch the Enterprise Manager Website.
My server is running on on port 7001 ,hence I tried accessing the Enterprise Manager
using the below url i.e http://localhost:7001/em,but i was not able to access.
Could somebody help me on how I can access the enterprise Manager.
Regards
Harish

Actually, with FMW 11g (WLS version 10.3.1 NOT 10.3), there is now an application called Fusion Middleware Control that is part of the Enterprise Manager family. This typically binds to http://host:port/em on the AdminServer. This is for the FMW components in a single domain, plus any other web tier components like Oracle HTTP Server or Web Cache.
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10223/17_em.htm
Check the docs for installation instructions of this component.

SP10 for WebLogic Server 5.1

Similar Messages

Maybe you are looking for