• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

[EJB:011055]Error deploying the EJB

 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi lijoy..plz help me out...
Hi all,
This is my first request to all of u...it is very urjent
here is my problem...
i am trying to deploy EJB 2.0 CMP bean in web logic 8.1.
i have create the data source "CMPDBSource" and JNDI "ISUIJNDI" in weblogic ,it is created nicely, the same datasource and JNDI i am using in my EJB Bean in weblogic-cmp-rdbms-jar.xml and weblogic-ejb-jar.xml.
now when i deploy my bean,weblogic says that the JNDI name alreay exist....i have tried with diff JNDI name but every time error is same.
put some light on this...plz
here is my error
Exception:weblogic.management.ApplicationException: prepare failed for CMPAccount Module: CMPAccount Error: Exception preparing module: EJBModule(CMPAccount,status=NEW) Unable to deploy EJB: CMPBean from CMPAccount.jar: [EJB:011055]Error deploying the EJB 'CMPBean(Application: CMPAccount, EJBComponent: CMPAccount)', the JNDI name 'ISUIJNDI' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor for this EJB before it can be deployed.
[Deployer:149033]preparing application CMPAccount on SphereServer
[Deployer:149033]failed application CMPAccount on SphereServer
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application CMPAccount on SphereServer.: Exception:weblogic.management.ApplicationException: prepare failed for CMPAccount Module: CMPAccount Error: Exception preparing module: EJBModule(CMPAccount,status=NEW) Unable to deploy EJB: CMPBean from CMPAccount.jar: [EJB:011055]Error deploying the EJB 'CMPBean(Application: CMPAccount, EJBComponent: CMPAccount)', the JNDI name 'ISUIJNDI' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor for this EJB before it can be deployed.
plz let me know,where i am going wrong ?
 
Ranch Hand
Posts: 1871
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
Check out the config.xml file. Remove all references to the JNDI name that is creating the problem, or rename them appropriately.
The problem is that your config.xml file is really messed up and you need to rectify that.
 
Rahul Mahindrakar
Ranch Hand
Posts: 1871
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
Also try removing any temporary files that have been created.
 
Ashraf Ali Syed
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
here is my config.xml file
<Domain ConfigurationVersion="8.1.0.0" Name="ISUIAppServer">
<Server ListenAddress="" ListenPort="7001" Name="SphereServer"
NativeIOEnabled="true" ReliableDeliveryPolicy="RMDefaultPolicy" ServerVersion="8.1.1.0">
<SSL Enabled="false" HostnameVerificationIgnored="false"
IdentityAndTrustLocations="KeyStores" Name="SphereServer"/>
</Server>
<JMSFileStore Directory="rmfilestore" Name="FileStore"/>
<WSReliableDeliveryPolicy DefaultRetryCount="10"
DefaultTimeToLive="60000" Name="RMDefaultPolicy" Store="FileStore"/>
<Security Name="ISUIAppServer"
PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm" RealmSetup="true"/>
<EmbeddedLDAP
Credential="{3DES}+jq9zyLaL7Evvt89QPfaASUj+f3RNmm5CPZx6P0dJ00=" Name="ISUIAppServer"/>
<SecurityConfiguration
Credential="{3DES}lmZlakOcoeXqNqGF31EA1PpimcYNfQZsntdz2mXvXSGI1ZIm8ZX99TS3oEacnr0CsjHGsPXFhm+8aZRbStdGbnYh44umLisk"
Name="ISUIAppServer" RealmBootStrapVersion="1"/>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<FileRealm Name="wl_default_file_realm"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<JMSServer Name="WSStoreForwardInternalJMSServerSphereServer"
Store="FileStore" Targets="SphereServer">
<JMSQueue CreationTime="1075376594015"
JNDIName="jms.internal.queue.WSStoreForwardQueue"
JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSStoreForwardQueueSphereServer"/>
<JMSQueue CreationTime="1075376594546"
JNDIName="jms.internal.queue.WSDupsEliminationHistoryQueue"
JNDINameReplicated="false" Name="WSInternaljms.internal.queue.WSDupsEliminationHistoryQueueSphereServer"/>
</JMSServer>
<JDBCConnectionPool DriverName="COM.ibm.db2.jdbc.app.DB2Driver"
Name="ISUIDataPool" Password="{3DES}QMX7E/Hme5rvrvw8uWjvkQ=="
Properties="user=db2admin;DatabaseName=PRODUCT"
Targets="SphereServer"
TestTableName="SQL SELECT COUNT(*) FROM SYSIBM.SYSTABLES" URL="jdbc b2 RODUCT"/>
<JDBCTxDataSource JNDIName="ISUIJNDI" Name="CMPDBSource"
PoolName="ISUIDataPool" Targets="SphereServer"/>
</Domain>
--------------------------------------------------------------------------
I think every thing is ok here....
even i created new server configuration using weblogic configuration wizard
and try to deploy but still the same problem.
Rahul...
u also mention to remove temp files,what do u mean by this..kindly explain.
 
Ranch Hand
Posts: 1646
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Ashraf Ali Syed:
I think every thing is ok here....


Same here. The problem it seems is that you are specifying a JNDI name *for the bean's home* that is clashing -- not the data source. In the deployment descriptor, you specify the data source to use. This doesn't publish any new JNDI objects; it just looks them up.
What gets published in JNDI are your home stubs. If you're using both local and remote, make sure the JNDI names are different. Make sure their JNDI names are different from all other objects going into JNDI. It looks like you are using the data source name as the home stub name, thus producing a clash.
 
Ashraf Ali Syed
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you so much for your help,it has been deployed successfully.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic