Injecting ejb impossible using deployment descriptor ?

Hi.
I wanted to inject an EJB reference into a JSF manged bean. @EJB annotation worked, but then I tried <ejb-reb> and <injection-target> and EJB reference wasn't injected.
Looking at the specification, it seems that this is not supported. Is there any other possibility or am I forced to use annotations?

Similar Messages

The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing

Hello,
I want to create web service from ejb but everytime I want to do it, I get the following error:
I'm using NWDS 7.2 and JDK 1.6
[004]Deployment aborted
Settings
SDM host : XXX
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/XXXX/LOCALS1/Temp/temp3760382784932063822XXXWSProjectEar.ear
Result
=> deployment aborted : file:/C:/DOCUME1/XXX/LOCALS1/Temp/temp3760382784932063822XXX/WSProjectEar.ear
Aborted: development component 'XXXWSProjectEar'/'sap.com'/'localhost'/'2011.01.06.15.48.31'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/XXXWSProjectEar.. Reason: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing. ; nested exception is: com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Can anyone tell me why am I getting this error.
Thnx for your help.
Best regards.

Hello Decio Junior,
Actually yes, I resolved my problem.
I'm developing an EJB 3.0 project. I'm using NWDS 7.2 and JDK 1.6 as I said.
The problem is that my server was using JDK 1.4 and that was the problem.
EJB 1.1 and 2.1 need ejb-jar.xml but EJB 3.0 use the annotations instead.
Check your server JDK Version. It should be JDK 1.5 or higher.
Something else that you should check, in your project properties :
In the Build PATH : Use JDK 1.5
In the Java Compiler : Set the java compiler compliance level to 1.6 and check use default compliance settings
Hope it would help.
If you need more explanations, I'm here
Good luck.

EJB references in deployment descriptors and weblogic heuristic on resolving links

There are two different ways to lookup home interfaces using JNDI.
1. Query JNDI tree at runtime using some initial context.
2. Use <ejb-ref> in deployment descriptor for all the refrenced EJBs and then
use initCtxt.lookup(java:comp/env/BeanHomeName).
The second approach is recommended as most of the EJB vendors resolve these referenced
EJBs at deployment time and it becomes much faster as compare to lookup in JNDI
as EJB refrences or links can bypass querying the JNDI.
Does anyone know if Weblogic (5.1 sp9 or higher) resolves these links at deployment
time or not?

Hi Sami,
Run your question by the folks in the EJB newsgroup and see if they can
offer some assistance:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.ejb
Thanks,
Bruce
sami titi wrote:
>
Bruce,
Thanks for your prompt reply. We have resorted to using a startup servlet much
like we do in CA. However, we're still faced with the second issue which is related
to not being able to lookup the EJB after it has been included in an EAR file
now. Is there any setting we're missing?
Thanks
Sami
Bruce Stephens <[email protected]> wrote:
Hello,
Please correct me if I'm not understanding your question, but you are
looking for an easy way to pass initialization parameters to your
webservice? This is not currently supported, however it is on the wish
list for the next major release.
The workaround is to use a handler or read your init params from a
file. If you backend is java class, then you can put file loading:
1. in the constructor
2. in init() method if you java class implement
javax.xml.rpc.server.ServiceLifecycle
Regards,
Bruce

Referencing EJB on remote server AND using deployment descriptor

We're using Weblogic 6.1sp2 under Windows 2000.
We have a web application on server A and several EJBs running on server B -
some of these may in the future be moved to different servers.
We would like to ensure that this only requires reconfiguring the deployment
descriptors.
In our web app, we access the EJB's like this:
AccountHome accHome = (AccountHome) (new
InitialContext()).lookup("java:comp/env/ejb/AccountHome")
- we then map ejb/AccountHome to the JNDI name in the weblogic.xml file in
the web app - the JNDI name will usually (but not always) be the class name
of the implementing class, e.g. system.billing.accounting.AccountHome
However, to make this work when the EJB is on server B, we must put a
jndi.properties file in the server A classpath containing
java.naming.provider.url=t3://server_b:7001/
to point to server B.
Now, this makes ALL JNDI lookups on server A go to server B - this is not
what we want. Especially not in the case where some EJB's move to server C -
B and C may be in separate clusters and will not be clustering the JNDI
tree. Also, other web applications on the server will need to go to
different servers.
Alternatively, we could specify a property set in the InitialContext
constructor with a provider url. But in that case, the mapping from
web.xml/weblogic.xml is apparently not applied - or rather, if we look up
"java:comp/env/ejb/AccountHome", weblogic maps it to
"system.billing.accounting.AccountHome" and then tries to look it up on the
local machine, server A.
If we look up "system.billing.accounting.AccountHome", it does correctly
look it up on the server specified in the provider url and finds the entry.
However, this would mean that we would have to specify the exact jndi name.
In addition, we would have to hard-code the server name for each lookup.
An alternative would be to "copy" the JNDI entries from server B to server A
(or to some other shared, global JNDI registry). But these would need to be
kept in sync - especially since server B is really a cluster, where
different servers may come online at different times and register their EJBs
as clusterable, so the stubs would need to be continously updated.
My best idea is to bypass the whole web.xml/weblogic.xml mapping scheme and
just add our own config file with stuff like
<mappings>
<map entry="java:comp/env/ejb/AccountHome">
<jndi-properties>
java.naming.provider.url=t3://server_b:7001/
java.naming.security.principal=jndiuser
java.naming.security.credentials=mysecretpassword
</jndi.properties>
<jndi-name>sysmte.billing.accounting.AccountHome</jndi-name>
</map>
</mappings>
We then need to wrap all the lookups in our own lookup mechanism which first
checks the config file to find any mappings.
However, this seems like reinventing the wheel and will also confuse most
deployment tools etc.
Does anybody have any suggestions where we
1. Don't put a jndi.properties file in the server classpath
2. Lookup ejb's using "java:comp/env/ejb/SomeEJB" - not the JNDI name.
3. Don't hardcode the server names in the application - but potentially
in the deployment descriptor.
4. Can look up different EJB's on different machines
Niels Harremoës

There is an article on dev2dev that may explain what you are seeing...
http://dev2dev.bea.com/articlesnews/discussion/thread.jsp?thread=142
HTH
dwfa
"Niels Ull Harremoës" <[email protected]> wrote in message
news:[email protected]...
It turns out that we can make it work by entering the url of the server in
the weblogic.xml entry - e.g. instead of having
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/AccountHome</ejb-ref-name>
<jndi-name>system.billing.accounting.AccountHome</jndi-name>
</ejb-reference-description>
</reference-descriptor>
we enter
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/AccountHome</ejb-ref-name>
<jndi-name>t3://server_b:7001/system.billing.accounting.AccountHome</jndi-na
me>
</ejb-reference-description>
</reference-descriptor>
However, we are unsure on whether this will establish a new JNDIconnection
to server_b on every lookup? And it's not documented anywhere?
Does anybody have any other suggestions?
"Niels Ull Harremoës" <[email protected]> wrote in message
news:[email protected]...
We're using Weblogic 6.1sp2 under Windows 2000.
We have a web application on server A and several EJBs running on serverB -
some of these may in the future be moved to different servers.
We would like to ensure that this only requires reconfiguring thedeployment
descriptors.
In our web app, we access the EJB's like this:
AccountHome accHome = (AccountHome) (new
InitialContext()).lookup("java:comp/env/ejb/AccountHome")
- we then map ejb/AccountHome to the JNDI name in the weblogic.xml file
in
the web app - the JNDI name will usually (but not always) be the classname
of the implementing class, e.g. system.billing.accounting.AccountHome
However, to make this work when the EJB is on server B, we must put a
jndi.properties file in the server A classpath containing
java.naming.provider.url=t3://server_b:7001/
to point to server B.
Now, this makes ALL JNDI lookups on server A go to server B - this is
not
what we want. Especially not in the case where some EJB's move to serverC -
B and C may be in separate clusters and will not be clustering the JNDI
tree. Also, other web applications on the server will need to go to
different servers.
Alternatively, we could specify a property set in the InitialContext
constructor with a provider url. But in that case, the mapping from
web.xml/weblogic.xml is apparently not applied - or rather, if we look
up
"java:comp/env/ejb/AccountHome", weblogic maps it to
"system.billing.accounting.AccountHome" and then tries to look it up onthe
local machine, server A.
If we look up "system.billing.accounting.AccountHome", it does correctly
look it up on the server specified in the provider url and finds theentry.
However, this would mean that we would have to specify the exact jndiname.
In addition, we would have to hard-code the server name for each lookup.
An alternative would be to "copy" the JNDI entries from server B to
server
A
(or to some other shared, global JNDI registry). But these would need tobe
kept in sync - especially since server B is really a cluster, where
different servers may come online at different times and register theirEJBs
as clusterable, so the stubs would need to be continously updated.
My best idea is to bypass the whole web.xml/weblogic.xml mapping schemeand
just add our own config file with stuff like
<mappings>
<map entry="java:comp/env/ejb/AccountHome">
<jndi-properties>
java.naming.provider.url=t3://server_b:7001/
java.naming.security.principal=jndiuser
java.naming.security.credentials=mysecretpassword
</jndi.properties>
<jndi-name>sysmte.billing.accounting.AccountHome</jndi-name>
</map>
</mappings>
We then need to wrap all the lookups in our own lookup mechanism whichfirst
checks the config file to find any mappings.
However, this seems like reinventing the wheel and will also confuse
most
deployment tools etc.
Does anybody have any suggestions where we
1. Don't put a jndi.properties file in the server classpath
2. Lookup ejb's using "java:comp/env/ejb/SomeEJB" - not the JNDIname.
3. Don't hardcode the server names in the application - butpotentially
in the deployment descriptor.
4. Can look up different EJB's on different machines
Niels Harremoës

Ejb accessing the deployment descriptor

My ejb needs to be able to access the deployment descriptor to retrieve some user information needed to connect to a web service. What is the best way to do this? I know servletts can do this, and if necessary, I could have my servlet retrieve the info and pass it to the bean, but I was hoping to avoid this.
Thanks
Matt

Well, sure I think that is easy. In your <entity> or <session> deployment descriptor you can have:
<env-entry>
<env-entry-name>WebServiceLogins</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>su, dan, bob, steve, richard, suzie, carla</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>WebServicePasswords</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>drs100, vfdds2, ajk14, pass411, richard23, q4lty, uo738ww1</env-entry-value>
</env-entry>
Then in your intial-context in your session or entity ejb.....
InitialContext ic = new InitialContext();
String logins = (String) ic.lookup("java:comp/env/WebServiceLogins");
String passwords = (String) ic.lookup("java:comp/env/WebServicePasswords");

Using deployment descriptor authentication

Hello,
I'm working on a web application and want to have a login for anyone that accesses the service. Is it possible to use the deployment descriptor to implement security but using my own authentication method? What I want to do is something like this; have my web.xml similar to this:
<security-constraint>
<web-resource-collection>
<web-resource-name>all private</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<form-login-page>/login.jsp</form-login-page>
</login-config>
But, in my login.jsp, instead of having <form action="j_security_check" ...
I'll do something like <form action="tryLogin" ... and I'll implement my own login method that will use HttpSession to validate/invalidate the session. The reason I'm trying to do things this way is that I want to have username/password pairs stored on mySQL on my server. I am using the struts framework and the latest version of Tomcat. If anyone knows if this would work or if there is an easier way to do this please let me know!! Thanks!

Yup. It can be done having "tryLogin" as a servlet/jsp which retrives the username and pwd from the request object and connects to db for validating the same

EJB 2.1 Deployment Descriptor tags

Hi all, where can i find a good explanation on the EJB 2.1 Deployment Descrptor tags? I can see in the specification but that explanation on the XML Schema is not so good to understand nor to read.
I thank any tip or url to visit.
Giovani

http://www.orionserver.com/docs/ejb-jar.xml.html
This should help you get started.
Also you could start reading the spec to understand more about anything.
http://java.sun.com/products/ejb/docs.html
Follow the link to the Specification.
Vijay

Setting an Authentication Level for a WS using Deployment Descriptor Files

Hi
I'm developing WS with authentication level BASIC but I have some problem deploying it.
I read from https://cw.sdn.sap.com/cw/docs/DOC-106319 how to setting authentication level using annotation, but I cannot use annotation because my WS are cross-platform (they can be executed on SAP NetWeaver AS, JBoss, IBM WebSphere).
My WS is based on a stateless EJB Session 2.1.
My ejb-jar contains security-role-ref.
<?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">
     <enterprise-beans>
          <session id="AsyncOrd10">
               <description>AsyncOrd10</description>
               <ejb-name>AsyncOrd10</ejb-name>
               <local-home>com.dat.now.ws.ord.AsyncOrd10Home</local-home>
               <local>com.dat.now.ws.ord.AsyncOrd10</local>
               <service-endpoint>com.dat.now.ws.ord.AsyncOrd10WS</service-endpoint>
               <ejb-class>com.dat.now.ws.ord.AsyncOrd10EJB</ejb-class>
               <session-type>Stateless</session-type>
               <transaction-type>Container</transaction-type>
               <resource-ref id="AsyncOrd10Ref">
                    <description>Reference to the DataSource used by AsyncOrd10</description>
                    <res-ref-name>jdbc/AsyncOrd10</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <res-auth>Container</res-auth>
               </resource-ref>
               <security-role-ref id="SecurityRoleRef_AsyncOrd10">
                    <role-name>everyone</role-name>
                    <role-link>everyone</role-link>
               </security-role-ref>
          </session>
     </enterprise-beans>
     <assembly-descriptor id="assembly-descriptor_ID">
          <security-role id="SecurityRole_everyone">
               <role-name>everyone</role-name>
          </security-role>
          <security-role id="SecurityRole_sysadm">
               <role-name>sysadm</role-name>
          </security-role>
          <method-permission id="MethodPermission_AsyncOrd10">
               <role-name>everyone</role-name>
               <method id="MethodElement_AsyncOrd10">
                    <ejb-name>AsyncOrd10</ejb-name>
                    <method-name>*</method-name>
               </method>
          </method-permission>
          <container-transaction id="container-transaction_AsyncOrd10">
               <method id="AsyncOrd10_methods">
                    <ejb-name>AsyncOrd10</ejb-name>
                    <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
     </assembly-descriptor>
</ejb-jar>

for JBoss I can set in the jboss.xml the auth-method (under the port-component)
<?xml version="1.0" encoding="UTF-8"?>
<jboss>
     <security-domain>java:/jaas/absolut</security-domain>
     <enterprise-beans>
          <session>
               <ejb-name>AsyncOrd10</ejb-name>
               <local-jndi-name>com.dat.now.ws.ord.AsyncOrd10</local-jndi-name>
               <port-component>
               <port-component-name>AsyncOrd10WSPort</port-component-name>
                    <port-component-uri>AsyncOrd10</port-component-uri>
                    <auth-method>BASIC</auth-method>
               </port-component>
               <resource-ref>
                    <res-ref-name>jdbc/AsyncOrd10</res-ref-name>
                    <res-type>javax.sql.DataSource</res-type>
                    <jndi-name>java:/now</jndi-name>
               </resource-ref>
          </session>
     </enterprise-beans>
</jboss>
For IBM WebSphere I should use an additional step in the deploy
Maybe I missing something in the ejb-j2ee-engine.xml ?
this is it :
<?xml version="1.0" encoding="UTF-8"?>
<ejb-j2ee-engine>
     <enterprise-beans>
          <enterprise-bean>
               <ejb-name>AsyncOrd10</ejb-name>
               <jndi-name>com.dat.now.ws.ord.AsyncOrd10</jndi-name>
               <resource-ref>
                    <res-ref-name>jdbc/AsyncOrd10</res-ref-name>
                    <res-link>now</res-link>
               </resource-ref>
          </enterprise-bean>
     </enterprise-beans>
<security-permission>
<security-role-map>
<role-name>everyone</role-name>
<server-role-name>all</server-role-name>
</security-role-map>
<security-role-map>
<role-name>sysadm</role-name>
<server-role-name>administrators</server-role-name>
</security-role-map>
</security-permission>
</ejb-j2ee-engine>
Thanks

Deploy ejbs without using deployment tool in J2EE server

Hi,
IS there any way to deploy ejbs in J2EE without using the deployment tool? I am using the j2ee 1.2.1.
Thanks,
Nipa

When I was in my companies Java Boot Camp (6 week fulltime training in Java technologies) the class was split about 75/25 with 75% of the class using a deployment tool (I think it was WebGain). The other 25% did not use a deployment tool. I was one of the 25%.
What we did was write a Perl script that took care of all the necessary deployment steps. It has been awhile, and I no longer work for that company, but I'll try and dig up some of those scripts. (Can't promise I'll find them!)
BTW, the 25% group deployed more EJBs with less problems than those using the deployment tool...

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?

How To Define Security in the deployment descriptor for an ejb

Hi All
Pls help!
I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
Thanks
Yours in Java

Hi All
Pls help!
I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
Thanks
Yours in Java

DPL8007: Unsupported deployment descriptors element message-destination?

Hi All,
I am not able to run a working Java EE 5 JMS tutorial in jdk1.6.0_25, GF3.1 (bundled with Netbeans 7.0 on Windows XP) despite having re-created the whole project from scratch. Below is the code snippets of various components of the project:
C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\src\java\com\ensode\mdb\MessageReceiverBean.java
@MessageDriven(mappedName = "jms/myQueue", activationConfig = {
    @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
public class MessageReceiverBean implements MessageListener {
    @Override
    public void onMessage(Message message) {
        TextMessage textMessage = (TextMessage) message;
        try {
            System.out.println("Received message:" + textMessage.getText());
        } catch (JMSException ex) {
            Logger.getLogger(MessageReceiverBean.class.getName()).log(Level.SEVERE, null, ex);
C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProjectApplicationClient\src\java\com\ensode\jms
public class Main {
    @Resource(name = "jms/myQueue")
    private static Queue myQueue;
    @Resource(name = "jms/myQueueConnectionFactory")
    private static ConnectionFactory myQueueConnectionFactory;
    public static void main(String[] args) throws JMSException {
        new Main().sendJMSMessageToMyQueue("NetBeans makes JMS trivial!");
    private Message createJMSMessageForjmsMyQueue(Session session,
            Object messageData) throws JMSException {
        TextMessage textMessage = session.createTextMessage();
        textMessage.setText((String) messageData);
        return textMessage;
    private void sendJMSMessageToMyQueue(Object messageData) throws
            JMSException {
        Connection connection = null;
        Session session = null;
        try {
            connection = myQueueConnectionFactory.createConnection();
            session = connection.createSession(false,
                    javax.jms.Session.AUTO_ACKNOWLEDGE);
            MessageProducer messageProducer = session.createProducer(myQueue);
            messageProducer.send(createJMSMessageForjmsMyQueue(session,
                    messageData));
        } finally {
            if (session != null) {
                session.close();
            if (connection != null) {
                connection.close();
C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\setup\glassfish-resources.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources PUBLIC "-//GlassFish.org//DTD GlassFish Application Server 3.1 Resource Definitions//EN" "http://glassfish.org/dtds/glassfish-resources_1_5.dtd">
<resources>
<admin-object-resource enabled="true" jndi-name="jms/myQueue" object-type="user" res-adapter="jmsra" res-type="javax.jms.Queue">
    <property name="Name" value="myQueue"/>
</admin-object-resource>
<connector-resource enabled="true" jndi-name="jms/myQueueConnectionFactory" object-type="user" pool-name="jms/myQueueConnectionFactory">
    <description/>
</connector-resource>
<connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.QueueConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/myQueueFactoryPool" ping="false" pool-resize-quantity="2" pooling="true" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
<connector-resource enabled="true" jndi-name="jms/myQueueFactory" object-type="user" pool-name="jms/myQueueFactoryPool"/>
<connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.ConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/myQueueConnectionFactory" ping="false" pool-resize-quantity="2" pooling="true" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
</resources>Yet it was met with the following exception which appears to be an unsupported deployment descriptor generated by Netbeans 7.0:
_GF3.1 server log_
WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
_Application Client Outpu
t_10/05/2011 2:59:45 AM com.sun.enterprise.deployment.util.ComponentValidator accept
WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
com.sun.enterprise.container.common.spi.util.InjectionException: Exception attempting to inject Unresolved Message-Destination-Ref jms/[email protected]@null into class com.ensode.jms.Main
Caused by: javax.naming.NamingException: Lookup failed for 'java:comp/env/jms/myQueue' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]]glassfish-resources.xml used to reside in C:\Documents and Settings\jack\JMSEnterpriseProject\ setup\ sun-resources.xml back in GF2.1.
Deployment was successful which resulted in the following resources created:
Connector Resources => jms/myQueueConnectionFactory, jms/myQueueFactory.
Connector Connection Pools => jms/myQueueFactoryPool, jms/myQueueConnectionFactory.
Admin Object Resources => jms/myQueue.
Your assistance would be very much appreciated.
Thanks,
Jack

Hi,
The same unsupported deployment descriptor persists despite having removed C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\setup\glassfish-resources.xml with the following exception:
10/05/2011 11:41:22 PM com.sun.enterprise.deployment.util.ComponentValidator accept
WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
10/05/2011 11:41:28 PM org.hibernate.validator.util.Version <clinit>
INFO: Hibernate Validator 4.1.0.Final
10/05/2011 11:41:28 PM org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA
INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter: Version: 4.5 (Build 29-b) Compile: Wed Feb 9 22:53:30 PST 2011
10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter starting: broker is REMOTE, connection mode is TCP
10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter Started:REMOTE
com.sun.enterprise.container.common.spi.util.InjectionException: Exception attempting to inject Unresolved Message-Destination-Ref jms/[email protected]@null into class com.ensode.jms.Main
     at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:698)
     at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.inject(InjectionManagerImpl.java:468)
     at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectClass(InjectionManagerImpl.java:215)
     at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectClass(InjectionManagerImpl.java:207)
     at org.glassfish.appclient.client.acc.AppClientContainer$ClientMainClassSetting.getClientMainClass(AppClientContainer.java:619)
     at org.glassfish.appclient.client.acc.AppClientContainer.getMainMethod(AppClientContainer.java:511)
     at org.glassfish.appclient.client.acc.AppClientContainer.completePreparation(AppClientContainer.java:405)
     at org.glassfish.appclient.client.acc.AppClientContainer.prepare(AppClientContainer.java:319)
     at org.glassfish.appclient.client.AppClientFacade.prepareACC(AppClientFacade.java:278)
     at org.glassfish.appclient.client.acc.agent.AppClientContainerAgent.premain(AppClientContainerAgent.java:76)
     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 sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323)
     at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
Caused by: javax.naming.NamingException: Lookup failed for 'java:comp/env/jms/myQueue' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]]
     at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:518)
     at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:597)
     ... 15 more
Caused by: javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]
     at com.sun.enterprise.naming.impl.JavaURLContext.lookup(JavaURLContext.java:242)
     at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:498)
     ... 18 more
Caused by: java.lang.NullPointerException
     at javax.naming.InitialContext.getURLScheme(InitialContext.java:269)
     at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:318)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
     at com.sun.enterprise.naming.util.JndiNamingObjectFactory.create(JndiNamingObjectFactory.java:82)
     at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:772)
     at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:740)
     at com.sun.enterprise.naming.impl.JavaURLContext.lookup(JavaURLContext.java:172)It is running on Windows 7 as opposed to XP earlier on.
Is it possible that this is a bug since all JMS resources have been declared without using deployment descriptor at all?
Thanks,
Jack

Deployment descriptor "weblogic.xml" is malformed. in managed server

Hi All,
          Appreciate if anyone can help.
          I have set up a cluster containing two nodes - one local and other
          remote machine on weblogic 8.1.4
          then i install my application this cluster setup its working fine.
          for my requirement i upgrade the the weblogic version from 8.1.4 to
          8.1.6 .
          i upgrade through the smart update from the bea site . i upgraded both
          the node.
          i started the admin server.it started with no issue.
          my problem comes when i start the my managed server on the cluster .it
          gives me this exception.
          <HTTP> <BEA-101296> <Unable to load the default compiler class
          "com.sun.tools.javac.Main". Using the default javac compiler to compile
          JSPs.>
          i checked the classpath it has the same jdk that i used for 8.1.4
          (jdk1.4.05 from sun.)
          should i used new jdk that comes with the upgrade package of 8.1.6 like
          (jdk1.4.11)
          my class path having the weblogic jar also.
          this is my class path.:
          E:\bea\weblogic81\server\lib\weblogic.jar and other my application
          jars.
          complete exception it is shown like :
          <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
          <Application:
          'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
          Module: 'Nexaweb': Public ID references the old version of the Servlet
          DTD. You must change the public ID in web.xml file to "-//Sun
          Microsystems, Inc.//DTD Web Application 2.3//EN".>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
          <[Application:
          'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?br>Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
          Check against the DTD: org.xml.sax.SAXParseException: The content of
          element type "weblogic-web-app" must match
          "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?t*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?ontainer-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?ap?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
          (line 26, column 20).>
          Compiler class: 'com.sun.tools.javac.Main', not found
          java.lang.ClassNotFoundException: com.sun.tools.javac.Main
          at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
          at java.security.AccessController.doPrivileged(Native Method)
          at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
          at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
          at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
          at java.lang.Class.forName0(Native Method)
          at java.lang.Class.forName(Class.java:141)
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?6)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
          <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
          will have better performance if it is enabled. To enable
          call-by-reference, set the enable-call-by-reference element to True in
          the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
          <Failed to initialize the application Xellerate due to error
          weblogic.management.ApplicationException: prepare failed for
          xlBackOfficeBeans.jar
          Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
          EJBModule(xlBackOfficeBeans.jar,status=NEW)
          Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
          Compiler class: 'com.sun.tools.javac.Main', not found
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
          found
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          weblogic.management.ApplicationException: prepare failed for
          xlBackOfficeBeans.jar
          Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
          EJBModule(xlBackOfficeBeans.jar,status=NEW)
          Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
          Compiler class: 'com.sun.tools.javac.Main', not found
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
          found
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1658)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          ><Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
          <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
          to initialize due to failed deployments.>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
          <The deployment framework was unable to resume accepting requests.>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
          <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
          deployment framework was unable to resume accepting
          requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
          is unable to initialize due to failed deployments.>
          hope the scope of the questions is not too broad. Kindly let me know
          if you need more information.
          Thanks a lot.

ram ram <> wrote:
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
Add tools.jar from your Java installation to the classpath.
Bart
Schelstraete Bart
http://www.schelstraete.org
http://www.mqseries.be

Deployment descriptor "weblogic.xml" is malformed.

Hi All,
Appreciate if anyone can help.
I have set up a cluster containing two nodes - one local and other
remote machine on weblogic 8.1.4
then i install my application this cluster setup its working fine.
for my requirement i upgrade the the weblogic version from 8.1.4 to
8.1.6 .
i upgrade through the smart update from the bea site . i upgraded both
the node.
i started the admin server.it started with no issue.
my problem comes when i start the my managed server on the cluster .it
gives me this exception.
<HTTP> <BEA-101296> <Unable to load the default compiler class
"com.sun.tools.javac.Main". Using the default javac compiler to compile
JSPs.>
i checked the classpath it has the same jdk that i used for 8.1.4
(jdk1.4.05 from sun.)
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
complete exception it is shown like :
<Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
<Application:
'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
Module: 'Nexaweb': Public ID references the old version of the Servlet
DTD. You must change the public ID in web.xml file to "-//Sun
Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
<[Application:
'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?r',
Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
Check against the DTD: org.xml.sax.SAXParseException: The content of
element type "weblogic-web-app" must match
"(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?gnment*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?er?,container-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?tch-map?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?oot?,wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
(line 26, column 20).>
Compiler class: 'com.sun.tools.javac.Main', not found
java.lang.ClassNotFoundException: com.sun.tools.javac.Main
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:406)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
<Call-by-reference is not enabled for the EJB 'JMSBean'. The server
will have better performance if it is enabled. To enable
call-by-reference, set the enable-call-by-reference element to True in
the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
<Failed to initialize the application Xellerate due to error
weblogic.management.ApplicationException: prepare failed for
xlBackOfficeBeans.jar
Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
EJBModule(xlBackOfficeBeans.jar,status=NEW)
Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
Compiler class: 'com.sun.tools.javac.Main', not found
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
found
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for
xlBackOfficeBeans.jar
Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
EJBModule(xlBackOfficeBeans.jar,status=NEW)
Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
Compiler class: 'com.sun.tools.javac.Main', not found
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
found
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1658)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
<BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
to initialize due to failed deployments.>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
<The deployment framework was unable to resume accepting requests.>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
<BEA-000342> <Unable to initialize the server: [Deployer:149601]The
deployment framework was unable to resume accepting
requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
is unable to initialize due to failed deployments.>
hope the scope of the questions is not too broad. Kindly let me know
if you need more information.
Thanks a lot.

ram ram <> wrote:
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
Add tools.jar from your Java installation to the classpath.
Bart
Schelstraete Bart
http://www.schelstraete.org
http://www.mqseries.be

[EJB:011055]Error deploying the EJB with error that JNDI name already inuse

Hi,
I have written a trivial application consisting of 4 stateless beans and 1 MDB. The ear is developed from some code generator tool and works fine if I directly deploy on weblogic server 812.
But in order to learn Weblogic Workshop I created new Application and EJB project. Then I imported the EJB jar and provided other source files.
From Weblogic Workshop I could generate the ear successfully. But while trying to deploy the ear I get the following exception :
<16/03/2005 10:02:38 PM GMT+05:30> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application hsbc.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for MCAppBEAN.jar
Module: MCAppBEAN.jar Error: Exception preparing module: EJBModule(MCAppBEAN.jar,status=NEW)
Unable to deploy EJB: StatelessBean from MCAppBEAN.jar:
<b>[EJB:011055]Error deploying the EJB 'StatelessBean(Application: hsbc, EJBComponent: MCAppBEAN.jar)', the JNDI name 'StatelessBeanHSBC' is already in use. You mu
st set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor for this EJB before it can be deployed.</b> at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2556)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
<b>Can someone tell where have I made the mistake?</b>
thanks in advance.

Try to undeploy and un target the applcation via WLS console and they try to deploy it again. Or just try to redeploy it.

Injecting ejb impossible using deployment descriptor ?

Similar Messages

Maybe you are looking for