AQ Adapter in 11g with weblogic

Hi all
I m looking to work on some sample AQ adapter in 11g with weblogic. is it possible?
if any one provide some light on this? some examples please?
thanks
Srikanth

Does the example from the guide doesnt work for you ?
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10231/adptr_aq.htm
Oracle AQ Adapter Use Cases

Similar Messages

Cannot start managed server domains for SOA Suite 11g with Weblogic

Hi all,
I have installed Oracle 11gR1 (11.1.1.3) SOA Suite with Oracle 11gR1 (10.3.3) Weblogic on Oracle Enterprise Linux 5 (64 bit OS) platform and cannot get the managed server domains to start due to the following
authentication errors.
$ sh startManagedWebLogic.sh soa_server1 http://xxx.xxx.xx.xxx:7001
<Dec 14, 2010 11:12:44 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 14, 2010 11:12:44 AM EST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 14, 2010 11:12:44 AM EST> <Notice> <LoggingService> <BEA-320400> <The log file /weblogic1033/oracle/user_projects/domains/dummy_domain/servers/soa_server1/logs/soa_server1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Dec 14, 2010 11:12:44 AM EST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /weblogic1033/oracle/user_projects/domains/dummy_domain/servers/soa_server1/logs/soa_server1.log00005. Log messages will continue to be logged in /weblogic1033/oracle/user_projects/domains/dummy_domain/servers/soa_server1/logs/soa_server1.log.>
<Dec 14, 2010 11:12:44 AM EST> <Notice> <Log Management> <BEA-170019> <The server log file /weblogic1033/oracle/user_projects/domains/dummy_domain/servers/soa_server1/logs/soa_server1.log is opened. All server side log events will be written to this file.>
<Dec 14, 2010 11:12:46 AM EST> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjp
<Dec 14, 2010 11:12:46 AM EST> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:891341 fatal store error> kodo.jdo.FatalDataStoreException: error result.
weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:891341 fatal store error> kodo.jdo.FatalDataStoreException: error result
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:465)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
There are 1 nested errors:
weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Dec 14, 2010 11:12:46 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 14, 2010 11:12:46 AM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Dec 14, 2010 11:12:46 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Caused By: netscape.ldap.LDAPException: error result (49)
at weblogic.ldap.EmbeddedLDAPConnection.bind(EmbeddedLDAPConnection.java:639)
at weblogic.ldap.EmbeddedLDAPConnection.determineFailover(EmbeddedLDAPConnection.java:2204)
at weblogic.ldap.EmbeddedLDAPConnection.connect(EmbeddedLDAPConnection.java:366)
at com.bea.common.ldap.LDAPConfiguration.getConnection(LDAPConfiguration.java:78)
at com.bea.common.ldap.LDAPStoreQuery.executeQuery(LDAPStoreQuery.java:199)
Truncated. see log file for complete stacktrace
>
<Dec 14, 2010 11:12:46 AM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 14, 2010 11:12:46 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
When I remove boot.properties file from $MIDDLEWARE_HOME/user_projects/domains/dummy_domain/servers/AdminServer/security
I am able to start AdminServer, however, the ManagedServers do not start. When I try to use boot.properties file for AdminServer it will not start neither will Managed Servers.
If anyone has idea how to resolve the issue, please let me know. I have tried using the following commands to change the passwords for ManagedServers to no success:
cd /weblogic1033/oracle/user_projects/domains/dummy_domain/security
java -cp /weblogic1033/oracle/wlserver_10.3/server/lib/weblogic.jar:$CLASSPATH weblogic.security.utils.AdminAccount newuser newpassword .
It works but fails to change the password. I also tried changing settings for LDAP and security in the admin console to no success in resolving this issue.

Take a backup of ldap folder under servers/managedServerName/data folder and delete those and thn restart managed servers,

Linux Startup script for Forms Services 11g with Weblogic

Hi,
Does anybody know where I can find info about the startup script process for Forms Service 11g under linux? I can't find it googling it... I think I have to startup weblogic first... isnt it ? or opmnctl works alone ?
In 10g we just need to set env vars and then "opmnctl startall" and if we need enterprise manager "emctl start iasconsole" ... what about on 11g?
Regards
Ricardo

You can start directly the WLS_FORMS without starting the Admin and Node manager ..
I think if you go through this link , you will get more information ..
Re: Forms 11g - Installation steps for a developer machine

How to know report server name in oracle forms and reports with weblogic server 10.3.5

Hello Experts, I am new in oracle forms and reports.I have installed Oracle forms 11g with weblogic server 10.3.5 at windows 7.Forms and reports are working well.But I want to call a report from an oracle form button press trigger. For This I need to know the my report server name which i dont know.Please tell me how can I know my report server name.

I want to call a report from an oracle form button press trigger. For This I need to know the my report server name
You can find the name of the standalone reports server in $ORACLE_INSTANCE/config/ReportsServerComponent.
Or you can use Fusion Middleware Control Console, normally at http://<machine name>:7001/em

Is it possible to use SOA Suite 11g with JDeveloper's integrated WebLogic?

Is it possible to use SOA Suite 11g with JDeveloper's integrated WebLogic? Or do you have to install an external WebLogic?
Thanks for help.
Edited by: user7722720 on 07-Dec-2011 02:04

Hi
By default, NO it is NOT possible to deploy any SOA Applications on Integrated Weblogic Server that comes with JDeveloper. This integrated weblogic server is very light weight basic weblogic server with single domain (only 1 AdminServer) to deploy a standard J2EE, ADF Applications like EJBs, WebApps, WebServices, ADF Apps etc. BUT SOA (having BPEL, BPMs etc ) cannot be deployed.
There is an option to upgrade this integrated weblogic server and install SOA on top of this. Like download soa installer that matches with your JDeveloper version and install soa on top of this weblogic. BUT I strongly do not recommend this, because you will not be able to upgrade iin future to the latest versions.
Yes, its always better to install the standalone Weblogic Server that matches with your JDeveloper version. Then install SOA on top of this Weblogic Server. Then create RCU Schemas in any Oracle Database. Run config wizard and create a SOA Domain. Now integrate this in your JDeveloper to deploy any soa applications.
Make sure that JDeveloper, Weblogic Server, SOA Software, RCU all these versions should match and they should be same.
Thanks
Ravi Jegga

SOA Suite 11g and its compatibility with Weblogic

Hi ,
I have two questions:
1. From where do I download the SOA Suite 11g --Link to the download?
2.If SOA suite 11g can be installed on weblogic. I understand that SOA suite 10.1.3.4 is compatible with weblogic 9.2 but need some inputs on the SOA Suite11g!
Cheers
Prabal

Prabal,
Did you get an answer or we have to wait for the official release till July-1-2009.
Thanks,
Rahul

Issue with Weblogic services in Linux OBIEE 11G

Hello All,
I have a OBI 11G set up on a linux OS.I am facing a issue with weblogic service.
Whenever I am trying to start the Admin server from command line using its .sh , it is starting successfully.
But whenever I am closing that Linux session or coming out of the Admin server log , this service is getting stopped on its own.
OBI is working perfectly when that Linux session and Admin server log is intact, but as soon as i close either of them Admin server shut itself down.
Please any help on this will be appreciated.
Thanks,
Bhavnesh

Hi Bhavnesh.
Try this way and let me know the outcome.
nohup ./startWeblogic.sh -Dweblogic.management.username=Username -Dweblogic.management.password=password & tail -f nohup.out
Mark if helps,
Thanks,

Toplink 10.1.3.1 compatible with weblogic 11g server

When deploying to weblogic 11g server using OEPE, I get the following error:
java.lang.VerifyError: (class: com/co/proj/toplink/TimeTrackProject, method: <init> signature: ()V) Incompatible argument to function
     at com.co.db.core.DBConnFactory.initSessionsPoolExternal(DBConnFactory.java:109)
     at com.co.db.core.DBConnFactory.initSessionsPoolExternal(DBConnFactory.java:66)
     at com.co.db.core.DBConnFactory.init(DBConnFactory.java:46)
     at com.co.db.core.DBConnInitializer.contextInitialized(DBConnInitializer.java:43)
     at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
     Truncated. see log file for complete stacktrace
TimeTrackProject extends Project class in toplink-10.3 jar.
Are there compatibility issues with weblogic 11g and toplink 10.1.3.1?

The older TopLink versions were not certified on the latest WebLogic releases. Oracle TopLink 11g (11.1.1.0.0) was certified on WebLogic 10.3.0 and 11gR1 (11.1.1.1.0) was included with WebLogic 10.1.3.1 as a system module. You may be experiencing a conflict between the included TopLink libraries and the older ones you built your application against. I would recommend rebuilding your application against the TopLink libraries shipped with WLS 10.3.1 and not including the older version.
If this is not an option then you would need to use an application classpath filer to ensure the TopLink libraries in the system module of WLS 10.3.1 are not used.
Doug

Inqmy resource adapter for SAP with Bea Weblogic Server

          Hi everybody,
          Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic server
          It works well with INQMY server, but with BEA I'm getting a lot of problems creating
          the connections.
          Thanks in advance.
          Xavi.


All,
          Here are the steps we (used for internal testing) had to perform to get
          IN-Q-MY adapter for SAP to work with WebLogic:
          The wli.adapter.inqmy.sapr3.spi package contains extensions to the
          In-Q-My J2EE Connector Architecture classes to overcome some limitations
          in the base implementation classes. To get around these issues, we had
          to extend their R3ManagedConnectionFactory, R3ConnectionManager, and
          R3ConnectionFactory classes.
          * The javax.resource.spi.ManagedConnectionFactory implementation
          does not over-ride the equals and hashCode methods correctly. This
          causes problems with WLS 6.1.
          * There is a bug in their javax.resource.spi.ConnectionManager
          implementation for non-managed uses of the adapter. Consequently, their
          adapter cannot be used in a non-managed scenario.
          * The javax.resource.cci.ConnectionFactory class does not support
          the getConnection() method that does not take any arguments (it throws a
          null pointer exception).
          I am attaching the classes discussed above.
          Cheers,
          Chris
          Torsten Friebe wrote:
          > Hi,
          >
          > does anybody know where to get a trail version - if one exists - of IN-Q-MY
          > application server or the resource adapter?
          >
          > Thanks, regards
          > Torsten
          >
          > "Xavi" <[email protected]> schrieb im Newsbeitrag
          > news:[email protected]...
          >
          >>Hi everybody,
          >>
          >>Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic
          >>
          > server
          >
          >>?
          >>
          >>It works well with INQMY server, but with BEA I'm getting a lot of
          >>
          > problems creating
          >
          >>the connections.
          >>
          >>Thanks in advance.
          >>Xavi.
          >>
          >>
          >
          >
          package wli.adapter.inqmy.sapr3.spi;
          import java.io.Serializable;
          import javax.resource.ResourceException;
          import javax.resource.cci.Connection;
          import javax.resource.cci.ConnectionSpec;
          import javax.resource.spi.ConnectionManager;
          import javax.resource.spi.ConnectionRequestInfo;
          import javax.resource.spi.ManagedConnection;
          import javax.resource.spi.ManagedConnectionFactory;
          import com.inqmy.r3adapter.R3ConnectionSpec;
          import com.inqmy.r3adapter.R3ManagedConnectionFactory;
          * Extends the In-Q-My implementation to allow for getConnection() with no
          * connection spec, i.e. use the default configured connection parameters.
          public class R3ConnectionFactory
          extends com.inqmy.r3adapter.R3ConnectionFactory
          implements com.bea.connector.IProxyMarker {
          private R3ConnectionSpec m_cspec;
          public R3ConnectionFactory(ConnectionManager cm, R3ManagedConnectionFactory mcf)
          throws ResourceException {
          super(cm, mcf);
          String strClientNumber = mcf.getClientNumber();
          if (strClientNumber == null) {
          throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+mcf);
          String strLanguage = mcf.getLanguage();
          if (strLanguage == null) {
          throw new javax.resource.spi.IllegalStateException("Language not set for "+mcf);
          String strUserName = mcf.getUserName();
          if (strUserName == null) {
          throw new javax.resource.spi.IllegalStateException("UserName not set for "+mcf);
          String strPassword = mcf.getPassword();
          if (strPassword == null) {
          throw new javax.resource.spi.IllegalStateException("Password not set for "+mcf);
          m_cspec = new R3ConnectionSpec(strClientNumber, strLanguage, strUserName, strPassword);
          public Connection getConnection(ConnectionSpec connectionSpec)
          throws ResourceException {
          if (connectionSpec == null) connectionSpec = m_cspec;
          return super.getConnection(connectionSpec);
          package wli.adapter.inqmy.sapr3.spi;
          import java.io.Serializable;
          import javax.resource.ResourceException;
          import javax.resource.spi.ConnectionManager;
          import javax.resource.spi.ConnectionRequestInfo;
          import javax.resource.spi.ManagedConnection;
          import javax.resource.spi.ManagedConnectionFactory;
          * Extends the In-Q-My implementation to over-ride the
          * allocateConnection method to return a CCI connection vs. a ManagedConnection
          public class R3DefaultConnectionManager
          implements ConnectionManager, Serializable {
          public R3DefaultConnectionManager() {}
          public Object
          allocateConnection(ManagedConnectionFactory mcf, ConnectionRequestInfo cri)
          throws ResourceException {
          ManagedConnection mc = mcf.createManagedConnection(null, cri);
          return mc.getConnection(null, cri);
          package wli.adapter.inqmy.sapr3.spi;
          import javax.resource.spi.ConnectionManager;
          import javax.resource.spi.ConnectionRequestInfo;
          import javax.resource.spi.ManagedConnection;
          import javax.security.auth.Subject;
          * Extends the In-Q-My implementation to get around some problems encountered
          * while running on WebLogic:
          * <ul>
          * <li>Must over-ride default implementation of equals and hashCode method</li>
          * <li>Needed to provide my version of the CCI ConnectionFactory</li>
          * <li>Needed to provide my version of the default ConnectionManager for the
          * non-managed scenario use case</li>
          * </ul>
          public class R3ManagedConnectionFactory
          extends com.inqmy.r3adapter.R3ManagedConnectionFactory {
          private int m_iHashCode;
          transient private com.inqmy.r3adapter.R3ConnectionRequestInfo t_cri = null;
          public R3ManagedConnectionFactory() {
          super();
          java.rmi.server.UID uid = new java.rmi.server.UID();
          m_iHashCode = uid.hashCode();
          public Object createConnectionFactory() {
          // need to install our own default connection manager because In-Q-My
          // version causes a ClassCastException in CCI ConnectionFactory
          // getConnection
          return createConnectionFactory(new R3DefaultConnectionManager());
          public ManagedConnection createManagedConnection(Subject subject, ConnectionRequestInfo cri)
          throws javax.resource.ResourceException {
          // need to check for null on the ConnectionRequestInfo object because the
          // In-Q-My R3ManagedConnection ctor does not check for null
          if (cri == null) cri = getDefaultConnectionRequestInfo();
          return new com.inqmy.r3adapter.R3ManagedConnection(this, subject, cri);
          public Object createConnectionFactory(ConnectionManager connectionManager) {
          // need to supply a connection factory that can deal with getConnection
          // that does not take a ConnectionSpec
          try {
          return new R3ConnectionFactory(connectionManager, this);
          } catch (javax.resource.ResourceException re) {
          re.printStackTrace();
          throw new java.lang.IllegalStateException(re.getMessage());
          com.inqmy.r3adapter.R3ConnectionRequestInfo getDefaultConnectionRequestInfo()
          throws javax.resource.spi.IllegalStateException {
          if (t_cri == null) {
          String strClientNumber = this.getClientNumber();
          if (strClientNumber == null) {
          throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+this);
          String strLanguage = this.getLanguage();
          if (strLanguage == null) {
          throw new javax.resource.spi.IllegalStateException("Language not set for "+this);
          String strUserName = this.getUserName();
          if (strUserName == null) {
          throw new javax.resource.spi.IllegalStateException("UserName not set for "+this);
          String strPassword = this.getPassword();
          if (strPassword == null) {
          throw new javax.resource.spi.IllegalStateException("Password not set for "+this);
          t_cri = new com.inqmy.r3adapter.R3ConnectionRequestInfo(strClientNumber, strLanguage, strUserName, strPassword);
          return t_cri;
          public boolean equals(Object obj) {
          if (obj == null) return false;
          if (obj == this) return true;
          if (!this.getClass().isInstance(obj)) return false;
          R3ManagedConnectionFactory mcf = (R3ManagedConnectionFactory)obj;
          return compare(getClientNumber(), mcf.getClientNumber()) &&
          compare(getLanguage(), mcf.getLanguage()) &&
          compare(getUserName(), mcf.getUserName()) &&
          compare(getPassword(), mcf.getPassword()) &&
          compare(getServerName(), mcf.getServerName()) &&
          compare(getSystemNumber(), mcf.getSystemNumber());
          protected final boolean compare(final Object obj1, final Object obj2) {
          if (obj1 == obj2) return true;
          if (obj1 != null) {
          return obj1.equals(obj2);
          } else {
          if (obj2 == null) {
          return true;
          } else {
          return false;
          public int hashCode() { return m_iHashCode; }

Need Web Service implementation tutorial on SOA11g with weblogic 11g AppSer

Hi Experts,
I am new to webservice topic. I don't know ABCD of web service, but i got a task to implement webservice and need prepare xsd file to move 3 fields information from source system to target machine.
Note: Target system have webservice to capture 3 fields information but I need to prepare a web service to capture 3 fields information from log file (normal text file) through web service (from source system and later link same to target web service).
My task is to implement web service at source system to fetch 3 fileds data from log file and link to target machine web service.
Can any one help me out any basic information on it and apreciate if any one provide practical tutorial on web service creation using SAO 11g and weblogic 11g application server.
Thanks,
Phani

thanks you for your response and tutorial.
I need some more help, can you please help me out how to read data from log file to webservice
Note: Log file have a xml content but it is saved as .log file thru an third party application. Third party application does not have capability to store log file as xml but it istoring has .log file (normal text file) with XML content.
If you have any sample code, please provide the same
Thanks,
Phani

Oracle reports 11g with ADF weblogic

hi every body,
on our organization we have already weblogic with ADF support
we want to install oracle reports to our reporting issues
what you think using our already version of weblogic or using fresh weblogic is good
I want to figure which is the best choice so please help me
BR,
Alaa

Hi,
Yes Oracle forms and reports 11g needs weblogic to be installed first which creates a Middleware home .
Under that Middleware home you have to create a Forms & Reports home where in the respective binaries are installed.
Thanks,
Sharmela

How to start workin with WebLogic 11g

Hi!.
can anyone out there guide me with how to start working with Weblogic..
i have made a jsp page but cant deploy it.. actually i know how to on Weblogic 8 but not on this version of the S/W...
Please give a detailed guiding about where to paste the jsp , servelets ant other pages in my folder because i cant find out where i have to paste the files to deploy them... and i cant find the weblogic builder...
Please..

Developing and deploying of web applications/ Enterprise applications remains the same as in wls 81.
Please refer the following doc for deployment : http://download.oracle.com/docs/cd/E12839_01/web.1111/e13702/understanding.htm#i1051084
For developing web application pls refer : http://download.oracle.com/docs/cd/E12839_01/web.1111/e13712/basics.htm#i153628
Hope this helps.

Deploying J2E CA 1.0 Resource Adapter on 11g

I am currently only supplying an ra.xml file since I have not been able to get the same RAR file that worked with WLS 8 to install correctly on 11g with my weblogic-ra.xml. I receive the following error even though I do not supply a weblogic-ra.xml file as the error message states. Are 1.0 resource adapters supported? I have included a copy of the ra.xml at the bottom of message.
Any ideas?
Eric
<Nov 24, 2010 2:37:04 PM MST> <Error> <Deployer> <BEA-149265> <Failure occurred
in the execution of deployment request with ID '1290634624475' for task '0'. Err
or is: 'weblogic.application.ModuleException: A <jndi-name> is specified for the
resource adapter bean in weblogic-ra.xml, however no <resourceadapter-class> el
ement is specified in ra.xml'
weblogic.application.ModuleException: A <jndi-name> is specified for the resourc
e adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is
specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
>
<Nov 24, 2010 2:37:04 PM MST> <Warning> <Deployer> <BEA-149004> <Failures were d
etected while initiating deploy task for application 'BullHooXG8Line'.>
<Nov 24, 2010 2:37:04 PM MST> <Warning> <Deployer> <BEA-149078> <Stack trace for
message 149004
weblogic.application.ModuleException: A <jndi-name> is specified for the resourc
e adapter bean in weblogic-ra.xml, however no <resourceadapter-class> element is
specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
Truncated. see log file for complete stacktrace
>
<Nov 24, 2010 2:37:04 PM MST> <Error> <Console> <BEA-240003> <Console encountere
d the following error weblogic.application.ModuleException: A <jndi-name> is spe
cified for the resource adapter bean in weblogic-ra.xml, however no <resourceada
pter-class> element is specified in ra.xml
at weblogic.connector.deploy.ConnectorModule.prepare(ConnectorModule.jav
a:229)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:507)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:149)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.ja
va:1221)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.j
ava:367)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleMo
duleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(Deployme
ntStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(App
ContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.cr
eateAndPrepareContainer(ActivateOperation.java:207)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.do
Prepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.pr
epare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploym
entPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploy
mentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare
(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.pre
pare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallb
ackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTunin
gWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connector PUBLIC '-//Sun Microsystems, Inc.//DTD Connector 1.0//EN' 'http://java.sun.com/dtd/connector_1_0.d
td'>
<connector>
<display-name>HooXG8 Line NoTxn Adapter</display-name>
<vendor-name>Bull</vendor-name>
<spec-version>1.0</spec-version>
<eis-type>GCOS</eis-type>
<version>2.1</version>
<resourceadapter>
<managedconnectionfactory-class>com.bull.HooX.GcosManagedConnectionFactoryImpl</managedconnectionfactory-class
>
<connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
<connectionfactory-impl-class>com.bull.HooX.GcosConnectionFactory</connectionfactory-impl-class>
<connection-interface>javax.resource.cci.Connection</connection-interface>
<connection-impl-class>com.bull.HooX.GcosConnectionImpl</connection-impl-class>
<transaction-support>NoTransaction</transaction-support>
<config-property>
<description>IP name or address</description>
<config-property-name>ipAddress</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>DSA node name</description>
<config-property-name>dsaNode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Mailbox name</description>
<config-property-name>mailbox</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Protocol to use(EGATE, LINE, NONE)</description>
<config-property-name>protocol</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>LINE</config-property-value>
</config-property>

There should be a weblogic-ra.xml file in your deployment plan somewhere. The structure of the deployment plan is as follows:
somewhere/Plan.xml
somewhere/plan/META-INF/weblogic-ra.xml
The resource adapter does not support you specifying a <jndi-name> for the resource adapter. You can however specify <jndi-name> for the connection instances you create after deploying the adapter. If you have a <jndi-name> for the recource adapter, simply delete it from weblogic-ra.xml (also delete empty element such as <jndi-name></jndi-name> or <jndi-name /> ). Then update the adapter from the Deployments page in Admin console.
Here is my weblogic-ra.xml file:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-connector xmlns="http://xmlns.oracle.com/weblogic/weblogic-connector" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-connector http://xmlns.oracle.com/weblogic/weblogic-connector/1.0/weblogic-connector.xsd">
<native-libdir>C:\dev\wls_domains\domain1\lib</native-libdir>
<enable-access-outside-app>false</enable-access-outside-app>
<enable-global-access-to-classes>true</enable-global-access-to-classes>
<security></security>
<outbound-resource-adapter>
<default-connection-properties>
<pool-params></pool-params>
<logging></logging>
</default-connection-properties>
<connection-definition-group>
<connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
<default-connection-properties>
<pool-params></pool-params>
<logging>
<logging-enabled>false</logging-enabled>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>false</number-of-files-limited>
<file-count>7</file-count>
<file-size-limit>500</file-size-limit>
<rotate-log-on-startup>true</rotate-log-on-startup>
<log-file-rotation-dir></log-file-rotation-dir>
<rotation-time>00:00</rotation-time>
<file-time-span>24</file-time-span>
</logging>
</default-connection-properties>
<connection-instance>
<jndi-name>hoox</jndi-name>
<connection-properties>
<pool-params></pool-params>
<logging>
<log-filename>C:\dev\wls_domains\domain1\servers\AdminServer\logs\hoox.log</log-filename>
<logging-enabled>true</logging-enabled>
<rotation-type>bySize</rotation-type>
<number-of-files-limited>true</number-of-files-limited>
<file-count>7</file-count>
<file-size-limit>10000</file-size-limit>
<rotate-log-on-startup>false</rotate-log-on-startup>
<log-file-rotation-dir>C:\dev\wls_domains\domain1\servers\AdminServer\logs</log-file-rotation-dir>
<rotation-time>00:00</rotation-time>
<file-time-span>24</file-time-span>
</logging>
<properties>
<property>
<name>mailbox</name>
<value>XXXXXXXXXXXXXX</value>
</property>
<property>
<name>dsaNode</name>
<value>XXXXXXXXXXXXX</value>
</property>
<property>
<name>ipAddress</name>
<value>XXXXXXXXXXXXXXX</value>
</property>
<property>
<name>options</name>
<value>-TL FULL -MCMDSIZE 5</value>
</property>
<property>
<name>protocol</name>
<value>EGATE</value>
</property>
<property>
<name>serviceMapPath</name>
<value>C:\dev\wls_domains\domain1\lib\vdirmap.xml</value>
</property>
</properties>
</connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>

Deploy ADF 11g to WebLogic Server: Unmarshaller failed

Hello,
I have an IBM server which was built with an Intel Xeon CPU; and I run Solaris 10 on it.
It seems there is no WebLogc 10.3 package installer for Solaris x86 (SPARC only). So I must install WebLogic 10.2.
Does JDeveloper 11g support WebLogic 10.2 ? (I see only 10.3 when create an Application Server connection)
When I tried to deploy my ADF application to WebLogic Server (with the connection for WebLogic 10.3) from my computer, an exception occurred:
weblogic.management.DeploymentException: Unmarshaller failed
When I read the log file on the server, it said that there was an error in weblog-application.xml, related to the descriptor. (Sorry, I am not at the server right now; so I cannot write exactly what it said. If necessary, I'll post it later.)
I hope someone will help me to resolve this problem.
Thanks for reading my thread!

There are messages in the log file:
<1230546713435> <BEA-160197> <Unable to load descriptor /export/home/PhucNT/bea/wlserver_10.0/samples/domains/wl_server/./servers/examplesServer/upload/BKSync/app/BKSyncDeployment.ear/META-INF/weblogic-application.xml of module BKSyncDeployment.ear. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
     at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:333)
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:177)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     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:464)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-application@http://www.bea.com/ns/weblogic/weblogic-application
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
     ... 28 more
.>
####<Dec 29, 2008 5:31:53 PM ICT> <Error> <Deployer> <TLSolaris> <examplesServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1230546713523> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean BKSync. Error - weblogic.management.DeploymentException: Unmarshaller failed.
weblogic.management.DeploymentException: Unmarshaller failed
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     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:464)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-application@http://www.bea.com/ns/weblogic/weblogic-application
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
     at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:333)
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:177)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     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:464)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Dec 29, 2008 5:31:53 PM ICT> <Error> <Deployer> <TLSolaris> <examplesServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1230546713552> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1230546711085' for task '0'. Error is: 'weblogic.management.DeploymentException: Unmarshaller failed'
weblogic.management.DeploymentException: Unmarshaller failed
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     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:464)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-application@http://www.bea.com/ns/weblogic/weblogic-application
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
     at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:333)
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:177)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     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:464)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Dec 29, 2008 5:31:54 PM ICT> <Warning> <Deployer> <TLSolaris> <examplesServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1230546714489> <BEA-149004> <Failures were detected while initiating deploy task for application 'BKSync'.>
####<Dec 29, 2008 5:31:54 PM ICT> <Warning> <Deployer> <TLSolaris> <examplesServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1230546714490> <BEA-149078> <Stack trace for message 149004
weblogic.management.DeploymentException: Unmarshaller failed
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     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:464)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-application@http://www.bea.com/ns/weblogic/weblogic-application
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754)
     at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:333)
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:177)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:86)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:719)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1186)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:157)
     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:464)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

EJB 3.0 MDB deployment issue with weblogic 10.0

Hi there,
I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
Unable to deploy EJB: MessageBean from Message.jar:
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
     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)
     Truncated. see log file for complete stacktrace
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
     at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
     Truncated. see log file for complete stacktrace
>
Any help really appreciated. It's too urgent.
Thanks in advance,
Piyush

here is the code for my bean.
package com.ups;
import java.util.logging.Logger;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.EJBException;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
* Message-Driven Bean implementation class for: MessageBean
@MessageDriven(
          activationConfig = { @ActivationConfigProperty(
                    propertyName = "destinationType", propertyValue = "javax.jms.Queue"
public class MessageBean implements MessageListener {
     private MessageDrivenContext mdc;
* Default constructor.
public MessageBean() {
// TODO Auto-generated constructor stub
* @see MessageListener#onMessage(Message)
public void onMessage(Message message) {
     TextMessage tmsg = null;
try {
tmsg = (TextMessage) message;
System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
System.out.println ("The onMessage() is called");
} catch (JMSException e) {
e.printStackTrace( );
mdc.setRollbackOnly( );
catch (Throwable th) {
th.printStackTrace();
public void ejbRemove( )throws EJBException{
     System.out.println("ejbRemove() is executed >>>>>>>");
I have configured my JMS Distributed queue in the Weblogic.
If possible please provide more details so that I can get rid of this error as soon as possible.
Thanks for reply.
Piyush

AQ Adapter in 11g with weblogic

Similar Messages

Maybe you are looking for