EJB Migration Problem (WLS 9.2 = WLS 10.3.2)

Hi,
we are migrating Stateful, Stateless, and Message Driven Bean from wls 9.2 to wls 10.3.2. There is no compile error. But workshop shows Error: "Failed to retrieve WLS runtime for EJB processing".
Thank you very much for your input.
John

Similar Messages

Message transmission from Wls 7 to Wls 8 and then to Wls10

Hi All,
We are currently doing a POC in which we are using Wls 7, Wls 8.1 and Wls 10 . The basic idea of the POC is that we need to post a message on Wls 7, and from Wls 7 the message should reach Wls 8.1 and inturn from Wls 8.1 it should reach Wls 10. For this communication to take place we have configured message bridges on the respective servers.
But the problem that we are facing is, we are not bale to transmit message from one Wls server to other, from Wls 7 to Wls 8 and also from 8 to 10.
We are gettin the following error:-
<Error> <Security> <090473> <ServerIdentity failed validation, downgrading to anonymous.>
Can anybody please help on this.
Regards,
Rakesh

If this is just a POC, you might try enabling Domain Trust on each of the domains (here is the 10.3 link, probably different in 8.1 and 7.0):
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/security/EnableTrustBetweenDomains.html
In a production environment there are other security implications for doing this willy nilly, that I recommend you read the docs and post questions in the WLS Security forum.

Photoshop/Elements to Revel Photo Migration Problem!

What happened to my Photoshop/element photos? They were supposedly migrated, but I don't see them! I have no albums in my Revel account.I had a paid subscriiption and it was cancelled back in or around February, and told that the photos would be moved over to REVEL...Can anyone help me to get them back?

First, thanks Pattie for following up with me. I am going to check my backed up hard drives to see if my photoshop materials are on them. It will take me a few days, as I have only small amounts of time to research it at this time. maybe a break will come in a day or two for a determination.
Date: Mon, 12 Aug 2013 09:45:52 -0700
From: [email protected]
To: [email protected]
Subject: Photoshop/Elements to Revel Photo Migration Problem!
    Re: Photoshop/Elements to Revel Photo Migration Problem!
    created by Pattie F in Photoshop.com Sharing and Storage - View the full discussion
Michael-
Is it possible you logged into Photoshop.com with a different email, or is it possible that you did not set up your Elements to sync with Photosho.com? These are the two main reasons users can not find their files.
The Photoshop.com account created in 2009 with the email you use to log in to this forum has no files in it, and therefore, nothing migrated to the Revel account with the same login. You do have a Revel account with the same login, but it is also empty since nothing migrated.
Pattie
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5587690#5587690
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5587690#5587690
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5587690#5587690. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Photoshop.com Sharing and Storage by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

I have one migration problem.

Dear All,
i have one migration problem.
while doing transfer rules migration i got a popup saying that " GJAHR source filed automatic conversion is not possible "
what is this message if continue with that what will happens if not what i should do.

hi vsuree,
If u r getting this message for field FISCPER of ur data source,then map Fiscper to 0Fiscyear ,the system wil automatically convert it and the problem will be resolved. hope it will help u.
thanks

Webservice Migration Problems (WLS 9.2 - WLS 10.3.2)

Hi,
we're upgrading our weblogic server from version 9.2 to 10.3.2. Everything runs just fine in my testing environment except for the webservices we have.
We have 6 webservices (JAX-RPC) which use a generic set of xml schema types to which each webservice offers specialized types that extend the supertype. Here comes the problem: The ant tasks wsdlc and clientgen from wls 9.2 generates java classes that do extend from the superclass. Unfortunatley the same call from the wls 10.3.2 results in a loss of class hierarchy.
Example:
<xs:complexType name="personinfo">
<xs:sequence>
<xs:element name="firstname" type="xs:string"/>
<xs:element name="lastname" type="xs:string"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="fullpersoninfo">
<xs:complexContent>
<xs:extension base="personinfo">
<xs:sequence>
<xs:element name="address" type="xs:string"/>
<xs:element name="city" type="xs:string"/>
<xs:element name="country" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
On WLS 9.2 this results in the following:
class Personinfo {
class Fullpersoninfo extends Personinfo {
On WLS 10.3.2. the result differs:
class Personinfo implements Serializable {
class Fullpersoninfo implements Serializable {
Is there any way to tell the wls 10.3.2 to generate a jax-rpc webservice that obeys the extension directive?
I look forward to your replies =)
Regards,
Johannes Bialek

Hi Jay,
thanks for the reply. Unfortunately using the other ant task doesn't seem to help. This is a WLS8.2 Version of Clientgen (which used the attribute "clientjar" rather than "destDir"/"destFile" and expected "packagename" as a required parameter). I tried id and it seems to have a couple of problems with schema files imported in included schema files. I worked around this by importing in the schema files from the wsdl itself, but now I get a "weblogic.xml.schema.binding.BindingException: ERROR: during code compilation".
Full stack trace:
weblogic.xml.schema.binding.BindingException: ERROR: during code compilation
at weblogic.xml.schema.binding.internal.codegen.Compiler.invoke_compiler(Compiler.java:581)
at weblogic.xml.schema.binding.internal.codegen.Compiler.compile_descriptors(Compiler.java:380)
at weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compiler.java:290)
at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.addTypesInSchemas(XSDTypeMappingBuilder.java:140)
at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.processSchemaTypes(TypeMappingBuilderBase.java:310)
at weblogic.webservice.tools.build.internal.Schema2JavaImpl.doTypeMapping(Schema2JavaImpl.java:317)
at weblogic.webservice.tools.build.internal.Schema2JavaImpl.run(Schema2JavaImpl.java:204)
at weblogic.webservice.tools.build.internal.WSDL2JavaImpl.run(WSDL2JavaImpl.java:258)
at weblogic.webservice.tools.build.internal.ClientGenImpl.getTypeMappingFromWSDL(ClientGenImpl.java:747)
at weblogic.webservice.tools.build.internal.ClientGenImpl.doClientGenFromWsdl(ClientGenImpl.java:419)
at weblogic.webservice.tools.build.internal.ClientGenImpl.run(ClientGenImpl.java:359)
at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.doClientGen(ClientGenTask.java:375)
at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:229)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: java.io.IOException: Compiler failed executable.exec: null
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:493)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:332)
at weblogic.xml.schema.binding.internal.codegen.Compiler.invoke_compiler(Compiler.java:575)
... 41 more
Shouldn't we be able to use a 9.2 weblogic.jar for creating webservices that run on a 10.3.2?
Regards,
Johannes

EJB Compliance problem with WLS 9.1, Ant 1.6.5

We create an actionframe which in turn creates any ejbs that are needed for a users particular session. However, I am seeing the following error during the build's appc task.
weblogic.ejb.container.compliance.ComplianceException: In EJB cbm.persistence.generic.sponsorCheckListItem.SponsorCheckListItem, the home interface of a stateless session bean must have one create method that takes no arguments.
     at weblogic.ejb.container.compliance.SessionHomeInterfaceChecker.checkStatelessNoArgCreate(SessionHomeInterfaceChecker.java:82)
     at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
     at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
     at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:261)
     at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:215)
     at weblogic.ejb.container.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:868)
     at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:836)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:228)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:494)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:434)
     at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:292)
     at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:95)
     at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:113)
     at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:43)
     at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:55)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:24)
     at weblogic.application.compiler.Appc.runBody(Appc.java:151)
     at weblogic.utils.compiler.Tool.run(Tool.java:158)
     at weblogic.utils.compiler.Tool.run(Tool.java:115)
     at weblogic.application.compiler.Appc.main(Appc.java:162)
     at weblogic.appc.main(appc.java:14)
Any thoughts as to why this would be throwing this particular error here, when it has already checked several other ejbs that do not use the create method either?

Here is the EJB java file followed by the xdoclet created home file.
* The persistor used to load/store entity attribute objects
* @ejb:bean type="Stateless"
* name="cbm.persistence.generic.sponsorCheckListItem.SponsorCheckListItem"
* jndi-name="cbm/persistence/generic/sponsorCheckListItem/SponsorCheckListItem"
* display-name="cbm/persistence/generic/sponsorCheckListItem/SponsorCheckListItem"
* view-type="remote"
* @ejb:interface remote-class = "bf.cbm.implementation.persistors.generic.sponsorCheckListItem.SponsorCheckListItemPersistor" extends="bf.cbm.framework.engine.persistor.Persistor"
* @ejb:home remote-class = "bf.cbm.implementation.persistors.generic.sponsorCheckListItem.SponsorCheckListItemPersistorHome" extends="javax.ejb.EJBHome"
* @ejb:transaction-type type="Container"
* @ejb:transaction type="Supports"
* @weblogic:transaction-descriptor trans-timeout-seconds="600"
public class SponsorCheckListItemPersistorEJB extends BaseBeanDaoPersistorBean implements SessionBean {
     protected IGenericDao getDao() {
          return DaoManagerFactory.getDaoManager().getSponsorCheckListItemDao();
* Returns the CBM, Cacheable, Proxyable interface class for the object
* @return Class Cacheable interface class
public Class getInterfaceClass() {
return SponsorCheckListItem.class;
* Returns the PersistorHome class for the object
* @return Class PersistorHome class
public Class getPersistorHomeClass() {
return SponsorCheckListItemPersistorHome.class;
* Returns the Bean class for the given object
* @return Class bean class
public Class getBeanClass() {
return SponsorCheckListItemBean.class;
* Returns the hecklist template record for the given carrier checklist template
* @param sponsor the sponsor for the check list
* @return an array of CacheImpl
     * @ejb:interface-method
public CacheImpl[] findBySponsor(CacheImpl sponsor){
Object[] args = new Object[1];
args[0] = sponsor.getHandle();
return findByObject("findBySponsorHandle", args);
* Generated by XDoclet - Do not edit!
package bf.cbm.implementation.persistors.generic.sponsorCheckListItem;
* Home interface for cbm.persistence.generic.sponsorCheckListItem.SponsorCheckListItem.
* @xdoclet-generated at April 24 2006
public interface SponsorCheckListItemPersistorHome
extends javax.ejb.EJBHome
public static final String COMP_NAME="java:comp/env/ejb/cbm/persistence/generic/sponsorCheckListItem/SponsorCheckListItem";
public static final String JNDI_NAME="cbm/persistence/generic/sponsorCheckListItem/SponsorCheckListItem";
Again, these two files look very similar to all of our other EJBs and their generated classes. The only ejb containing a create class is the ActionframeHome.java file generated from the ActionFrameEJB.java, which contains an EJBCreate() class.
Thanks for the help!!

Porting EJB 3 MDB from OC4J to WLS

Posting this again since my last post didn't seem to take.
I get the following three deployment error messages when attempting to deploy an application to WebLogic Server 10.3 technical preview. The problem is centered around my deployment of an EJB 3 message driven bean.
1. An error occurred during activation of changes, please see the log for details.
2. Exception preparing module: EJBModule(EngineEjb.jar) Unable to deploy EJB: Requestor from EngineEjb.jar: [EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment. weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'jms/demoQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation. at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:641) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:246) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1013) at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:907) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1211) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:387) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:381) 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.EarDeployment.prepare(EarDeployment.java:16) 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:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:517) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
3. Substituted for missing class [EJB - 11026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment. weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'jms/demoQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.
My MDB uses an annotation like the following:
@MessageDriven(mappedName = "jms/demoQueue", name = "MyMDB",
activationConfig =
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue")
@ActivationConfigProperty(propertyName = "messageSelector", propertyValue =
"RECIPIENT = 'MyRecipient'")
Earlier, I did create a JMS Module named demoQueue with the following resources:
Name Type JNDI Name
testQueue Queue jms/demoQueue
ConnectionFactory-0 Connection Factory jms/QueueConnectionFactory
Any suggestions to fix the WLS deployment error?
For continuing compatibility with my OC4J deployment, I would like to continue using a connection factory with the following JNDI name "jms/QueueConnectionFactory" shown above.
So I plan to add the following properties to the @MessageDriven annotation above. These are needed to continue working with our OC4J deployment. However, my primary concern is to get this MDB working with WLS. Does this strategy seem reasonable for allowing deployment to both OC4J and WLS?
@ActivationConfigProperty(propertyName = "connectionFactoryJndiName",
propertyValue =
"jms/QueueConnectionFactory") ,
@ActivationConfigProperty(propertyName = "destinationName", propertyValue =
"jms/demoQueue")
Thanks,
Travis

Travis, you pose a very good question. If I understand your goal, you would like to use code that compiles and works in OC4J and WLS. For example, you want to use javax.ejb.MessageDriven instead of weblogic.ejbgen.MessageDriven.
Using something like mappedName as it is referred to here allows you specify the JNDI name in WLS if it is not defined elsewhere, but it appears to be specific to the WLS implementation.
I've seen several other questions posed about finding all of the available ActivationConfigProperty name / value pairs and I have been unable to find it myself.
I tried several permutations of annotations, and I can't figure out why something like this would even work, but it does. The mapped name is my JNDI name, but I never specify that it is a javax.jms.Queue or which connection factory to use. How does WLS figure that out?
@MessageDriven(
     mappedName = "exampleQueue", name = "HelloWorldMDB"
public class HelloWorldMDB implements MessageListener {
     @Override
     @TransactionAttribute(value = javax.ejb.TransactionAttributeType.REQUIRED)
     public void onMessage(Message message) {
          System.out.println( "received message " + message );
}This is a good question for support as the documentation seems to be incomplete here.

Problem in servlet engine (WLS 7.0) with the chunked transfer

Hi,
          While using jakarta-slide on weblogic 7.0, I encountered the following
          problem while uploading files using WebDAV servlet deployed on WLS:
          "**** This file has a corrupted %%EOF marker, or garbage after the
          %%EOF."
          Is this is a problem with the way that WLS servlet engine is handling
          chunked transfers ?
          According to the change request 084847, "For chunked
          transfer, WebLogic Server was including a hexadecimal number which
          other
          servlet engines used to ignore. This has been fixed WLS 6.1 sp 4."
          Is this fixed in WLS 7.0 ? I could not find this in the resolved bugs
          list for WLS 7 SP1. If this has not been fixed in 7.0, any idea when
          this fix would make it to WLS 7.0 ?
          Any pointers would be of great help.
          Thanks,
          Jeeji.


Hi,
          While using jakarta-slide on weblogic 7.0, I encountered the following
          problem while uploading files using WebDAV servlet deployed on WLS:
          "**** This file has a corrupted %%EOF marker, or garbage after the
          %%EOF."
          Is this is a problem with the way that WLS servlet engine is handling
          chunked transfers ?
          According to the change request 084847, "For chunked
          transfer, WebLogic Server was including a hexadecimal number which
          other
          servlet engines used to ignore. This has been fixed WLS 6.1 sp 4."
          Is this fixed in WLS 7.0 ? I could not find this in the resolved bugs
          list for WLS 7 SP1. If this has not been fixed in 7.0, any idea when
          this fix would make it to WLS 7.0 ?
          Any pointers would be of great help.
          Thanks,
          Jeeji.

Problem starting the server WLS after installing OIM11g

Failed to restart weblogic server after installing Oracle Identity Manager 11g.
Weblogic server log Part:
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719297> <BEA-149060> <Module iam-async-mdb.jar of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719297> <BEA-149059> <Module xlWebApp of application oim [Version=11.1.1.3.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719297> <BEA-149060> <Module xlWebApp of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719297> <BEA-149059> <Module oim of application oim [Version=11.1.1.3.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149060> <Module oim of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149059> <Module SchedulerService-web of application oim [Version=11.1.1.3.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149060> <Module SchedulerService-web of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149059> <Module workflowservice of application oim [Version=11.1.1.3.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149060> <Module workflowservice of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149059> <Module sodcheck of application oim [Version=11.1.1.3.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149060> <Module sodcheck of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149059> <Module callbackResponseService of application oim [Version=11.1.1.3.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149060> <Module callbackResponseService of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149059> <Module jmx-config-lifecycle of application oim [Version=11.1.1.3.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149060> <Module jmx-config-lifecycle of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149059> <Module admin of application oim [Version=11.1.1.3.0] is transitioning from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
####<Dec 23, 2010 4:15:19 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149719312> <BEA-149060> <Module admin of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server oim_server1.>
*####<Dec 23, 2010 4:15:21 PM PST> <Error> <HTTP> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721875> <BEA-101216> <Servlet: "XellerateBootstrapServlet" failed to preload on startup in Web application: "xlWebApp".*
java.lang.NoClassDefFoundError: weblogic/jdbc/wrapper/XAConnection
     at java.lang.ClassLoader.defineClass1(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
     at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:328)
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:285)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
     at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:247)
     at weblogic.utils.classloaders.GenericClassLoader.defineCodeGenClass(GenericClassLoader.java:508)
     at weblogic.utils.classfile.utils.CodeGenerator.generateClass(CodeGenerator.java:73)
     at weblogic.utils.wrapper.WrapperFactory.generateWrapperClass(WrapperFactory.java:340)
     at weblogic.utils.wrapper.WrapperFactory.getWrapperClass(WrapperFactory.java:244)
     at weblogic.utils.wrapper.WrapperFactory.getWrapperClass(WrapperFactory.java:190)
     at weblogic.utils.wrapper.WrapperFactory.createWrapper(WrapperFactory.java:175)
     at weblogic.jdbc.wrapper.JDBCWrapperFactory.getWrapper(JDBCWrapperFactory.java:194)
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:507)
     at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:173)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)
     at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:427)
     at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
     at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:322)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:438)
     at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:317)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
     at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
     at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1670)
     at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1468)
     at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
     at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
     at oracle.iam.platform.Platform.loadConnectionRetryProperties(Platform.java:147)
     at oracle.iam.platform.Platform.getOperationalDS(Platform.java:118)
     at oracle.iam.platform.utils.OIMMessageResourcesUtil.getXLResourcesFromDB(OIMMessageResourcesUtil.java:413)
     at oracle.iam.platform.utils.OIMMessageResourcesUtil.getXLResources(OIMMessageResourcesUtil.java:398)
     at oracle.iam.platform.utils.OIMMessageResourcesUtil.getCustomDefaultResources(OIMMessageResourcesUtil.java:388)
     at com.thortech.xl.webclient.util.tcMessageResourcesUtil.getCustomDefaultResources(tcMessageResourcesUtil.java:128)
     at com.thortech.xl.webclient.servlet.XellerateBootstrapServlet.initializeLocalizationUtil(XellerateBootstrapServlet.java:92)
     at com.thortech.xl.webclient.servlet.XellerateBootstrapServlet.init(XellerateBootstrapServlet.java:48)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721922> <BEA-149059> <Module admin of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721953> <BEA-149060> <Module admin of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721953> <BEA-149059> <Module jmx-config-lifecycle of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721953> <BEA-149060> <Module jmx-config-lifecycle of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721953> <BEA-149059> <Module callbackResponseService of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721953> <BEA-149060> <Module callbackResponseService of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721953> <BEA-149059> <Module sodcheck of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721969> <BEA-149060> <Module sodcheck of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721969> <BEA-149059> <Module workflowservice of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721969> <BEA-149060> <Module workflowservice of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721969> <BEA-149059> <Module SchedulerService-web of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721969> <BEA-149060> <Module SchedulerService-web of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721969> <BEA-149059> <Module oim of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721969> <BEA-149060> <Module oim of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:21 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149721969> <BEA-149059> <Module xlWebApp of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722062> <BEA-149060> <Module xlWebApp of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722062> <BEA-149059> <Module iam-async-mdb.jar of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722094> <BEA-149060> <Module iam-async-mdb.jar of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722094> <BEA-149059> <Module dataobjects-ejb.jar of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722141> <BEA-149060> <Module dataobjects-ejb.jar of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722141> <BEA-149059> <Module iam-ejb.jar of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722156> <BEA-149060> <Module iam-ejb.jar of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722156> <BEA-149059> <Module empty.jar of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722156> <BEA-149060> <Module empty.jar of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722156> <BEA-149059> <Module weblogic.xml.registry.XMLModule of application oim [Version=11.1.1.3.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Info> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722156> <BEA-149060> <Module weblogic.xml.registry.XMLModule of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server oim_server1.>
####<Dec 23, 2010 4:15:22 PM PST> <Error> <Deployer> <IAM11G> <oim_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1293149722172> <BEA-149231> <Unable to set the activation state to true for the application 'oim [Version=11.1.1.3.0]'.
Any suggestions on how to fix this error
Thanks

2 things to check:
1. Have you set the CLASSPATH correctly in the Weblogic->Server Start?
2. Are all the required jar files present?

Problems installing Axis with WLS 8.1

I'm having problems installing Apache Axis with WLS 8.1.
I'm totally new to WLS, so this may be at the heart of the problem.
I install Axis as per the installation instructions.
These are the steps I followed:
1. Installed the axis directory to
C:\bea\weblogic81\samples\domains\examples\applications\axis2. Added xml-apis.jar and xercesImpl.jar to the AXISCLASSPATH ( the complete AXISCLASSPATH is
C:\axis-1_2RC2\lib\wsdl4j.jar;C:\axis-1_2RC2\lib\axis-ant.jar;C:\axis-1_2RC2\lib\commons-discovery.jar;C:\axis-1_2RC2\lib\commons-logging.jar;C:\axis-1_2RC2\lib\jaxrpc.jar;C:\axis-1_2RC2\lib\log4j.properties;C:\axis-1_2RC2\lib\log4j-1.2.8.jar;C:\axis-1_2RC2\lib\saaj.jar;C:\axis-1_2RC2\lib\axis.jar;C:\javasoft\javamail-1.3.2\mail.jar;C:\javasoft\javamail-1.3.2\lib\smtp.jar;C:\javasoft\javamail-1.3.2\lib\mailapi.jar;C:\javasoft\javamail-1.3.2\lib\pop3.jar;C:\javasoft\javamail-1.3.2\lib\imap.jar;C:\javasoft\jaf-1.0.2\activation.jar;C:\javasoft\Xerces\xerces-2_5_0\xercesImpl.jar;C:\javasoft\Xerces\xerces-2_5_0\xml-apis.jar)3.Added weblogic.xml file to C:\bea\weblogic81\samples\domains\examples\applications\axis\WEB-INF\weblogic.xmlas per instructions with <prefer-web-inf-classes>true</prefer-web-inf-classes> 4. Started the examples server.
5. I then tried to validate the installation as per intructions using <a href="http://localhost:7001/axis"></a>
Everything looks OK with the Axis start page displayed.
6. I then tried happyaxis.jsp . All needed components are present with saaj.jar being picked up from :
Found SAAJ API (javax.xml.soap.SOAPMessage) at C:\bea\weblogic81\samples\domains\examples\examplesServer\.wlnotdelete\extract\examplesServer__appsdir_axis_dir_axis\jarfiles\WEB-INF\lib\saaj.jar7. I'm missing optional component xmlsec.jar
8. Now the trouble starts!!!
pretty much anything I try now comes back with:
AXIS error
Sorry, something seems to have gone wrong... here are the details:
Exception - java.lang.NullPointerExceptionI get this if I try:
<a href="http://localhost:8080/axis/services/Version?method=getVersion"></a>
or
<a href="http://localhost:7001/axis/services/AdminService?wsdl"></a>
or
<a href="http://localhost:7001/axis/services/Version?wsdl"></a>
So, what's going wrong? I cant think what to do next. Please help! I need this to work fairly urgently.
Nigel
PS. here's the NP exception in detail
java.lang.NullPointerException
        at weblogic.xml.jaxp.ChainingEntityResolver.popEntityResolver(ChainingEn
tityResolver.java:61)
        at weblogic.xml.jaxp.RegistryDocumentBuilder.setEntityResolver(RegistryD
ocumentBuilder.java:168)
        at org.apache.axis.utils.XMLUtils.releaseDocumentBuilder(XMLUtils.java:2
35)
        at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:312)
        at org.apache.axis.utils.XMLUtils.StringToElement(XMLUtils.java:485)
        at org.apache.axis.AxisFault.addFaultDetail(AxisFault.java:654)
        at org.apache.axis.AxisFault.addHostname(AxisFault.java:888)
        at org.apache.axis.AxisFault.addHostnameIfNeeded(AxisFault.java:877)
        at org.apache.axis.AxisFault.initFromException(AxisFault.java:280)
        at org.apache.axis.AxisFault.<init>(AxisFault.java:181)
        at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
        at org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:487)
        at org.apache.axis.transport.http.QSWSDLHandler.invoke(QSWSDLHandler.jav
a:62)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.axis.transport.http.AxisServlet.processQuery(AxisServlet.j
ava:1132)
        at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:233
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
        at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:301)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1006)
        at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:419)
        at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:315)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6718)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
121)
        at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3764)
        at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2644)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

I'm doing exactly the same thing (adding the xerces jars to my web-inf/lib), but happyaxis.jsp is saying the jar I'm using is invalid as follows:
Error: Invalid version of SAAJ API found in D:\bea\weblogic81\server\lib\webservices.jar. Make sure that Axis' saaj.jar precedes D:\bea\weblogic81\server\lib\webservices.jar in CLASSPATH.
Axis will not work.
Maybe this worked in a previous release/SP? I'm using 8.1SP3. I've read some other post saying you cannot override stuff in the weblogic.jar, so I've tried to add the jars to the pre_classpath, which resolves the issue but I get a soap fault related to this thread. Any ideas?
Thanks,
Lou
My weblogic.xml looks as follows:
<weblogic-web-app>
<jsp-descriptor>

<jsp-param>
<param-name>jspServlet</param-name>
<param-value>weblogic.servlet.WlwJSPServlet</param-value>
</jsp-param>
<jsp-param>
<param-name>debug</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
<url-match-map>
weblogic.servlet.utils.SimpleApacheURLMatchMap
</url-match-map>
</weblogic-web-app>

EJB Deployment Descriptors not deploying to WLS

Hi,
We're using Eclipse 3.4.1 with the OEPE to target WLS 10.3 with Java 6/JEE 1.4 on a Windows XP Professional development machine.
We have an EJB 2.1 project as part of a larger EAR. The beans (all stateless session beans) and associated interfaces and deployment descriptors within are maintained manually for internal reasons; we do not rely on EJBGen or XDoclet or anything like that to manage these. We are NOT using any annotations in these EJBs, as is the default when you create a bean. Instead we rely on weblogic-ejb-jar.xml and ejb-jar.xml.
We're having an issue where deploying to the local Weblogic server instance fails with the following error displaying in the Eclipse console:
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'xxxxxxx'.>
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(xxxxxxxEJB.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation..
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
java.io.IOException: No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:199)
     at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
     at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     Truncated. see log file for complete stacktrace
We DO have multiple beans defined, but it seems that WLS just isn't aware of them due to the lack of a deployment descriptor. It appears that Eclipse/OEPE is not copying the ejb-jar.xml and weblogic-ejb-jar.xml files to the build directory when the project is build:
xxxxxEJB
|-- ejbModule
|.....|-- META-INF
|.....|.....|-- ejb-jar.xml
|.....|.....|-- MANIFEST.MF
|.....|.....|-- weblogic-ejb-jar.xml
|.....|-- com (etc., .java files)
|-- build
......|-- classes
............|-- META-INF
............|......|-- MANIFEST.MF
............|-- com (etc, .class files)
Other notes:
- Cleaning the project does not help.
- Starting a new workspace does not help.
- It works under Eclipse 3.3.2 with the Europa version of OEPE.
- Explicitly exporting an EJB Jar file DOES include the two deployment descriptors (just not deploying to the embedded test server we've defined in our Servers view)
Any ideas? This seems like either a bug in the OEPE, or maybe WTP.

Yes, I have a simple EJB2.1 project with hand-crafted EJB remote/home interfaces/classes and deployment descriptors. Also tried Clean/Rebuild and manually delete
files under /build/classes.
Here are my descriptors files:
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
     <display-name>TestEJB</display-name>
<enterprise-beans>
<session>
<display-name>HelloSessioin</display-name>
<ejb-name>HelloSession</ejb-name>
<home>sessions.HelloSessionHome</home>
<remote>sessions.HelloSession</remote>
<ejb-class>sessions.HelloSessionBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
<security-identity>
<use-caller-identity/>
</security-identity>
</session>
</enterprise-beans>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloSession</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<jndi-name>ejb.HelloSessionRemoteHome</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Did you check if there is any error/warning in Error Log view?

New EJB 2.0 Persistence Engine Supports WLS 6.1

ObjectFrontier today made available its latest version of FrontierSuite.
FrontierSuite is a powerful JCA compliant persistence engine and a Model
Driven Architecture (MDA) based platform for designing, developing and
deploying both Java and J2EE applications. FrontierSuite for J2EE platform
supports both EJB 1.1 and EJB 2.0.
FrontierSuite's CMP can be plugged to industry leading EJB 2.0 compliant
Application Servers and improve performance by up to 5000%. New features
include EJB 2.0 CMP support for WebLogic 6.1 application server, support for
additional databases and much more .....;
More information can be found on the web site at
http://www.objectfrontier.com/index.html
Some of the highlights of FrontierSuite are:
- Easily build new Java/J2EE applications, Reverse Engineer or incorporate
our state of the art persistence engine to your existing applications.
- Full Support for EJB 2.0 (PDF2).
- BMP/CMP O-R Mapping.
- JMS based Distributed Cache.
- Customizable XML encoders and decoders.
- Integrated with a host of Modeling Tools, IDE and J2EE Application
Servers.
- JCA Compliant with ability to persist data across ERP's, CRM's, RDBM's
etc.
- 100% Java, Standards based and compliant with Model Drive Architecture.
Shirish Shetty

I'm sending the stack trace error on WLPI side.
Is important to say that the functionality on Webservice is done correctly, When
Webservice ends and sends SOAP message to WLPI this error comes up.
Thanks&Regards
"Mauricio Del Moral" <[email protected]> wrote:
>
Hi,
I hope somebody can help me with this, very urgent!
We implement a Workflow using WLI 2.0, on this process we need to call
a WebService
message style on WLs6.1 hosted by another Company.
After searching for something we found a plug-in to use with Weblogic
process
integrator but this is just for a RPC-style webservice, can anyone have
solved
something like that.
Could I implement an EJB on the process side that call the webservice
without
compatibility problems.
Thanks&Regards.
Mauricio Del Moral
[WLI&WS.txt]

Migration from J2EE RI to WLS 6.0

Hi Everybody,
I'm new to WLS. So far I have been using J2EE RI to develop and deploy my
applications. Due to my experience with J2EE RI's deployment tool for
packaging, I would like to know, if there is any tool or simple approach to
convert generated .ear file from RI format to WLS' one?
Thanks in advance
Mohammad Kargar

Better you can go with IDOC, thsi is best method to transfer data from SAP to SAP.
Thanks
Yogesh

Problem with JNDI in WLS 5.1

Hi all,
i have a problem with JNDI in WLE 5.1.
i am accessing an LDAP on another machine running Netscape Directory Server.
The host URL is ldap://myhost:65535/o=marco, c=fi
i am always getting back the following exception:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.
WLInitialContextFactory. Root exception is java.lang.ClassCastException: weblog
ic.jndi.WLInitialContextFactory
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
58)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242
at javax.naming.InitialContext.init(InitialContext.java:218)
at javax.naming.InitialContext.<init>(InitialContext.java:194)
and my code is this:
Hashtable _environment = new Hashtable();
try {
environment.put(Context.INITIALCONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
environment.put(Context.PROVIDERURL, "ldap://myhost:65535");
if ((principal!=null) || (credentials!=null)) {
environment.put(Context.SECURITYAUTHENTICATION, "simple");
environment.put(Context.SECURITYPRINCIPAL, principal);
environment.put(Context.SECURITYCREDENTIALS, credentials);
context = new InitialContext(environment);
parser = context.getNameParser(initialCtxFactory);
} catch(Exception e) {
e.printStackTrace();
can anyone help me please??
thanx in advance
marco

Take out the "weblogic.jndi.WLInitialContextFactory" and add the respective factory NAME..
environment.put(Context.INITIALCONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
Cheers,
Naggi
Senthil Kumar S wrote:
http://weblogic.com/docs51/classdocs/API_jndi.html#delegate
Marco wrote:
Hi all,
i have a problem with JNDI in WLE 5.1.
i am accessing an LDAP on another machine running Netscape Directory Server.
The host URL is ldap://myhost:65535/o=marco, c=fi
i am always getting back the following exception:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.
WLInitialContextFactory. Root exception is java.lang.ClassCastException: weblog
ic.jndi.WLInitialContextFactory
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
58)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242
at javax.naming.InitialContext.init(InitialContext.java:218)
at javax.naming.InitialContext.<init>(InitialContext.java:194)
and my code is this:
Hashtable _environment = new Hashtable();
try {
environment.put(Context.INITIALCONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
environment.put(Context.PROVIDERURL, "ldap://myhost:65535");
if ((principal!=null) || (credentials!=null)) {
environment.put(Context.SECURITYAUTHENTICATION, "simple");
environment.put(Context.SECURITYPRINCIPAL, principal);
environment.put(Context.SECURITYCREDENTIALS, credentials);
context = new InitialContext(environment);
parser = context.getNameParser(initialCtxFactory);
} catch(Exception e) {
e.printStackTrace();
can anyone help me please??
thanx in advance
marco--
http://www.net4tech.com

Passivation EJB statefull with PersistenceContextType.EXTENDED in WLS 12c

Hi guys,
I have one web app with some EJB stateful working under Weblogic 12c.
A snippet of code:
public abstract class CommonHibernateDao<T extends AbstractModel, K extends Serializable> {
     private static final Logger LOGGER = LoggerFactory.getLogger(GenericHibernateDao.class);
     @PersistenceContext(type = PersistenceContextType.EXTENDED)
     protected transient EntityManager em;
     protected transient Session session;
     @SuppressWarnings("unused")
     private Class<T> persistentClass;
// common method like save delete...
@Stateful(name = "myDao")
public class MyDaoImpl extends CommonHibernateDao<Pojo, Serializable> implements MyDao, Serializable {
// methods with specific querys
In Glassfish 3.1.2 works fine, but in Weblogic 12c not.
What is happened?
When in Weblogic 12c the passivation the EJB throw one exception:
Message: <BEA-010024> <Error occurred during passivation: java.io.NotSerializableException: weblogic.persistence.ExtendedPersistenceContextWrapper
Stack: at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at java.util.HashSet.writeObject(HashSet.java:267)
     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)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at weblogic.ejb.container.swap.PassivationUtils.write(PassivationUtils.java:101)
     at weblogic.ejb.container.swap.DiskSwap.write(DiskSwap.java:173)
     at weblogic.ejb.container.manager.StatefulSessionManager.swapOut(StatefulSessionManager.java:1582)
     at weblogic.ejb.container.cache.LRUCache.put(LRUCache.java:149)
     at weblogic.ejb.container.manager.StatefulSessionManager.create(StatefulSessionManager.java:1246)
     at weblogic.ejb.container.manager.StatefulSessionManager.createBean(StatefulSessionManager.java:1313)
     at weblogic.ejb.container.internal.StatefulEJBLocalHomeImpl.createBeanAndReturnPK(StatefulEJBLocalHomeImpl.java:112)
     at weblogic.ejb.container.internal.StatefulSessionBeanReferenceImpl.getBusinessObject(StatefulSessionBeanReferenceImpl.java:39)
     at com.oracle.injection.integration.EjbDescriptorAdapter$EjbInstanceManagerAdapter.getEjbInstance(EjbDescriptorAdapter.java:236)
     at com.oracle.injection.provider.weld.WeldEjbServicesAdapter.resolveEjb(WeldEjbServicesAdapter.java:45)
     at org.jboss.weld.bean.SessionBean.createReference(SessionBean.java:406)
     at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.<init>(EnterpriseBeanProxyMethodHandler.java:69)
     at org.jboss.weld.bean.SessionBean.create(SessionBean.java:293)
     at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:61)
     at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:630)
     at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:691)
     at org.jboss.weld.injection.ParameterInjectionPoint.getValueToInject(ParameterInjectionPoint.java:120)
     at org.jboss.weld.injection.MethodInjectionPoint.getParameterValues(MethodInjectionPoint.java:217)
     at org.jboss.weld.injection.MethodInjectionPoint.invoke(MethodInjectionPoint.java:111)
     at org.jboss.weld.util.Beans.callInitializers(Beans.java:712)
     at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:701)
     at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1$1.proceed(ManagedBean.java:156)
     at com.oracle.injection.provider.weld.WeldInjectionServicesAdapter.aroundInject(WeldInjectionServicesAdapter.java:88)
     at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:45)
     at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1.work(ManagedBean.java:152)
     at org.jboss.weld.bean.ManagedBean$FixInjectionPoint.run(ManagedBean.java:126)
     at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.inject(ManagedBean.java:148)
     at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:285)
     at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:61)
     at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:630)
     at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:657)

I got exactly the same issue with Weblogic 11g (10.3.6)
Could anybody take a look ?

EJB Migration Problem (WLS 9.2 = WLS 10.3.2)

Similar Messages

Maybe you are looking for