cannot seems to configure sun app server

MyEclipse Archived

Application Servers and Deployment

This topic has 1 reply, 2 voices, and was last updated 19 years, 10 months ago by Riyad Kalla.

Viewing 2 posts - 1 through 2 (of 2 total)

Author

Posts
May 2, 2005 at 12:46 pm #228965 Reply

saavz
Member

hi,

I am using myeclipseIDe to do a project and i am have been having
problems with the deployment descriptor , the project used to work
well under NetBeans but now doesnt seem to be working now , i cant
access the ejb from a servlet, i am posting the deployment desriptor
and the error , please help.

<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE sun-ejb-jar PUBLIC “-//Sun Microsystems, Inc.//DTD Sun ONE
Application Server 7.0 EJB 2.0//EN”
“http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd”>

<!– Generated by XDoclet –>

<sun-ejb-jar>

<!–
To add any role mappings, add an Unparsed XML Entity file to
your XDoclet
merge directory called sunone-role-mappings.ent that contains the
<role-mapping> elements.
<!ELEMENT role-mapping (role-name, role-impl)>
<!ELEMENT role-impl (group*, user*)>
N.B. This is an Unparsed XML Entity file, rather than an XML Document,
since if there are multiple mappings it will not be well-formed.
–>

<enterprise-beans>

<ejb>
<ejb-name>Customer</ejb-name>

<jndi-name>ejb/Customer</jndi-name>
<resource-ref>
<res-ref-name>proj0638</res-ref-name>
<jndi-name>jdbc/proj0638</jndi-name>
</resource-ref>

</ejb>

<!–
To add any persistence manager descriptors, put an XML
Document named
sunone-pm-descriptors.xml in your XDoclet merge directory
containing the
<pm-descriptors> element.
–>

</enterprise-beans>
</sun-ejb-jar>

<?xml version=”1.0″ encoding=”UTF-8″?>
<web-app version=”2.4″
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/web-app_2_4.xsd”>
<servlet>
<description>This is the description of my J2EE component</description>
<display-name>test</display-name>
<servlet-name>FrontController</servlet-name>
<servlet-class>FrontController.FrontController</servlet-class>
</servlet>

<servlet-mapping>
<servlet-name>FrontController</servlet-name>
<url-pattern>/servlet/FrontController</url-pattern>
</servlet-mapping>
<ejb-local-ref>
<ejb-ref-name>ejb/Customer</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>CustomerEJB.CustomerLocalHome</local-home>
<local>Customer.CustomerSession</local>
<ejb-link>proj0638EJB.jar#Customer</ejb-link>

</ejb-local-ref>

</web-app>

<?xml version=”1.0″ encoding=”UTF-8″?>

<!DOCTYPE ejb-jar PUBLIC “-//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN” “http://java.sun.com/dtd/ejb-jar_2_0.dtd”>

<ejb-jar >

<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>

<enterprise-beans>

<!– Session Beans –>
<session >
<description><![CDATA[Description for Customer]]></description>
<display-name>Name for Customer</display-name>

<ejb-name>Customer</ejb-name>

<local-home>CustomerEJB.CustomerLocalHome</local-home>
<local>CustomerEJB.CustomerLocal</local>
<ejb-class>CustomerEJB.CustomerSession</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
<resource-ref>
<res-ref-name>jdbc/proj0638</res-ref-name>
<res-type>javax.sql.DataSource </res-type>
<res-auth>Container</res-auth>
</resource-ref>

</session>

<!–
To add session beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called session-beans.xml
that contains
the <session></session> markup for those beans.
–>

<!– Entity Beans –>
<!–
To add entity beans that you have deployment descriptor info for, add
a file to your XDoclet merge directory called entity-beans.xml
that contains
the <entity></entity> markup for those beans.
–>

<!– Message Driven Beans –>
<!–
To add message driven beans that you have deployment descriptor
info for, add
a file to your XDoclet merge directory called
message-driven-beans.xml that contains
the <message-driven></message-driven> markup for those beans.
–>

</enterprise-beans>

<!– Relationships –>

<!– Assembly Descriptor –>
<!–
To specify your own assembly descriptor info here, add a file to your
XDoclet merge directory called assembly-descriptor.xml that contains
the <assembly-descriptor></assembly-descriptor> markup.
–>

<assembly-descriptor >
<!–
To specify additional security-role elements, add a file in the merge
directory called ejb-security-roles.xml that contains them.
–>

<!– method permissions –>
<!–
To specify additional method-permission elements, add a file in the merge
directory called ejb-method-permissions.ent that contains them.
–>

<!– finder permissions –>

<!– transactions –>
<!–
To specify additional container-transaction elements, add a
file in the merge
directory called ejb-container-transaction.ent that contains them.
–>

<!– finder transactions –>

<!–
To specify an exclude-list element, add a file in the merge directory
called ejb-exclude-list.xml that contains it.
–>
</assembly-descriptor>

</ejb-jar>

[#|2005-05-02T13:23:12.171-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy]
Selecting file [
C:\Sun8\AppServer\domains\domain1\autodeploy\proj0638.ear ] for
autodeployment.|#]

[#|2005-05-02T13:23:12.250-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent
the event to instance:[ApplicationDeployEvent — undeploy proj0638]|#]

[#|2005-05-02T13:23:12.250-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status
of dynamic reconfiguration event processing:[success]|#]

[#|2005-05-02T13:23:12.359-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|in
application/module Node, handling of id = myeclipse.1114985100296
failed|#]

[#|2005-05-02T13:23:12.359-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|in
application/module Node, handling of id = myeclipse.1114985104656
failed|#]

[#|2005-05-02T13:23:12.703-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|in
application/module Node, handling of id = myeclipse.1114985100296
failed|#]

[#|2005-05-02T13:23:12.703-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|in
application/module Node, handling of id = myeclipse.1114985104656
failed|#]

[#|2005-05-02T13:23:12.859-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|WARNING
proj0638EJB.jar#Customer ejb-ref expected bean interface to be
Customer.CustomerSession and got CustomerEJB.CustomerLocal|#]

[#|2005-05-02T13:23:12.859-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|WARNING
proj0638EJB.jar#Customer ejb-ref assumed bean interface is now
CustomerEJB.CustomerLocal|#]

[#|2005-05-02T13:23:12.875-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109:
EJBC – START of EJBC for [proj0638]|#]

[#|2005-05-02T13:23:12.890-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Processing
beans …|#]

[#|2005-05-02T13:23:12.890-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110:
EJBC – END of EJBC for [proj0638]|#]

[#|2005-05-02T13:23:13.015-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|in
application/module Node, handling of id = myeclipse.1114985100296
failed|#]

[#|2005-05-02T13:23:13.015-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|in
application/module Node, handling of id = myeclipse.1114985104656
failed|#]

[#|2005-05-02T13:23:13.062-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total
Deployment Time: 859 msec, Total EJB Compiler Module Time: 15 msec,
Portion spent EJB Compiling: 1%
Breakdown of EJBC Module Time: Total Time for EJBC: 15 msec, CMP
Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI
Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]

[#|2005-05-02T13:23:13.609-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Deleted
previous deployment directory:
C:\Sun8\AppServer\domains\domain1\applications\j2ee-apps\proj0638_old|#]

[#|2005-05-02T13:23:13.609-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|deployed
with moduleid = proj0638|#]

[#|2005-05-02T13:23:13.609-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent
the event to instance:[ApplicationDeployEvent — deploy proj0638]|#]

[#|2005-05-02T13:23:13.671-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=11;|EJB5090:
Exception in creating EJB container
[javax.naming.InvalidNameException: Real JNDI name cannot be empty for
jdbc/proj0638]|#]

[#|2005-05-02T13:23:13.671-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=11;|Invalid
jndiName forappId=proj0638; moduleName=proj0638EJB_jar;
ejbName=Customer|#]

[#|2005-05-02T13:23:13.671-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=11;|jndiName=|#]

[#|2005-05-02T13:23:13.687-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=11;|LDR5004:
UnExpected error occured while creating ejb container
javax.naming.InvalidNameException: Real JNDI name cannot be empty for
jdbc/proj0638
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:493)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:1759)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:376)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:135)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:191)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:477)
at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:125)
at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:96)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:205)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:156)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:480)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:448)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:432)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:299)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:107)
at com.sun.enterprise.admin.server.core.mbean.config.ManagedServerInstance.multicastEvent(ManagedServerInstance.java:3880)
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:324)
at com.sun.enterprise.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:181)
at com.sun.enterprise.admin.server.core.mbean.config.AdminBase.invoke(AdminBase.java:86)
at com.sun.enterprise.admin.server.core.mbean.config.ConfigMBeanBase.invoke(ConfigMBeanBase.java:680)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.phasing.DeploymentService.multicastEvent(DeploymentService.java:341)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:284)
at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:115)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:74)
at com.sun.enterprise.deployment.phasing.DeploymentService.executePhases(DeploymentService.java:233)
at com.sun.enterprise.deployment.phasing.DeploymentService.deploy(DeploymentService.java:150)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:275)
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:324)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:287)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:280)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:221)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:228)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:823)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:282)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:471)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:367)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployApplication(AutoDeployer.java:346)
at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:167)
at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:344)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)
|#]

[#|2005-05-02T13:23:13.687-0400|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|CORE5021:
Application NOT loaded: [proj0638]|#]

[#|2005-05-02T13:23:13.687-0400|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM5603:Event
listener error [Error while loading application [proj0638]. Please
refer to the server log for more details. ]|#]

[#|2005-05-02T13:23:13.687-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status
of dynamic reconfiguration event processing:[listener_error]|#]

[#|2005-05-02T13:23:13.703-0400|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1075:Error
on listening event:[Error while loading application [proj0638]. Please
refer to the server log for more details. ]|#]

[#|2005-05-02T13:23:13.703-0400|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|Exception
while deploying :
com.sun.enterprise.deployment.backend.IASDeploymentException: Error
while loading application [proj0638]. Please refer to the server log
for more details.
com.sun.enterprise.deployment.backend.IASDeploymentException: Error
while loading application [proj0638]. Please refer to the server log
for more details.
.|#]

[#|2005-05-02T13:23:13.703-0400|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy]
Autodeploy failed :
C:\Sun8\AppServer\domains\domain1\autodeploy\proj0638.ear.|#]

thank you for any help you guys can give.
– System Setup ——————————-
Operating System and version: windows xp pro sp2
Eclipse version: 3.0.2
Eclipse build id: 200503110845
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*:
MyEclipse version:
Eclipse JDK version:
Application Server JDK version:
Are there any exceptions in the Eclipse log file?

If this is a DB related question please answer the following:

RDBMS vendor and version: pointbase 4.8
JDBC driver vendor and version, and access type (thin, type-2, etc):
Connection URL:
Eclipse error logs related to com.genuitec.eclipse.sqlexplorer packages:

May 2, 2005 at 4:50 pm #228987 Reply

Riyad Kalla
Member

Please take a look at this thread, this is a Sun Server config issue: http://swforum.sun.com/jive/thread.jspa?threadID=23069&messageID=56626

And if that doesn’t help, try this: http://www.google.com/search?hl=en&q=javax.naming.InvalidNameException%3A+Real+JNDI+name+cannot+be+empty&btnG=Google+Search
Author

Posts

Viewing 2 posts - 1 through 2 (of 2 total)