Jboss help!!!!

I want to configure Jboss in my eclipse. I'm currently using eclipse version 3.1.1 and jdk 1.4.1_01 version.
I copied JbossIDE and Easie Plugins (com.genuitec.eclipse.easie.jboss , com.genuitec.eclipse.easie.core).
I then tried to configure as given in the following site
http://www.laliluna.de/webprojects-eclipse-jbosside-tutorial-en.html
But on mentioning Jboss Home directory I get the following error
[JDK]: Could not locate tools.jar. Unexpected results may occur. Make sure that you have selected a jdk with its path pointing to its home directory not to its JRE
Following are the details i provided on clicking NEW (Jboss 3.2.x - pls see the link as i followed that)
Name: Jboss3.2.2 (name i have given)
Jboss 3.2.x Home Directory: D:\Jboss3.2.2\Jboss3.2.2RC1_tomcat-4.1.24
(this directory name is the folder containing the extracted content of the zip Jboss3.2.2RC1_tomcat-4.1.24 stored in D:/Jboss3.2.2)
Hav I mentioned the correct path in home directory? ...why am i getting this error? Can anyone help??
Thanks in advance

hi,
I resolved this problem. Try doing the following....
Goto Preferences -> Java -> Installed JREs.
click Edit on selecting the currently added JRE.
In JRE Home Directory: Set the path to the installed jdk version folder. say, u have installed jdk1.4.2 in folder "java" in ur C:/MyInstallations
Then give the home directory path as C:/MyInstallations/java/jdk1.4.2
It worked for me...u too try out!
... I got this solution from the following link...
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=76362&view=next

Similar Messages

Deploying BC4J as a session EJB in JBoss.Help while looking up

Hello there,
I have developed a simple bc4j component.I have deployed the
same in Weblogic server5.1.I have to deploy the same thing in
JBoss Server.I am using JBoss-Tomcat bundle(Jboss-2.2.2_Tomcat-
3.2.2).I have deployed the BC4J component as a session bean in
JBoss server(No erros while deploying)
But the problem is when to call this session bean.To lookup the
application module as is done in Weblogic the value for
JboContext.DEPLOY_PLATFORM is given as JboContext.PLATFORM_WLS.
This is taken to be specific to weblogic server.What is the
value for this property for a JBossServer.
Any help would be appreciated.Thanks a lot

Hello there,
I have developed a simple bc4j component.I have deployed the
same in Weblogic server5.1.I have to deploy the same thing in
JBoss Server.I am using JBoss-Tomcat bundle(Jboss-2.2.2_Tomcat-
3.2.2).I have deployed the BC4J component as a session bean in
JBoss server(No erros while deploying)
But the problem is when to call this session bean.To lookup the
application module as is done in Weblogic the value for
JboContext.DEPLOY_PLATFORM is given as JboContext.PLATFORM_WLS.
This is taken to be specific to weblogic server.What is the
value for this property for a JBossServer.
Any help would be appreciated.Thanks a lot

LCDS + JBoss Help

I am looking for info. on getting LCDS to run on JBoss 4.2.2. I searched google and found a few links that looked promising but they are no longer up.
Such as:
http://acspace.can.adobe.com/blogs/xav/2008/03/15/how-to-setup-an-efficient-lcds-applicati on-with-flex-3-on-jboss
Anyone know how to get to that place on adobe...the posting was just a few months ago.
I have a WAR (exploded) running in JBoss. (i.e. C:\jboss\server\default\deploy\MyProject.war)
The project exposes a Java class as a web service using Apache CXF. I have a Flex 3 client that accesses it, all is well.
I'd like to add LiveCycle DS (LCDS) to the web app so that I can get messages from ActiveMQ to my Flex client. What do I need to do to make this WAR one that includes the LCDS configs and JARs necessary ?
thanks

Hi Here i m working on JBoss 4.2.2 and eclipse Gynemade. I m instantiating a java file at the time when jboss configure log4j.xml. I had given its entry in log4j.xml. Now my problem is that file have to access the database which are bound to perticuler JNDI names. And JNDI service starts after the log4j configure. So a null pointer exception is coming at the time server configure log4j, due to that java file. Can Anyone help me here. I m sending the change in log4j.xml that exception detail Code: <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender"> <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/> <param name="File" value="${jboss.server.log.dir}/server.log"/> <param name="Append" value="false"/>  <param name="DatePattern" value="'.'yyyy-MM-dd"/>  <layout class="org.apache.log4j.PatternLayout">  <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>  </layout> </appender> <appender name ="FILE1" class="org.apache.log4j.FileAppender"> <param name="File" value="${jboss.server.log.dir}/server1.log" /> <param name="Append" value="false" /> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/> </layout> <filter class="com.propco.tools.mergemanager.profiles.Domfilter"/> [img]http://img223.imageshack.us/my.php?image=95972212vg1.png[/img] Please zoom in the image as the image is a little out of focus. Sorry for the inconvenience. Thanks Divya Garg

Need urgent help regarding Adobe LC ES2 JBOSS Clustering

Hi,
Am trying to setup a Horizontal Cluster setup(with two nodes) for Adobe LiveCycle ES2 with Adobe preconfigured JBOSS 4.2.1 and MSSQL 2008(single instance running on one of the nodes).
I have successfully completed till Installing LC ES2 Modules in both the nodes according to the "Configuring LiveCycle® ES2 Application Server Clusters Using JBoss" document.
But now the problem is about the next step, which is "Configuring LiveCycle ES2 for Deployment". The steps in this section do not clearly talk about where to run the configuration manager tool, i mean on which node of the cluster as two nodes are different machines in my case as it is a horizontal cluster. But at step 20 of configuring LC ES2(page 45 of the above mentioned document) there's note which says "Note: You need to initialize the database against only one server of the cluster. Subsequent steps need to be performed on only this server as well."
Now,
i) Does it mean that till step 19 i will have to parallely run configuration manager tool on both the nodes of the cluster and at step 20 i will have to completely exit the configuration manager tool on one node(Say node A) and continue the rest of all the steps(till 46) only in the other node( node B ) ?
OR
I will have to keep the configuration manager window open in both the machines and perform some steps say for example 20 to 25 only in one node(say node B ) and skip these steps in node A and resume from 26 in node A and complete till the end in both the machines ?
ii) At step 16 of the same section theres a note which says "Note: The paths for pop3.jar and the JDK must be same on all nodes in the cluster.". Where will the pop3.jar be ? I cudn't find it anywhere in the installation media or in the server folders ?
Please help me asap as am stuck with it for two days !!! Please let me know if you need any other details.

Hi,
Am trying to setup a Horizontal Cluster setup(with two nodes) for Adobe LiveCycle ES2 with Adobe preconfigured JBOSS 4.2.1 and MSSQL 2008(single instance running on one of the nodes).
I have successfully completed till Installing LC ES2 Modules in both the nodes according to the "Configuring LiveCycle® ES2 Application Server Clusters Using JBoss" document.
But now the problem is about the next step, which is "Configuring LiveCycle ES2 for Deployment". The steps in this section do not clearly talk about where to run the configuration manager tool, i mean on which node of the cluster as two nodes are different machines in my case as it is a horizontal cluster. But at step 20 of configuring LC ES2(page 45 of the above mentioned document) there's note which says "Note: You need to initialize the database against only one server of the cluster. Subsequent steps need to be performed on only this server as well."
Now,
i) Does it mean that till step 19 i will have to parallely run configuration manager tool on both the nodes of the cluster and at step 20 i will have to completely exit the configuration manager tool on one node(Say node A) and continue the rest of all the steps(till 46) only in the other node( node B ) ?
OR
I will have to keep the configuration manager window open in both the machines and perform some steps say for example 20 to 25 only in one node(say node B ) and skip these steps in node A and resume from 26 in node A and complete till the end in both the machines ?
ii) At step 16 of the same section theres a note which says "Note: The paths for pop3.jar and the JDK must be same on all nodes in the cluster.". Where will the pop3.jar be ? I cudn't find it anywhere in the installation media or in the server folders ?
Please help me asap as am stuck with it for two days !!! Please let me know if you need any other details.

Problem with clustering with JBoss server---help needed

Hi,
Its a HUMBLE REQUEST TO THE EXPERIENCED persons.
I am new to clustering. My objective is to attain clustering with load balencing and/or Failover in JBoss server. I have two JBoss servers running in two diffferent IP addresses which form my cluster. I could succesfully perform farm (all/farm) deployment
in my cluster.
I do believe that if clustering is enabled; and if one of the server(s1) goes down, then the other(s2) will serve the requests coming to s1. Am i correct? Or is that true only in the case of "Failover clustering". If it is correct, what are all the things i have to do to achieve it?
As i am new to the topic, can any one explain me how a simple application (say getting a value from a user and storing it in the database--assume every is there in a WAR file), can be deployed with load balencing and failover support rather than going in to clustering EJB or anything difficult to understand.
Kindly help me in this mattter. Atleast give me some hints and i ll learn from that.Becoz i could n't find a step by step procedure explaining which configuration files are to be changed to achieve this (and how) for achiving this. Also i could n't find Books explaining this rather than usual theorectical concepts.
Thanking you in advance
with respect
abhirami

hi ,
In this scenario u can use the load balancer instead of fail over clustering .
I would suggest u to create apache proxy for redirect the request for many jboss instance.
Rgds
kathir

HELP with JBoss 4.0.3 and ADF Faces

Hi! I'm trying to deploy a simple web application using ADF Faces. The point is that when trying to access the main page I get the following error:
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:370)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
oracle.adfinternal.view.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:157)
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:367)
oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:336)
oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:196)
oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:87)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
root cause
java.lang.NullPointerException
javax.faces.webapp.UIComponentTag.setupResponseWriter(UIComponentTag.java:615)
javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:217)
org.apache.myfaces.taglib.core.ViewTag.doStartTag(ViewTag.java:71)
org.apache.jsp.main_jspx._jspx_meth_f_view_0(org.apache.jsp.main_jspx:99)
org.apache.jsp.main_jspx._jspService(org.apache.jsp.main_jspx:77)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
oracle.adfinternal.view.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:157)
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._invokeDoFilter(AdfFacesFilterImpl.java:367)
oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl._doFilterImpl(AdfFacesFilterImpl.java:336)
oracle.adfinternal.view.faces.webapp.AdfFacesFilterImpl.doFilter(AdfFacesFilterImpl.java:196)
oracle.adf.view.faces.webapp.AdfFacesFilter.doFilter(AdfFacesFilter.java:87)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5 logs.
Apache Tomcat/5.5
I used to get this error time a ago when using MyFaces. It was caused by not getting the page through the Faces Servlet. This time that's not the case. I've got:
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
and I load the page this way: http://localhost:8080/MyApp/faces/main.jspx
Maybe it's because I'm missing some libraries within the war. Next I list the jars I'm incluiding in the archive:
adf-faces-api.jar
adf-faces-impl.jar
adfshare.jar
commons-beanutils.jar
commons-collections.jar
commons-digester.jar
commons-logging-api.jar
commons-logging.jar
jsf-api.jar
jsf-impl.jar
jstl.jar
Any help would really be appreciated.
Thank you very much.
Joaquín.

I suggest that see on JBoss server the list of jndi tree, maybe the entity stay whit another name.
You can go to server administrator page, login on jboss console and find the jndi list. JBoss bring with a mbean that can show the jndi tree of the server, you can use the JMX console of the JBoss to invoke it.
Sorry for my poor english

Authentication problem on JBOSS. Need help!

I use jboss 3.0.3.
My "auth.conf" file is:
simple {
org.jboss.security.ClientLoginModule required
 password-stacking="useFirstPass"
Application policy in "login-config.xml" is
<application-policy name="admin">
<authentication>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
<module-option name="unauthenticatedIdentity">guest</module-option>
</login-module>
</authentication>
</application-policy>
My "jboss.xml" is :
<jboss>
<enterprise-beans>
<entity>
<ejb-name>Sec1</ejb-name>
<jndi-name>Sec1Remote</jndi-name>
</entity>
</enterprise-beans>
<security-domain>java:/jaas/admin</security-domain>
</jboss>
File "users.properties" is :
alexander=aaa
File "roles.properties" is :
alexander=admin
Client code is :
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
properties.put(Context.PROVIDER_URL, "localhost:1099");//app server url
properties.put(Context.SECURITY_PRINCIPAL, "admin");
properties.put(Context.SECURITY_CREDENTIALS, "aaa");
InitialContext ctx = new InitialContext(properties);
Object ref = ctx.lookup("Sec1Remote");
Sec1RemoteHome sec1RemoteHome = (Sec1RemoteHome) PortableRemoteObject.narrow(ref, Sec1RemoteHome.class);
Sec1Remote sec1Remote = sec1RemoteHome.findByPrimaryKey("1");
System.out.println(sec1Remote.getName());
My "ejb-jar.xml" is:
<ejb-jar>
<enterprise-beans>
<entity>
<display-name>sec1</display-name>
<ejb-name>Sec1</ejb-name>
<home>untitled2.Sec1RemoteHome</home>
<remote>untitled2.Sec1Remote</remote>
<ejb-class>untitled2.Sec1Bean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<abstract-schema-name>Enterprise1</abstract-schema-name>
<env-entry>
<description />
<env-entry-name>eee</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>rrr</env-entry-value>
</env-entry>
<security-role-ref>
<description />
<role-name>admin</role-name>
<role-link>admin</role-link>
</security-role-ref>
<security-identity>
<description>aaa</description>
<use-caller-identity />
</security-identity>
</entity>
</enterprise-beans>
<assembly-descriptor>
<security-role>
<description>admin</description>
<role-name>admin</role-name>
</security-role>
<security-role>
<description>System Manager</description>
<role-name>manager</role-name>
</security-role>
<method-permission>
<role-name>admin</role-name>
<method>
<description />
<ejb-name>Sec1</ejb-name>
<method-intf>Remote</method-intf>
<method-name>getName</method-name>
<method-params />
</method>
</method-permission>
<method-permission>
<unchecked />
<method>
<description />
<ejb-name>Sec1</ejb-name>
<method-intf>Home</method-intf>
<method-name>findByPrimaryKey</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>Sec1</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
When I try to run client's program, an error appeares:
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
 java.rmi.ServerException: EJBException:; nested exception is:
 javax.ejb.EJBException: checkSecurityAssociation; CausedByException is:
 Insufficient method permissions, principal=null, method=getName, interface=REMOTE, requiredRoles=[admin], principalRoles=[]
I have no ideas, why it appeares? What's wrong?
Help me, please... :(

easy... your principal should be alexander, not admin

Need help in installing JBOSS along with Jdk version

Hi,
I am using Linux 64 bit Machine.
I have Jdk1.5.0_18 and jboss-4.2.3.GA installed in my machine.
But the JBOSS Server is failed in booting.
What version of JBOSS Server needed for the 64 bit along with Jdk1.5.0_18
Any help will be needful for me
Thanks and Regards

The name of this forum is "Database - General" not JBOSS, JDK, or "anything goes."
Please delete this post and post your question in the appropriate forum.
Thank you.

Datasource connection with jboss, need help

Hi friends,
I am doing data source connection through Jboss (jboss-4.0.2) with mysql database. I am using java(j2sdk1.4.2_04). I have made all changes given in this link -- http://community.jboss.org/wiki/SetUpAMysqlDatasource
After making changes I restart jboss properly, but when I am going to attempt to connection through class. it give following error.
1.ERROR! Shared library ioser12 could not be found.
Can't find SerialContextProvider
When a create a diffrent new class, then give me this error.
2. ERROR! Shared library ioser12 could not be found.
Cannot get connection: javax.naming.CommunicationException: Can't find SerialContextProvider
Kindly help me out for this problem.
Thanks
Abhishek Jain

user13428037 wrote:
,,, JBoss ... give following error.
1.ERROR! Shared library ioser12 could not be found.
Can't find SerialContextProvider
When a create a diffrent new class, then give me this error.
2. ERROR! Shared library ioser12 could not be found.
Cannot get connection: javax.naming.CommunicationException: Can't find SerialContextProviderPlease don't crosspost http://www.javaprogrammingforums.com/jdbc-databases/6353-datsource-connection-mysql-need-help.html#post22533
The
ERROR! Shared library ioser12 could not be found.error message has nothing to do with you adding a datasource.
It would happen even before you made the datasource configuration changes.
Looks like you added a j2ee.jar to the JBoss classpath.

Ergent Help Using JBoss, EJBs ...

Hey to all ....
Please help me, i just started EJBs and i am having difficulties with the given project.
So ..
I am using EJB, Jboss too deploy everything
I have created my entities and some sessions.
Entities have created my database correctly.
Now i want to access the data from Jsp.
I Could use some help on that.
I am trying to create the JSP to call the sessions files that i have but i must be doing something wrong.
I have jared both entities and sessions and uploaded them in ejb container.
I am placing my jsp into the jsp container.
i am placing all classes into the web-inf container as well in the jsp container.
HOW will i get the data using the JSp ?
Please some help here.
Perhaps not the best post, but i have no idea what else too post

done it .... :)

How to deploy JavaHelp server help demo on JBoss?

I tried JavaHelp's server help demo on tomcat it worked fine. I was able to view all the help docs. But I need to change the configuration for the demo to work on JBoss-4.0.1. I deployed the content on Jboss but when running the index.jsp, I got this error. What am I missing? Do I need to change the implementation or what? Any input is appreciated.
org.apache.jasper.JasperException: File "/jhlib.tld"; not found
 org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)
 org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:411)
 org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:118)
 org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:159)
 org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:418)
 org.apache.jasper.compiler.Parser.parseDirective(Parser.java:483)
 org.apache.jasper.compiler.Parser.parseElements(Parser.java:1539)
 org.apache.jasper.compiler.Parser.parse(Parser.java:126)
 org.apache.jasper.compiler.ParserController.doParse(ParserController.java:220)
 org.apache.jasper.compiler.ParserController.parse(ParserController.java:101)
 org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:203)
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:470)
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
 org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
 org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
 org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
 org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)

BPEL Console is for deploying BPEL projects. And when you talking about war file, those are web archive files, application server specific. Please refer to the Application Server document for deploying war files. Like for OC4J, you can do the same via Enterprise Manager.

Help: Deploying CMP Entity Bean on Jboss (DB2)

Hi, I have a problem which I have tried to solve for a couple of days now with now success.
I have deployed an ordinary Entity CMP Bean which name is Customer.
This bean has 2 fields, an id field and a customername field.
I use DB2 where the table is named customer and the fields are named as the fields in the bean, id and customername.
I have configured the db2-ds.xml file as follows, and put it in %jboss%\server\default\deploy:
<local-tx-datasource>
<jndi-name>DB2DS</jndi-name>
<connection-url>jdbc:db2://192.168.10.220:6789/business</connection-url>
<driver-class>COM.ibm.db2.jdbc.net.DB2Driver</driver-class>
<user-name>db2admin</user-name>
fuck4future
<min-pool-size>5</min-pool-size>
<max-pool-size>25</max-pool-size>



<type-mapping>DB2</type-mapping>
</local-tx-datasource>
I have created the jbosscmp-jdbc.xml file and put it in the META-INF directory in my ejb-application:
<jbosscmp-jdbc>
DB2DS

<create-table>false</create-table>
<enterprise-beans>
<ejb-name>Customer</ejb-name>
<table-name>customers</table-name>
<cmp-field>
<field-name>id</field-name>
<column-name>id</column-name>
</cmp-field>
<cmp-field>
<field-name>companyname</field-name>
<column-name>companyname</column-name>
</cmp-field>
</enterprise-beans>
</jbosscmp-jdbc>
I have created the standardjaws.xml also in my META-INF directory of the ejb application. This file contains a lot of information (type-mappings), and starts with:
java:/DB2DS
<type-mapping>DB2</type-mapping>
false
I have the ejb-jar.xml file automaticly generated for me in my developer tool (WSAD).
When I try to start my server I get the following error:
ObjectName: jboss.j2ee:jndiName=Customer,service=EJB
state: FAILED
Depends On Me: org.jboss.deployment.DeploymentException: type-mapping is not initialized: DB2DS was not deployed or type-mapping was not configured.
ObjectName: jboss.j2ee:service=EJB,plugin=pool,jndiName=Customer
etc.......
Please can someone help me and give me a clue, what am I doing wrong??

And this is my console :
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: c:\jboss4\bin\\..
JAVA: c:\program\java\jdk1.5.0_01\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Xms128m -Xmx512m
CLASSPATH: c:\program\java\jdk1.5.0_01\lib\tools.jar;c:\jboss4\bin\\run.jar
===============================================================================
22:36:01,986 INFO [Server] Starting JBoss (MX MicroKernel)...
22:36:01,986 INFO [Server] Release ID: JBoss [Zion] 4.0.1sp1 (build: CVSTag=JBoss_4_0_1_SP1 date=200502160314)
22:36:01,986 INFO [Server] Home Dir: C:\jboss4
22:36:01,986 INFO [Server] Home URL: file:/C:/jboss4/
22:36:01,996 INFO [Server] Library URL: file:/C:/jboss4/lib/
22:36:01,996 INFO [Server] Patch URL: null
22:36:01,996 INFO [Server] Server Name: default
22:36:01,996 INFO [Server] Server Home Dir: C:\jboss4\server\default
22:36:01,996 INFO [Server] Server Home URL: file:/C:/jboss4/server/default/
22:36:01,996 INFO [Server] Server Data Dir: C:\jboss4\server\default\data
22:36:01,996 INFO [Server] Server Temp Dir: C:\jboss4\server\default\tmp
22:36:02,006 INFO [Server] Server Config URL: file:/C:/jboss4/server/default/conf/
22:36:02,006 INFO [Server] Server Library URL: file:/C:/jboss4/server/default/lib/
22:36:02,006 INFO [Server] Root Deployment Filename: jboss-service.xml
22:36:02,006 INFO [Server] Starting General Purpose Architecture (GPA)...
22:36:02,336 INFO [ServerInfo] Java version: 1.5.0_01,Sun Microsystems Inc.
22:36:02,336 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_01-b08,Sun Microsystems Inc.
22:36:02,336 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
22:36:02,827 INFO [Server] Core system initialized
22:36:04,289 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
22:36:04,379 INFO [WebService] Using RMI server codebase: http://CYONARA:8083/
22:36:04,549 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
22:36:08,625 INFO [Embedded] Catalina naming disabled
22:36:09,246 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
22:36:09,276 INFO [Catalina] Initialization processed in 571 ms
22:36:09,276 INFO [StandardService] Starting service jboss.web
22:36:09,286 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.0.28
22:36:09,306 INFO [StandardHost] XML validation disabled
22:36:09,336 INFO [Catalina] Server startup in 60 ms
22:36:09,476 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/C:/jboss4/server/default/deploy/http-invoker.sar/invoker.war/
22:36:10,187 INFO [TomcatDeployer] deploy, ctxPath=/ws4ee, warUrl=file:/C:/jboss4/server/default/tmp/deploy/tmp43675jboss-ws4ee-exp.war/
22:36:10,318 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/C:/jboss4/server/default/deploy/jbossweb-tomcat50.sar/ROOT.war/
22:36:10,508 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/C:/jboss4/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
22:36:12,741 INFO [MailService] Mail Service bound to java:/Mail
22:36:13,272 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss4/server/default/deploy/jboss-local-jdbc.rar
22:36:13,412 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss4/server/default/deploy/jboss-xa-jdbc.rar
22:36:13,552 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss4/server/default/deploy/jms/jms-ra.rar
22:36:13,732 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/jboss4/server/default/deploy/mail-ra.rar
22:36:14,153 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DB2DS to JNDI name 'java:DB2DS'
22:36:14,834 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS to JNDI name 'java:DefaultDS'
22:36:14,864 WARN [ConfiguredIdentityLoginModule] Creating LoginModule with no configured password!
22:36:15,145 INFO [A] Bound to JNDI name: queue/A
22:36:15,145 INFO Bound to JNDI name: queue/B
22:36:15,155 INFO [C] Bound to JNDI name: queue/C
22:36:15,155 INFO [D] Bound to JNDI name: queue/D
22:36:15,155 INFO [ex] Bound to JNDI name: queue/ex
22:36:15,175 INFO [testTopic] Bound to JNDI name: topic/testTopic
22:36:15,175 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
22:36:15,185 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
22:36:15,185 INFO [testQueue] Bound to JNDI name: queue/testQueue
22:36:15,235 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
22:36:15,275 INFO [DLQ] Bound to JNDI name: queue/DLQ
22:36:15,795 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA to JNDI name 'java:JmsXA'
22:36:15,835 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C:/jboss4/server/default/deploy/jmx-console.war/
22:36:15,996 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C:/jboss4/server/default/deploy/management/web-console.war/
22:36:16,526 INFO [EARDeployer] Init J2EE application: file:/C:/jboss4/server/default/deploy/HTC.ear
22:36:16,787 INFO [EjbModule] Deploying Customer
22:36:17,047 ERROR [EntityContainer] Starting failed jboss.j2ee:jndiName=Customer,service=EJB
org.jboss.deployment.DeploymentException: type-mapping is not initialized: java:/DB2DS was not deployed or type-mapping was not configured.
 at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityMetaData.getTypeMapping(JDBCEntityMetaData.java:1071)
 at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:412)
 at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:353)
 at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157)
 at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:416)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy47.start(Unknown Source)
 at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:416)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy22.start(Unknown Source)
 at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
 at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy8.deploy(Unknown Source)
 at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
 at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:416)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy4.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
 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:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy5.deploy(Unknown Source)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:413)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
 at org.jboss.Main.boot(Main.java:162)
 at org.jboss.Main$1.run(Main.java:423)
 at java.lang.Thread.run(Thread.java:595)
22:36:17,047 WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=Customer,service=EJB
org.jboss.deployment.DeploymentException: type-mapping is not initialized: java:/DB2DS was not deployed or type-mapping was not configured.
 at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityMetaData.getTypeMapping(JDBCEntityMetaData.java:1071)
 at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.initStoreManager(JDBCStoreManager.java:412)
 at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:353)
 at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:157)
 at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:340)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:416)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy47.start(Unknown Source)
 at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:416)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy22.start(Unknown Source)
 at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
 at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy8.deploy(Unknown Source)
 at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
 at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:481)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
 at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:277)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
 at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start(ServiceController.java:416)
 at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy4.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start(SARDeployer.java:261)
 at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:722)
 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:585)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
 at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
 at $Proxy5.deploy(Unknown Source)
 at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:413)
 at org.jboss.system.server.ServerImpl.start(ServerImpl.java:310)
 at org.jboss.Main.boot(Main.java:162)
 at org.jboss.Main$1.run(Main.java:423)
 at java.lang.Thread.run(Thread.java:595)
22:36:17,057 INFO [EJBDeployer] Deployed: file:/C:/jboss4/server/default/tmp/deploy/tmp43727HTC.ear-contents/HTC_BM_EJB.jar
22:36:17,107 INFO [TomcatDeployer] deploy, ctxPath=/HTC BM Web, warUrl=file:/C:/jboss4/server/default/tmp/deploy/tmp43727HTC.ear-contents/HTC_BM_Web-exp.war/
22:36:17,228 INFO [EARDeployer] Started J2EE application: file:/C:/jboss4/server/default/deploy/HTC.ear
22:36:17,238 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
MBeans waiting for other MBeans:
ObjectName: jboss.j2ee:jndiName=Customer,service=EJB
state: FAILED
I Depend On:
Depends On Me: org.jboss.deployment.DeploymentException: type-mapping is not initialized: java:/DB2DS was not deployed or type-mapping was not configured.
ObjectName: jboss.j2ee:service=EJB,plugin=pool,jndiName=Customer
state: CREATED
I Depend On:
Depends On Me:
MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.j2ee:service=EJB,plugin=pool,jndiName=Customer
state: CREATED
I Depend On:
Depends On Me:
ObjectName: jboss.j2ee:jndiName=Customer,service=EJB
state: FAILED
I Depend On:
Depends On Me: org.jboss.deployment.DeploymentException: type-mapping is not initialized: java:/DB2DS was not deployed or type-mapping was not configured.

How to deploy Enterprise JavaBeans in JBoss server.pls help me

anybody can help me,how to deploy SessionBeans,CMP,BMP,JMS in jb oss server.pls explain me the steps for how to deploy EJB in JBoss server.what are the steps i have to follow.

Hi Chris,
Yes, I have created a MSI package for the application and installed it on the server.
I have created the run time package for powerbuilder and install it on the server.
I have installed the DB Client drivers also.
Can you please help me on how to the configure the application pools, as i never worked on this stuffs,In developemnt enviornment just click on the run webservice and its there .
Regards
Subrat

Need Urgent Help! Exception During Deployment of JBoss Scheduler Service

Hi Folks,
I have a web app (.war) to deploy to JBoss 4.0.2, and there's a class in the app that implements org.jboss.varia.scheduler.Schedulable.
I want this thing to be invoked by the JBoss Scheduler, but I can't seem to get my Schedulable instance started.
Note: This is simply a web deployment (WAR), not a J2EE Application (EAR).
I've tried to deploy the Scheduler at the server level but i've got a deployment exception - "file is not not found".
also, I've tried to add the scheduler-service.xml into my web app (in WAR file ~/META-INF/ directory).
I'm open to suggestions on how to configure the scheduler services so it will work without any exceptions.
My scheduler-service.xml is as follows:
<server>
<mbean code="org.jboss.varia.scheduler.Scheduler" name="TevaOrderScheduler:service=Scheduler">
 <attribute name="StartAtStartup">true</attribute>
 <attribute name="SchedulableClass">com.cnw.enfopack.TevaOrderScheduler</attribute>
 <attribute name="InitialStartDate">NOW</attribute>
 
 <attribute name="SchedulePeriod">20 * 1000</attribute>
 <attribute name="InitialRepetitions">-1</attribute>
</mbean>
</server>
Please HELP me, I'm working on this issue in the last 3 days!!!
Many Thanks in advance,
Sagi.
Edited by: Sagi_MY on Feb 11, 2009 11:32 PM

Thanks for your reply jwenting,
But for me it's an urgent case since my Scheduler refuse to work!!!
how it can be that you have'nt face such problem in JBoss 4.0.2?
I've search the Internet and saw many people that have faced the same problem like me.
(But, unfortunately, their answers didn't help me)
Please try to help me since It's almost 10 days that I'm dealing with it.
Many thanks mate.

Problems with log4j in jboss please help

Please i need help because i can't anywhere else.
Below is the log4j properties file
# initialise root logger with level INFO and call it
log4j.rootLogger=INFO, BLAH
# add a Appender to the logger BLAH
log4j.appender.BLAH=org.apache.log4j.RollingFileAppender
# set the layout
log4j.appender.BLAH.layout=org.apache.log4j.PatternLayout
#log4j.appender.BLAH.layout.ConversionPattern=%p %c - %m%n
log4j.appender.BLAH.layout.ConversionPattern=%d{dd-MMM-yyyy HH:mm:ss:SSS}: %m%n
log4j.appender.BLAH.File=c:/testing.log
log4j.appender.BLAH.MaxFileSize=10000KB
# Keep one backup file
log4j.appender.BLAH.MaxBackupIndex=10
Below is the code in which i am using log4j logging
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.PrintWriter;
import java.io.IOException;
import org.apache.log4j.Logger;
import org.apache.log4j.PropertyConfigurator;
public class rectest extends HttpServlet
private static final String CONTENT_TYPE = "text/html; charset=windows-1252";
public void init(ServletConfig config) throws ServletException
super.init(config);
String prefix = "D:/jdkwork/work/App/testing";
String file = getInitParameter("log4j-init-file");
// if the log4j-init-file is not set, then no point in trying
if(file != null) {
PropertyConfigurator.configure(prefix+file);
private static Logger log =Logger.getLogger(rectest.class);
public void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
doPost(request,response);
public void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
response.setContentType(CONTENT_TYPE);
PrintWriter out = response.getWriter();
out.println("<html>");
out.println("<head><title>rectest</title></head>");
out.println("<body>");
log.info("this is a test");
out.println("The servlet has received a POST. This is the reply.");
out.println("</body></html>");
out.close();
I deploy the war file in jboss4 and run it. It runs smoothly and when deploys the war file, all the info messages in the console are then logged to the log file of my application which is deployed in it. i am new to log4j and couldn't find solution for that. please help

should i assume that there will be no help for this or there is no solution for which is offcourse not possible.

Jboss help!!!!

Similar Messages

Maybe you are looking for