Sun One/JNDI
I have a working Sun One directory that has explicit groups -- groupOfUniqueName objectswith uniqueMember attributes.
I'm trying to use JNDI to do something similar to what I've done in the past on OpenLDAP. My searches are successful, but I have yet to be able to retrieve the uniqueMember attributes. It's as if they don't exist. Coincidentally (or not), a generic LDAP browser tool has the same problem.
I've perused what little I can find in the development documentation and there doesn't seem to be anything special required to do JNDI against a Sun One Directory Server.
What am I missing?
You don't have to create these files. You need to import the package and make sure your environment Classpath has access to the package also. Then only you will be able to compile your code.
Let me know if you need further help
Similar Messages
-
Crystal Reports XI and Sun One 6.1 web server SP 5 Error finding JNDI name
I am trying to create a Crystal Reports XI report in a JSP using Sun One 6.1 Web server sp 5.
At this point I am getting the error �Error finding JNDI name� on Sun One
The application will run on Netbeans/Tomcat
I have done the following:
I edited CRConfig.xml
<?xml version="1.0" encoding="utf-8"?>
<CrystalReportEngine-configuration>
�
<DataDriverCommon>
<JavaDir>C:\Program Files\Java\j2re1.4.2_10\bin</JavaDir>
<Classpath>C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14.jar;�</Classpath>
�
<JDBC>
<CacheRowSetSize>100</CacheRowSetSize>
<JDBCURL>jdbc:oracle:thin:@10.10.10.10:1521:dev</JDBCURL>
<JDBCClassName>oracle.jdbc.driver.OracleDriver</JDBCClassName>
<JDBCUserName>lab_ro</JDBCUserName>
<JNDIURL></JNDIURL>
�
</JDBC>
I created a report using JDBC (JNDI) connection and have the JNDI Connection set to the name of DATA.
The report works just fine in Crystal Reports.
Then in Netbeans I created an application and it runs in the Tomcat part of Netbeans
In context.xml I have:
<Context path="/BOEnterpriseTest3">
<Resource name="jdbc/dev" auth="Container" type="javax.sql.DataSource"
driverClassName="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@10.10.10.10:1521:dev"
username="theuserid" password="thepassword" maxActive="20" maxIdle="10" maxWait="-1"/>
</Context>
In web.xml I have
<web-app>
<context-param>
<param-name>crystal_image_uri</param-name>
<param-value>crystalreportviewers11</param-value>
</context-param>
�
<taglib>
<taglib-uri>/crystal-tags-reportviewer.tld</taglib-uri>
<taglib-location>/WEB-INF/crystal-tags-reportviewer.tld</taglib-location>
</taglib>
<resource-ref>
<description>jdbc:oracle:thin:@10.10.10.10:1521:dev</description>
<res-ref-name>jdbc/dev10g</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-ref>
<description>jdbc:oracle:thin:@10.10.10.10:1521:dev</description>
<res-ref-name>Data</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
</web-app>
in web-inf\sun-web.xml I have
<sun-web-app>
<resource-ref>
<res-ref-name>jdbc/dev10g</res-ref-name>
<jndi-name>Data</jndi-name>
</resource-ref>
</sun-web-app>
I have copied all of Common Files\Business Objects\3.0\java\lib and Common Files\Business Objects\3.0\java\lib\external to the lib folder
I have copied crystalreportviewers11 to the root of my web application
I have tried to load the JNDI information and display the report
<%@page pageEncoding="UTF-8"
import="com.crystaldecisions.reports.reportengineinterface.*,
com.crystaldecisions.report.web.viewer.*,
javax.naming.*,
javax.sql.*,
java.sql.*"%>
<%
InitialContext initContext = new InitialContext();
DataSource source = (DataSource) initContext.lookup("java:comp/env/jdbc/dev10g");
Context initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
try{
// Look up our data source
DataSource ds = (DataSource)initCtx.lookup("Data");
out.println("found ds under jdbc/Data");
catch ( NamingException e ){
// Look up our data source
DataSource ds = (DataSource) initContext.lookup("java:comp/env/jdbc/dev10g");
initCtx.bind("Data", ds);
out.println("found ds under java:com/env:jdbc/Data - bound into root initial context for Crystal to find");
%>
<%
//Use the relative path to the report; the physical or full qualified URL cannot be used.
String reportName = "useridincluded.rpt";
//Database username and password
String userName = "theuserid";
String password = "thepassword";
//check to see if the Report Source Session Variable already exist
Object reportSource = session.getAttribute("Report1");
// Create a new ConnectionInfos and ConnectionInfo object
com.crystaldecisions.sdk.occa.report.data.ConnectionInfos connectionInfos = new com.crystaldecisions.sdk.occa.report.data.ConnectionInfos();
com.crystaldecisions.sdk.occa.report.data.ConnectionInfo connectionInfo = new com.crystaldecisions.sdk.occa.report.data.ConnectionInfo();
//Set username and password for the report's database
connectionInfo.setUserName(userName);
connectionInfo.setPassword(password);
//Add object to collection
connectionInfos.add(connectionInfo);
//---------- Create a ReportClientDocument -------------
com.crystaldecisions.reports.sdk.ReportClientDocument reportClientDocument = new com.crystaldecisions.reports.sdk.ReportClientDocument();
//---------- Set the path to the location of the report soruce -------------
//Open report.
reportClientDocument.open(reportName, 0);
//Get the report source
reportSource = reportClientDocument.getReportSource();
//---------- Create the viewer and render the report -------------
//create the CrystalReportViewer object
com.crystaldecisions.report.web.viewer.CrystalReportViewer crystalReportViewer = new com.crystaldecisions.report.web.viewer.CrystalReportViewer();
//set the reportsource property of the viewer
crystalReportViewer.setReportSource(reportSource);
//set the DB logon into the viewer
crystalReportViewer.setDatabaseLogonInfos(connectionInfos);
//set viewer attributes
crystalReportViewer.setOwnPage(true);
crystalReportViewer.setOwnForm(true);
crystalReportViewer.refresh();
//set the CrystalReportViewer print mode
//crystalReportViewer.setPrintMode(com.crystaldecisions.report.web.viewer.CrPrintMode.ACTIVEX);
crystalReportViewer.setPrintMode(com.crystaldecisions.report.web.viewer.CrPrintMode.PDF);
//process the report
crystalReportViewer.processHttpRequest(request, response, getServletConfig().getServletContext(), null);
%>
On the Sun One Web server
On the Java Tab
JDBC Connection Pools
Pool Name = dev10g
Class name = oracle.jdbc.pool.OracleDataSource
User id = theuserid
url = 10.10.10.10
password=thepassword
JDBC Resources
JNDI Name=dev10g
Pool = dev10g
I get the error finding JNDI name � how do I tell Sun One where the JNDI is to make Crystal Reports work?I tried the following to test the JNDI
I am trying to do JNDI in Sun One Web server 6.1 sp 5 but I seem to be missing an important part. I get two different errors based on the JSP code, �Cannot retrieve data source: javax.naming.NamingException: Cannot create resource instance� or �Cannot retrieve data source: javax.naming.NamingException: Cannot create resource instance�.
Context.xml:
<?xml version="1.0" encoding="UTF-8"?>
<Context path="/BOTest">
<Resource name="jdbc/dev10g" auth="Container" type="javax.sql.DataSource"
driverClassName="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@10.10.10.10:1521:dev10g"
username="userid" password="password" maxActive="20" maxIdle="10" maxWait="-1"/>
<Resource name="Data" auth="Container" type="javax.sql.DataSource"
driverClassName="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@10.10.10.10:1521:dev10g"
username="userid" password="password" maxActive="20" maxIdle="10" maxWait="-1"/>
</Context>Sun-one.xml:
<sun-web-app>
<context-root>BOTest</context-root>
<resource-ref>
<res-ref-name>jdbc/dev10g</res-ref-name>
<jndi-name>jdbc/dev10g</jndi-name>
</resource-ref>
</sun-web-app>web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>
index.jsp
</welcome-file>
</welcome-file-list>
<resource-ref>
<description>jdbc:oracle:thin:@10.10.10.10:1521:dev10g</description>
<res-ref-name>jdbc/dev10g</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-ref>
<description>jdbc:oracle:thin:@10.10.10.10:1521:dev10g</description>
<res-ref-name>Data</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Application</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
</web-app>server.xml has:
<RESOURCES>
- <JDBCCONNECTIONPOOL name="dev10g" datasourceclassname="oracle.jdbc.pool.OracleDataSource" steadypoolsize="8" maxpoolsize="32" poolresizequantity="2" idletimeout="300" maxwaittime="60000" connectionvalidationrequired="off" connectionvalidationmethod="auto-commit" validationtablename="" failallconnections="off" transactionisolationlevel="read-uncommitted" isolationlevelguaranteed="off">
<PROPERTY name="URL" value="jdbc:oracle:thin:@10.45.3.197:1521:dev10g" />
<PROPERTY name="User" value="lab_ro" />
<PROPERTY name="Password" value="0asphalt1" />
</JDBCCONNECTIONPOOL>
<JDBCRESOURCE jndiname="jdbc/dev10g" poolname="dev10g" enabled="on" />
<JDBCRESOURCE jndiname="Data" poolname="dev10g" enabled="on" />
- <JDBCCONNECTIONPOOL name="Data" datasourceclassname="oracle.jdbc.pool.OracleDataSource" steadypoolsize="8" maxpoolsize="32" poolresizequantity="2" idletimeout="300" maxwaittime="60000" connectionvalidationrequired="off" connectionvalidationmethod="auto-commit" validationtablename="" failallconnections="off" transactionisolationlevel="read-uncommitted" isolationlevelguaranteed="off">
<PROPERTY name="User" value="lab_ro" />
<PROPERTY name="URL" value="jdbc:oracle:thin:@10.45.3.197:1521:dev10g" />
<PROPERTY name="Password" value="0asphalt1" />
</JDBCCONNECTIONPOOL>
<JDBCRESOURCE jndiname="jdbc/Data" poolname="Data" enabled="on" />
<JDBCRESOURCE jndiname="dev10g" poolname="dev10g" enabled="on" />
</RESOURCES>I am getting the following error: �Cannot retrieve data source: javax.naming.NamingException: Cannot create resource instance�
With the following code:
<%@page
import="java.io.*,
javax.sql.*,
javax.naming.*,
java.sql.*,
java.util.*"%>
<%
Context init;
Context ctx;
DataSource datasource;
Connection con;
try
init = new InitialContext();
Context envCtx = (Context) init.lookup("java:comp/env");
datasource = (DataSource) envCtx.lookup("jdbc/dev10g");
catch(NamingException ex)
out.print("Cannot retrieve data source: " + ex.toString(true));
return;
try
con = datasource.getConnection();
catch (Exception e)
out.print("Cannot retrieve connection: " + e.toString());
return;
try
PreparedStatement pstmt = con.prepareStatement("SELECT PROJNO FROM MATERIALSLAB.VW_ASPHALTHEADERINFO");
ResultSet results = pstmt.executeQuery();
while (results.next())
out.println(results.getString(1));
catch(Exception ex)
out.print("Got connection, can't execute query: " + ex.toString());
return;
%>I get the following error: Cannot retrieve data source: javax.naming.NamingException: Cannot create resource instance
With the following code:
<%@page
import="java.io.*,
javax.sql.*,
javax.naming.*,
java.sql.*,
java.util.*"%>
<%
Context init;
Context ctx;
DataSource datasource;
Connection con;
try
init = new InitialContext();
ctx = (Context) init.lookup("java:comp/env");
datasource = (DataSource) ctx.lookup("jdbc/dev10g");
catch(NamingException ex)
out.print("Cannot retrieve data source: " + ex.toString(true));
return;
try
con = datasource.getConnection();
catch (Exception e)
out.print("Cannot retrieve connection: " + e.toString());
return;
try
PreparedStatement pstmt = con.prepareStatement("SELECT PROJNO FROM MATERIALSLAB.VW_ASPHALTHEADERINFO");
ResultSet results = pstmt.executeQuery();
while (results.next())
out.println(results.getString(1));
catch(Exception ex)
out.print("Got connection, can't execute query: " + ex.toString());
return;
%> -
Bind a huge object to jndi tree in sun one 7
Hi we are loading all the master tables in to objects at the app server startup (SUN ONE 7) and then binding the whole object to the jndi tree. All the tables data in text files comes to about 5 MB and the serilized object with data to about 8 MB. But when the app server tries to bind the object the app server process consumes over 500MB of ram and gives OutOfmemoryError as the total ram is 512MB. why is it consuming so much memory. It does bind an object of about 5 MB but when trying to lookup subsequent to the first lookup it fails. Is this a bug or what??? the same thing works perfectly with Weblogic and Websphere and also Weblogic is very efficient in memory consumption and response time is amazing. For a 5 MB object the lookup takes about 5Secs in Weblogic and about 15Mins in Sun One. We might have to drop the Sun One App Srv and go for Weblogic though we dont want. Kindly provide some guidance. Thanks in advance.
Hi,
Refer http://java.sun.com/products/jndi/tutorial/objects/storing/remote.html
-amol -
Creating JNDI datsource for Sybase 11.2 in Sun One Web Server 6.1
Hi,
I would like to get detailed explanation on how to create JNDI datasource in Sun One Web Server 6.1 for Sybase 11.2. Can anybody help?Did you read and follow the WebServer manual? Since you did not even provide a version number, I'll point you at the latest:
http://docs.sun.com/app/docs/coll/WebServer_05q1
Thanks,
-- Marco -
Import netscape.ldap.* ; is it not supported in Sun one LDAP server
import netscape.ldap.*;
is the above line not supported n Sun One LDAP directory Server
if that is the case what should i do
wenever i compile my code the error tat comes up is : package netscap.ladp does not exists
need help immediately
my code is as follows
import netscape.ldap.*;
import java.util.*;
* Simple search program to experiment with filters
public class SearchFilter {
* Do a subtree search using a specified filter
* @parm args host, port, authDN, password, baseDN, filter
public static void main(String[] args) {
if (args.length != 6) {
System.out.println("Usage: java FilterSearch " + "<host> <port> " + "<authdn> <password> " + "<baseDN> <filter>");
System.out.println("Example:");
System.out.println(" java FilterSearch " + "localhost 389 " + "\"\" \"\" " + "\"o=airius.com\" " + "\"(|(cn=sam*)(cn=b*))\"");
System.exit(1);
}Couldn't you download the netscape.ldap package (iPlanet LDAP SDK) and put its jars in your app classpath?
The suggested way to replace netscape.ldap package is to use only JNDI calls, but maybe they can not fulfill all your needs.
By the way, you can get the source code for that package in Mozilla.org site.
(Note: if you are using Netscape LDAP SDK for parsing/generating ASN.1 streams including X.509 certificates, try using BouncyCastle instead of netscape.ldap.ber.stream package - I had to modify several classes from Netscape's package that is not meant to handle certificates, but LDAP streams...) -
Setup MySQL datasource for Sun ONE Studio
Hello all,
I've tried to post this message on the Sun ONE studio forum, however, there were compilation errors with JSP pages. As I needed the answer urgently, I decided to get some help here.
I've successfully made connection to MySQL database during the CMP development. However, when I tried to run it, it said the JNDI Datasource can't be blank and provide username & password if necessary. I went back and gave it a name as jdbc/MySQL, and also provided the username & password. I then reran the app, and I got the following error
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: Unable to get JDBC DataSource for CMP ....
I've mounted the mysql.jar and hacked some other things to no success. Please help.
Thanks & regards,
ThinhHi,
Try validating your data source using
http://developer.iplanet.com/tech/tools/dbping_overview.jsp
Get back in case of any issues -
MySQL & Sun ONE studio problem
hello all,
It seemed like I've got the data source & database driver stuff setup to work with MySQL database in Sun ONE studio. However, when I tried to run the helloworld_TestApp (CMP App), I've got the SQL syntax error. I tried to look at the sun-j2ee-ri.xml, and it looked just fine to me.. please help.
Here is the XML descriptor
<?xml version="1.0" encoding="UTF-8"?>
<j2ee-ri-specific-information>
<server-name></server-name>
<rolemapping/>
<web>
<display-name>helloworld_TestApp</display-name>
<servlet>
<servlet-name>dispatch</servlet-name>
</servlet>
<servlet>
<servlet-name>error</servlet-name>
</servlet>
<servlet>
<servlet-name>viewer</servlet-name>
</servlet>
<context-root>helloworld_TestApp</context-root>
<ejb-ref>
<ejb-ref-name>ejb/TestedEJB</ejb-ref-name>
<jndi-name>helloworld</jndi-name>
</ejb-ref>
</web>
<enterprise-beans>
<unique-id>1</unique-id>
<ejb>
<ejb-name>helloworld</ejb-name>
<jndi-name>helloworld</jndi-name>
<ejb20-cmp>
<sql-statement>
<operation>loadRow</operation>
<sql>SELECT "lastname" FROM "helloworld" WHERE "firstname" = ? </sql>
</sql-statement>
<sql-statement>
<operation>storeRow</operation>
<sql>UPDATE "helloworld" SET "lastname" = ? WHERE "firstname" = ? </sql>
</sql-statement>
<sql-statement>
<operation>deleteRow</operation>
<sql>DELETE FROM "helloworld" WHERE "firstname" = ? </sql>
</sql-statement>
<sql-statement>
<operation>deleteTable</operation>
<sql>DROP TABLE "helloworld"</sql>
</sql-statement>
<sql-statement>
<operation>findByPrimaryKey</operation>
<sql>SELECT "firstname" FROM "helloworld" WHERE "firstname" = ? </sql>
</sql-statement>
<sql-statement>
<operation>createRow</operation>
<sql>INSERT INTO "helloworld" ( "firstname" , "lastname" ) VALUES ( ? , ? )</sql>
</sql-statement>
<sql-statement>
<operation>createTable</operation>
<sql>CREATE TABLE "helloworld" ("firstname" VARCHAR(255) NOT NULL , "lastname" VARCHAR(255), CONSTRAINT "pk_helloworl" PRIMARY KEY ("firstname") )</sql>
</sql-statement>
<create-table-deploy>true</create-table-deploy>
<delete-table-undeploy>false</delete-table-undeploy>
</ejb20-cmp>
<principal>
<name></name>
</principal>
<ior-security-config>
<transport-config>
<integrity>supported</integrity>
<confidentiality>supported</confidentiality>
<establish-trust-in-target>supported</establish-trust-in-target>
<establish-trust-in-client>supported</establish-trust-in-client>
</transport-config>
<as-context>
<auth-method>username_password</auth-method>
<realm>default</realm>
<required>true</required>
</as-context>
<sas-context>
<caller-propagation>supported</caller-propagation>
</sas-context>
</ior-security-config>
</ejb>
<cmpresource>
<ds-jndi-name>jdbc/MySQL</ds-jndi-name>
<default-resource-principal>
<name>root</name>
<password>root</password>
</default-resource-principal>
</cmpresource>
</enterprise-beans>
</j2ee-ri-specific-information>
And here is the error message:
The exception java.rmi.ServerException was thrown when invoking findByPrimaryKey with parameters:
thinh
Following is the stack trace:
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: nested exception is: java.sql.SQLException: Syntax error or access violation: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '"helloworld" WHERE "firstname" = 'thinh'' at line 1; nested exception is: java.sql.SQLException: Syntax error or access violation: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '"helloworld" WHERE "firstname" = 'thinh'' at line 1 at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.wrapException(Util.java:345) at javax.rmi.CORBA.Util.wrapException(Util.java:277) at ..
...more and more..Where are you running your application? I assume you
are running your application on RI. Are you running
on RI or S1AS?I am running my application on R1, is there a problem with it? can the S1AS solve the problem?
Thanks & regards,
Tim -
Remote Interface problem using Sun ONE App & web server
HI,
1) I am using an S'less SB. I have local & remote interfaces. I am using the sun one appserver7 & the sun ones's htttp server. By default it doesnt pick up the remote interfaces is it ? How do i make my remote interfaces work ? what are the changes required in config/xml ?
2) However i changed my client code (i.e my action class which is called by the struts action servlet ) to access the localhome rather than the remote home, but then i get java.lang.classcastexception.
pls help !
sanjayHi parsuram,
Thanks for the tip. After looking at the sample source code, I did finally figure out the solution - so I'll post it in case anyone else happens to be working with websphere studio has the same issue deploying on sun one.
To access local interface ejb, you must have the following
1. ejb-local-ref tag in the ejb-jar.xml like so underneath the <session> or <entity> tag of the bean which you plan to access the local ejb with.
<ejb-local-ref>
<ejb-ref-name>TestL</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>memory.simple.TestLLocalHome</local-home>
<local>memory.tool.simple.TestLLocal</local>
<ejb-link>TestL</ejb-link>
</ejb-local-ref>
2. similar ejb-ref tag in sun-ejb-jar.xml
<ejb-ref>
<ejb-ref-name>TestL</ejb-ref-name>
<jndi-name>localejbs/module_memory.betaEJB/TestL68640023372300293</jndi-name>
</ejb-ref>
note: sun generates the <jndi-name> and overwrites whatever you put in that tag no matter what you put in there.
3. here is the code to access
Context initial = new InitialContext();
TestLLocalHome tlHome=(TestLLocalHome) Initial.lookup
("TestL");
//the string must match <ejb-ref-name> underneath <ejb-local-ref>
4. note that the jndi name for the local interface bean becomes irrelevant. only the <ejb-ref-name> in the ejb-jar and sun-ejb-jar matter. furthermore, both <ejb-ref-name> must be the same or you won't be able to deploy.
5. This is completely my fault for not checking the "proper" way to access local interfaces. in websphere, they let you get away without the ejb-ref tags and just use the string "local:/TestL"!
-matt -
HELP PLEASE: Tomcat 3 - Sun ONE Migration Problems
Hi everybody. We are new Sun One users. We are trying unsuccessfully to migrate our tomcat application to this environment. in order to deploy it we have created a WAR file from the Netbeans Ide and we are trying to load it into Sun One AS... but it seems there is something wrong with the process becouse we don't have access to the defined jdbc resources. Any help would be very apreciated... and please, excuse my English.
Javier MorenoThanks a lot of for your fast answer, but we haven't don't too much progress...
dbping shows a message about "java.lang.NoSuchMethodException: setdataSourceName"
wich probably means mysql driver isn't fully implemented. anyway i will try
to describe the steps we make to create de pool hoping you will be able to
help us...
That's what we do:
- first, we create a Connection pool:
name -> MySQLPool
database vendor -> Other
datasource class -> com.mysql.jdbc.jdbc2.optional.MysqlDataSource
serverName -> localhost
portNumber -> 3306
user -> test
password -> test
databasename -> jdbc:mysql://localhost/pol
datasourcename -> pol
- then, we define the resource:
jndi name -> jdbc/jdbc-pol01
pool name -> MySQLPool
data source enabled -> true
- in the web.xml of the application we got (just before /webapp):
<resource-ref>
<description>DB Connection</description>
<res-ref-name>jdbc/jdbc-pol01</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
- and we obtain the connection with a chunk of code like this:
ctx = new InitialContext();
dsName = "java:comp/env/jdbc/jdbc-pol01";
ds = (javax.sql.DataSource) ctx.lookup(dsName);
con = ds.getConnection();
If we don't write the resource-ref element at web.xml it fails at the lookup
step (not finding the resource). but when we add the element the appserver
claims "Error loading new module in virtual server: javax.naming.InvalidNameException: Real jndi name cannot beempty for jdbc/jdbc-polds.
We don't know what to do and the death line is comming here fast... any help
would be very much apreciated.
Thanks in advance, good karma.
jv -
HTTP transport and Sun ONE Message Queue
How do I get the HTTP transport to work? The docs don't seem to be correct.
There are a couple of errors in the Sun ONE Message Queue docs that shipped with
the product.
The following are corrections for those errors.
Servlet configuration
Please note the following correction in the Sun ONE Message Queue 2.0
Administration Guide, Appendix B -
The class name of the HTTP Servlet in Step 4 of the "Configuring the Tunnel Servlet"
section is given as:
com.sun.messging.jmq.transport.httptunnel.servlet.HTTPTunnelServlet
The correct class name is :
com.sun.messaging.jmq.transport.httptunnel.servlet.HttpTunnelServlet
Client setup for HTTP support
1.The following connection factory attributes must be specified to use the HTTP
tunnel connection support.
JMQConnectionType :
Set this attribute to "HTTP".
JMQConnectionURL :
Set this attribute to the URL that will be used to connect to the Sun ONE
Message Queue message service (i.e. the URL for the HTTP tunnel servlet).
Note that there is no need to specify the JMQConnectionHandler attribute as
mentioned in the Sun ONE Message Queue 2.0 Administration Guide -
Appendix B.
2.Before running the client application, set the CLASSPATH variable to include
jmqutil.jar in addition to the standard Sun ONE Message Queue jar files.
This file is located at "/opt/SUNWjmq/lib/jmqutil.jar".
If the "jmqutil.jar" file is not included in the CLASSPATH, the client will get a
"java.lang.NoClassDefFoundError" exception for the class
"com/sun/messaging/jmq/util/JMQTimerTask".
3.If you are using an HTTP proxy, set "http.proxyHost" to the proxy server host
name, and "http.proxyPort" to the proxy server port number using the -D
command line option.
An example command line would look like this:
java -classpath
/opt/SUNWjmq/lib/jms.jar:/opt/SUNWjmq/lib/jmq.jar:
/opt/SUNWjmq/lib/jndi.jar:.:/opt/SUNWjmq/lib/jmqutil.jar
-DJMQConnectionType=HTTP
-DJMQConnectionURL=http://webserver:80/imq/servlet ClientApplicaiton -
Integrating Sun One 8 with 3rd party queue provider
Hi,
I am trying to deploy a Message driven Bean based application on
"Sun System Java Application Server 8.1". The MDBs are configured to listen on queues which are hosted on a third party software "SeeBeyond SRE 5.0.4 ".
We already have a working environment on sun one 7.0.0._3b.
Doing following things on 8.1:
1. Creating a queue on "SeeBeyond SRE 5.0.4".
2. Binding the queue on a LDAP server
3. Creating a "remote-jndi-resource" on "Sun System Java Application Server 8.1" so that it looks-up in the LDAP and binds to the physical queue on Seebeyond
4. Creating an MDB application which listens to the above created queue and deploys it on the Application server.
The error message while we deploy the application/boot the server, is
[#|2005-11-11T14:30:54.924+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb.mdb|_ThreadID=15;|com.sun.enterprise.connectors.ConnectorRuntimeException
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/BridgeQueue
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:560)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:444)
at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
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:95)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:224)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:164)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:496)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:872)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:856)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:424)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:288)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:155)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:258)
at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:87)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:633)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:361)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:396)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:702)
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:302)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:357)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor27.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:272)
at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:119)
at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:360)
at java.lang.Thread.run(Thread.java:534)
|#]
[#|2005-11-11T14:30:54.939+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=15;|EJB5090: Exception in creating EJB container [
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/BridgeQueue]|#]
[#|2005-11-11T14:30:54.939+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=15;|appId=bridge-app moduleName=bridge-ejb_jar ejb
Name=TMSBridgeMessageEJB|#]
[#|2005-11-11T14:30:54.939+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core.classloading|_ThreadID=15;|LDR5004: UnExpected error occured while cr
eating ejb container
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/BridgeQueue
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:560)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:444)
at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
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:95)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:224)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:164)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:496)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:872)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:856)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:424)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:288)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:155)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:258)
at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:87)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:633)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:361)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:396)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:702)
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:302)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:357)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor27.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:272)
at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:119)
at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:360)
at java.lang.Thread.run(Thread.java:534)
|#]
[#|2005-11-11T14:30:54.955+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=15;|CORE5021: Application NOT loaded: [bridge-app]|#]
[#|2005-11-11T14:30:54.986+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.stream.err|_ThreadID=15;|com.sun.enterprise.admin.event.AdminEventListene
rException: Error while loading application [bridge-app]. Please refer to the server log for more details.
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:501)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:872)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:856)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:424)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:288)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:155)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:258)
at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:87)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:633)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:361)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:396)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:702)
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:302)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:357)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor27.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:272)
at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:119)
at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:360)
at java.lang.Thread.run(Thread.java:534)
|#]
[#|2005-11-11T14:30:55.018+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.
system.tools.admin|_ThreadID=15;|ADM5603:Event listener error [Error while loadi
ng application [bridge-app]. Please refer to the server log for more details. ]|
[#|2005-11-11T14:30:55.033+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.sys
tem.tools.admin|_ThreadID=15;|ADM1042:Status of dynamic reconfiguration event pr
ocessing:[listener_error]|#]
[#|2005-11-11T14:30:55.033+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.
system.tools.admin|_ThreadID=15;|ADM1075:Error on listening event:[Error while l
oading application [bridge-app]. Please refer to the server log for more details
. ]|#]
-Kshitij.Hi,
I am trying to deploy a Message driven Bean based application on
"Sun System Java Application Server 8.1". The MDBs are configured to listen on queues which are hosted on a third party software "SeeBeyond SRE 5.0.4 ".
We already have a working environment on sun one 7.0.0._3b.
Doing following things on 8.1:
1. Creating a queue on "SeeBeyond SRE 5.0.4".
2. Binding the queue on a LDAP server
3. Creating a "remote-jndi-resource" on "Sun System Java Application Server 8.1" so that it looks-up in the LDAP and binds to the physical queue on Seebeyond
4. Creating an MDB application which listens to the above created queue and deploys it on the Application server.
The error message while we deploy the application/boot the server, is
[#|2005-11-11T14:30:54.924+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb.mdb|_ThreadID=15;|com.sun.enterprise.connectors.ConnectorRuntimeException
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/BridgeQueue
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:560)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:444)
at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
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:95)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:224)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:164)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:496)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:872)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:856)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:424)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:288)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:155)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:258)
at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:87)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:633)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:361)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:396)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:702)
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:302)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:357)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor27.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:272)
at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:119)
at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:360)
at java.lang.Thread.run(Thread.java:534)
|#]
[#|2005-11-11T14:30:54.939+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=15;|EJB5090: Exception in creating EJB container [
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/BridgeQueue]|#]
[#|2005-11-11T14:30:54.939+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=15;|appId=bridge-app moduleName=bridge-ejb_jar ejb
Name=TMSBridgeMessageEJB|#]
[#|2005-11-11T14:30:54.939+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.core.classloading|_ThreadID=15;|LDR5004: UnExpected error occured while cr
eating ejb container
com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/BridgeQueue
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:560)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:444)
at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:187)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:221)
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:95)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:224)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:164)
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:496)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:872)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:856)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:424)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:288)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:155)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:258)
at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:87)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:633)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:361)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:396)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:702)
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:302)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:357)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor27.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:272)
at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:119)
at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:360)
at java.lang.Thread.run(Thread.java:534)
|#]
[#|2005-11-11T14:30:54.955+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=15;|CORE5021: Application NOT loaded: [bridge-app]|#]
[#|2005-11-11T14:30:54.986+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.system.stream.err|_ThreadID=15;|com.sun.enterprise.admin.event.AdminEventListene
rException: Error while loading application [bridge-app]. Please refer to the server log for more details.
at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:501)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:872)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:856)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:424)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:288)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:155)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:258)
at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:87)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:633)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:361)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:396)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:702)
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:302)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:357)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor27.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:272)
at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:119)
at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:360)
at java.lang.Thread.run(Thread.java:534)
|#]
[#|2005-11-11T14:30:55.018+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.
system.tools.admin|_ThreadID=15;|ADM5603:Event listener error [Error while loadi
ng application [bridge-app]. Please refer to the server log for more details. ]|
[#|2005-11-11T14:30:55.033+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.sys
tem.tools.admin|_ThreadID=15;|ADM1042:Status of dynamic reconfiguration event pr
ocessing:[listener_error]|#]
[#|2005-11-11T14:30:55.033+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.
system.tools.admin|_ThreadID=15;|ADM1075:Error on listening event:[Error while l
oading application [bridge-app]. Please refer to the server log for more details
. ]|#]
-Kshitij. -
Sun One EJB problem - PortableRemoteObject.narrow ClassCastException...
Hi all,
I'm using Sun One app server 7 for the first time and am having a bit of difficulty. I have deployed a very simple EAR containing one stateless session bean just to test it. The ear appears to have deployed correctly but PortableRemoteObject.narrow is throwing a ClassCastException when trying to do a remote lookup on the bean.
I'm using the following env settings...
initialContextFactory = com.sun.enterprise.naming.SerialInitContextFactory
providerUrl = iiop://127.0.0.1:3700The lookup appears to work okay - this line of code executes successfully
Object objref = initialContext.lookup(jndiHomeName);...objref appears to initalise succesfully (if I toString() it I get an iiop stream of some sort). However, it is the next line that is failing...
Object obj = PortableRemoteObject.narrow(objref, homeClass);...this is the exception I get...
java.lang.ClassCastException
at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(Unknown Source)
at javax.rmi.PortableRemoteObject.narrow(Unknown Source)
at com.scorlog.ServiceLocator.getRemoteHome(ServiceLocator.java:145)Furthermore, when PortableRemoteObject.narrow() executes, I get the following console exception on the server...
com.sun.corba.ee.internal.core.DuplicateServiceContext
at com.sun.corba.ee.internal.core.ServiceContexts.put(ServiceContexts.java:208)
at com.sun.corba.ee.internal.iiop.ServerRequestImpl.getServiceContextsForReply(ServerRequestImpl.java:258)
at com.sun.corba.ee.internal.iiop.ServerRequestImpl.createResponse(ServerRequestImpl.java:89)
at com.sun.corba.ee.internal.POA.SubcontractResponseHandler.createReply(SubcontractResponseHandler.java:50)
at org.omg.CosNaming.NamingContextExtPOA._invoke(NamingContextExtPOA.java:377)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatchToServant(GenericPOAServerSC.java:569)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.internalDispatch(GenericPOAServerSC.java:211)
at com.sun.corba.ee.internal.POA.GenericPOAServerSC.dispatch(GenericPOAServerSC.java:113)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:275)
at com.sun.corba.ee.internal.iiop.RequestProcessor.process(RequestProcessor.java:83)
at com.iplanet.ias.corba.ee.internal.iiop.ServicableWrapper.service(ServicableWrapper.java:25)
at com.iplanet.ias.util.threadpool.FastThreadPool$ThreadPoolThread.run(FastThreadPool.java:288)
at java.lang.Thread.run(Thread.java:534)
FINE: No SAS context element found in service context listI have seen the forum that other users have had similar problems and the suggestion was that the client can't see the ejb stubs. I don't think this is the problem in my case as I deployed the same ear on weblogic 7 (obviously substituting sun-ejb-jar.xml for a weblogic-ejb-jar.xml) and successfully executed the same client code for the remote lookup.
My feeling is that the problem revolves around the JNDI binding. Could it be the case that even though the object is binding properly, the app server doesn't realise it is an ejb and not a jdbc/jms/mail object? The documentation gives details on looking up a JDBC, javamail, URL, JMS resource (http://docs.sun.com/source/817-2177/djjndi.html) but not ejb so I could be doing something simple wrong here...
My sun-ejb-jar.xml is as follows....
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by XDoclet -->
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>SBTest</ejb-name>
<jndi-name>ejb/SBTestBean</jndi-name>
</ejb>
</enterprise-beans>
</sun-ejb-jar>However, I noticed on another thread, a user had some additional elements under their <ejb> tag like this...
<?xml version="1.0" encoding="UTF-8"?>
<sun-ejb-jar>
<enterprise-beans>
<name>Ejb1</name>
<ejb>
<ejb-name>HelloBean</ejb-name>
<jndi-name>HelloBean</jndi-name>
<ejb-ref>
<ejb-ref-name>ejb/helloBean</ejb-ref-name>
<jndi-name>HelloBean</jndi-name>
</ejb-ref>
</ejb>
</enterprise-beans>
</sun-ejb-jar>However, when I tried to add and <ejb-ref> element to my xml doc the ear failed to deploy. This is the error I get in the admin console...
Error
Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler -- --
Failed to load deployment descriptor for: testApp cause: Error converting J2EE-
specific ejb xml to object representation: testApp.jar app_testApp Generated by
XDoclet This bean has no ejb reference by the name of [ejb/SBtest]
ejb/SBTestSBTestThis problem is eating up my time and being made all the more frustrating by the fact that a) it deploys on weblogic and b) the documentation is terrible. Even the sample application that comes with sun one only provides the .class files for the code that does the ejb look up and not the .java so you can't see how they hell they do it!
Unfortunately I am tied to using Sun One so I really need to solve this problem fast. If anyone can provide any help I'd greatly appreciate it.
Cheers,
John :)I am having the same problem after upgrading to Sun One from iplanet. Any clue?
-
Sun One Webserver Connection Pooling - javax.naming.NamingException
I'm trying to configure a container managed datasource in Sun One Webserver. I've followed the steps given in the Sun One Webserver Administrator's Guide, however when I try to lookup the datasource I get a "javax.naming.NamingException: Cannot create resource instance" exception (full stack trace below). I have verified the database connection info (URL/user/password) is correct using Squirrel and I've appended the location of classes12.jar to the server's classpath in server.xml. Relevant snippets from the configuration files, my lookup code, and the stack trace are below. I've been beating my head on this for almost two days and I would appreciate any tips on how to debug this.
web.xml
<resource-ref>
<description>JNDI DataSource</description>
<res-ref-name>jdbc/web920</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Sharable</res-sharing-scope>
</resource-ref>
sun-web.xml
<resource-ref>
<res-ref-name>jdbc/web920</res-ref-name>
<jndi-name>jdbc/web920</jndi-name>
</resource-ref>
server.xml
<RESOURCES>
<JDBCCONNECTIONPOOL name="web920" datasourceclassname="oracle.jdbc.pool.OracleDataSource" steadypoolsize="8" maxpoolsize="32" poolresizequantity="2" idletimeout="300" maxwaittime="60000" connectionvalidationrequired="off"
connectionvalidationmethod="auto-commit" validationtablename="" failallconnections="off" transactionisolationlevel="read-uncommitted" isolationlevelguaranteed="off">
<PROPERTY name="URL" value="jdbc:oracle:thin:@d1web920.mydomain.com:1521:d1web920" />
<PROPERTY name="User" value="<username>" />
<PROPERTY name="Password" value="<password>" />
</JDBCCONNECTIONPOOL>
<JDBCRESOURCE jndiname="jdbc/web920" poolname="web920" enabled="on" />
</RESOURCES>
Lookup code
private static DataSource getDataSource(){
DataSource ds = null;
try {
Object o = new InitialContext().lookup("java:comp/env/jdbc/web920");
ds = (DataSource) o;
} catch (NamingException e) {
System.out.println("Error retrieving DataSource.");
e.printStackTrace();
return ds;
Stack Trace
warning: CORE3283: stderr: javax.naming.NamingException: Cannot create resource instance
warning: CORE3283: stderr: at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:167)
warning: CORE3283: stderr: at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
warning: CORE3283: stderr: at org.apache.naming.NamingContext.lookup(NamingContext.java:834)
warning: CORE3283: stderr: at org.apache.naming.NamingContext.lookup(NamingContext.java:181)
warning: CORE3283: stderr: at org.apache.naming.NamingContext.lookup(NamingContext.java:822)
warning: CORE3283: stderr: at org.apache.naming.NamingContext.lookup(NamingContext.java:181)
warning: CORE3283: stderr: at org.apache.naming.NamingContext.lookup(NamingContext.java:822)
warning: CORE3283: stderr: at org.apache.naming.NamingContext.lookup(NamingContext.java:181)
warning: CORE3283: stderr: at org.apache.naming.NamingContext.lookup(NamingContext.java:822)
warning: CORE3283: stderr: at org.apache.naming.NamingContext.lookup(NamingContext.java:194)
warning: CORE3283: stderr: at org.apache.naming.SelectorContext.lookup(SelectorContext.java:183)
warning: CORE3283: stderr: at javax.naming.InitialContext.lookup(InitialContext.java:351)
warning: CORE3283: stderr: at mil.army.usaac.portal.util.DatabaseConnectionManager.getDataSource(DatabaseConnectionManager.java:99)
warning: CORE3283: stderr: at mil.army.usaac.portal.util.DatabaseConnectionManager.init(DatabaseConnectionManager.java:40)
warning: CORE3283: stderr: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
warning: CORE3283: stderr: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
warning: CORE3283: stderr: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
warning: CORE3283: stderr: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
warning: CORE3283: stderr: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
warning: CORE3283: stderr: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
warning: CORE3283: stderr: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)we are trying to connect MS Access thru tomcat and it is giving the above exception
i have changed the server.xml
<Resource name="jdbc/Mess" auth="Container" scope="Shareable" type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/Mess">
<parameter>
<name>maxWait</name>
<value>5000</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>4</value>
</parameter>
<parameter>
<name>password</name>
<value>admin</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:odbc:Mess</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>sun.jdbc.odbc.JdbcOdbcDriver</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>2</value>
</parameter>
<parameter>
<name>username</name>
<value>admin</value>
</parameter>
</ResourceParams>
web.xml
<resource-ref>
<description>Access Datasource example</description>
<res-ref-name>jdbc/Mess</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
java class
Context initContext = new InitialContext();
DataSource ds = (DataSource)initContext.lookup("java:/comp/env/jdbc/Mess");
con = ds.getConnection();
Please help....... -
Can't deploy Simple 2.0 CMP Entity Bean into Sun One Server 7
Dear all:
I use JBuilder9 + SunOne Plug-in to
build a Simple Entity Bean, but I can't
deploy it into SunOne 7 Server that return
error message:
Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler -- -- Error while processing CMP beans.
But I use JBuilder9 + JBoss 3.x Plug-in
that corrent run on JBoss 3.2 RC
All code are generated by JBuilder9 EJB Designer
and only have PK finder.
Our deploy description flile are:
ejb-jar.xml=============================
<?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>
<enterprise-beans>
<entity>
<display-name>Enterprise1</display-name>
<ejb-name>Enterprise1</ejb-name>
<home>untitled1.Enterprise1RemoteHome</home>
<remote>untitled1.Enterprise1Remote</remote>
<local-home>untitled1.Enterprise1Home</local-home>
<local>untitled1.Enterprise1</local>
<ejb-class>untitled1.Enterprise1Bean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>untitled1.Enterprise1PK</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>Enterprise1</abstract-schema-name>
<cmp-field>
<field-name>inDate</field-name>
</cmp-field>
<cmp-field>
<field-name>sndSeq</field-name>
</cmp-field>
<cmp-field>
<field-name>msgSnd</field-name>
</cmp-field>
<cmp-field>
<field-name>msgRcv</field-name>
</cmp-field>
<cmp-field>
<field-name>brkId</field-name>
</cmp-field>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>Enterprise1</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
=================================
sun-ejb-jar.xml=====================
<?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'>
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>Enterprise1</ejb-name>
<jndi-name>Enterprise1Remote</jndi-name>
</ejb>
<pm-descriptors>
<pm-descriptor>
<pm-identifier>IPLANET</pm-identifier>
<pm-version>1.0</pm-version>
<pm-class-generator>com.iplanet.ias.persistence.internal.ejb.ejbc.JDOCodeGenerator</pm-class-generator>
<pm-mapping-factory>com.iplanet.ias.cmp.NullFactory</pm-mapping-factory>
</pm-descriptor>
<pm-inuse>
<pm-identifier>IPLANET</pm-identifier>
<pm-version>1.0</pm-version>
</pm-inuse>
</pm-descriptors>
<cmp-resource>
<jndi-name>jdo/sample-cmp</jndi-name>
<default-resource-principal>
<name>mv01</name>
<password>mv01</password>
</default-resource-principal>
</cmp-resource>
</enterprise-beans>
</sun-ejb-jar>
===========================
sun-cmp-mappings.xml===============
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-cmp-mappings PUBLIC '-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 OR Mapping //EN' 'http://www.sun.com/software/sunone/appserver/dtds/sun-cmp-mapping_1_0.dtd'>
<sun-cmp-mappings>
<sun-cmp-mapping>
<schema>META-INF/mySchema</schema>
<entity-mapping>
<ejb-name>Enterprise1</ejb-name>
<table-name>TSE_MSG_T</table-name>
<cmp-field-mapping>
<field-name>inDate</field-name>
<column-name>INDATE</column-name>
</cmp-field-mapping>
<cmp-field-mapping>
<field-name>sndSeq</field-name>
<column-name>SNDSEQ</column-name>
</cmp-field-mapping>
<cmp-field-mapping>
<field-name>msgSnd</field-name>
<column-name>MSGSND</column-name>
</cmp-field-mapping>
<cmp-field-mapping>
<field-name>msgRcv</field-name>
<column-name>MSGRCV</column-name>
</cmp-field-mapping>
<cmp-field-mapping>
<field-name>brkId</field-name>
<column-name>BRKID</column-name>
</cmp-field-mapping>
</entity-mapping>
</sun-cmp-mapping>
</sun-cmp-mappings>
=========================I remember getting errors like that. The only thing I see is in the map file. When I
did mine I used TABLENAME.CMPFIELD to map columns to CMP attributes.
TSE_MSG_T.INDATE
TSE_MSG_T.SNDSEQ
for column names in the sun-cmp-mappings.xml file.
For any other errors set the logging for server1 or which one you are using to "finest".
Try the deploy, shut down the server, and when you view the log, start at the bottom
and keep scrolling up to the top of each stack trace and you should get a more
specific error explanation at about the 3rd or 4th stack trace. -
Sun One App Server 8.1,Sun One Message Q3.6,administered objects in LDAP
Hi,
Has anyone tried hosting an MDB on Sun One App Server 8.1 listening to a queue on Sun One Message Queue 3.6 through administered objects in directory server...? It looks quite straight forward but somehow it doesn't seems to work. Any idea if Sun one app server supports this type of architecture...?
Regards,
PriteshHi,
Even I didn't see any obvious reason why it shouldn't work untill I found that Sun One App Server 8.1 does not support external JNDI lookup to Sun MQ 3.6 through administered objects. However, it is possible using a newly released generic resource adapter for JMS 1.5 RC1. I am still fighiting on it and let you know if it works.
I was getting an error "JMS resource can not be created" during deployment time.
Regards,
Pritesh Thakor
Maybe you are looking for
-
Not able to change the name of the attribute of the Table operator.
We are trying to create OMB scripts to automate certain tasks. As a part of this, there is a requirement to change the attribute name of table operators (which by default gets the name of the column). It is possible to change the attribute name from
-
Lost all pictures and contact from i phone 4s when trying to download to a laptop
lost all pictures and contracts from a 4s phone trying to download to a laptop
-
I posted about this before but now realize I may have misdiagnosed the problem. I have a DV quicktime file that play perfectly. When brought into FCE 3.5.1 however, there's one scene that becomes very distorted. Tom Wolsky originally suggested it was
-
Error inF2F mulitiline scenario using substring
Hi, I am doing a F2F mulitiline scenario using substring In AdapterFramework , i am getting this message Sender Adapter v1014 for Party '', Service 'YAMAHA_BUSYS': Configured at 19:12:31 2008-10-22 Initialization error: Conversion initialization fail
-
Text box tool remains "on" after use
Adobe Reader 11.0.09 on Mac OSX 10.6.8 (antique) QUESTION: How to resolve failure of text-box tool to inactivate after use. Instead, creates numerous undesired text boxes. I am using Adobe Reader 11.0.09 on a Mac with OS 10.6.8 (ancient). Under the