Tomcat , JMS & J2ee RI

anyone here knows if there is a way to configure Tomcat to support JMS on servlets by using the J2ee Reference Implementation Server as the JMS provider? I know there is openjms and other jakarta components that can help tomcat do jms, but is there a way to do it with the j2ee ri?

Both The tomcat.jar and j2ee.jar implements apache.* classes, and they are conflicting with each other. If you add "j2ee.jar" to Tomcat's classpath, you'll get an error message trying to start Tomcat.
The work around I made on my W2K box (Tomcat 3.3a with J2EE 1.3.1):
I created a temporary directory: d:\mine_j2ee_classes and unzip j2ee.jar to this directory. Then I renamed d:\mine_j2ee_classes\org\apache to d:\mine_j2ee_classes\org\apache_orig. After that, I added d:\mine_j2ee_classes to my Tomcat classpath, and it works fine. By doing this, I use J2EE as the JMS provider, but only use Tomcat's apache.* implementation.
Ye

Similar Messages

Problem with Sender JMS J2EE adapter...

I have configured the sender JMS J2EE adpater. I am getting this error at Adapter monitoring:
<b>Sender channel. Details: Last Exception during send at Fri May 25 09:44:18 CEST 2007: Error converting Message: 'java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 1: missing structure(s) in last recordset'.</b>
I am using recordset structure as Header,1,Item,99999. and also i am ignoring the recordsetName...i tried confiuring the File adapter using same parameters as in JMS adapter it is not giving any error at Adapter Monitoring.
Also i configured File adapter by putting in their the parameters of J2EE JMS adapter in Module tab, it too worked...
so What is exactly this error, if anyone can please tell me...

Hi,
Check some links for FCC
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
File Receiver with Content Conversion
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
File Receiver with Content Conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani

Problem in Sender JMS J2EE adapter....

Hello All.
I have configured the sender JMS J2EE adpater. I am getting this error at Adapter monitoring:
<b>Sender channel. Details: Last Exception during send at Fri May 25 09:44:18 CEST 2007: Error converting Message: 'java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 1: missing structure(s) in last recordset'.</b>
I am using recordset structure as Header,1,Item,99999. and also i am ignoring the recordsetName...i tried confiuring the File adapter using same parameters as in JMS adapter it is not giving any error at Adapter Monitoring.
Also i configured File adapter by putting in their the parameters of J2EE JMS adapter in Module tab, it too worked...
so What is exactly this error, if anyone can please tell me...
Thnsk in Advace

> I think you have to figure out first, which codepage you really have, not just try. Maybe you ask someone or you check with a hex editor.
Hi Stefan,
Finally we solved the problem.
As you said above to figure the the codepage, we asked to our MQ team for the same and found that they are using ISO-8859-1. In XI we were also trying with multiple conbinations (ISO-8859-1, UTF-8 and many more), but didn't get any success.
Finally MQ team changed their encoding to UTF-8 and in XI we used ISO-8859-1 and we get the success in picking the data with spl char. Even though in XI the spl char comes in destorted order but at the receiver end they are in proper shape.
Thanks a lot for your help.
Regards,
Sarvesh

Tomcat to J2EE .... how to convert?

Hi Guys
I have been using tomcat for a while to do my School's Java Servlets and Jsp projects. Now my school require us to use only J2EE for my final year project. Im quite lost... i have done the tutorial for J2EE but still unsure how to make an existing application in TOMCAT to work like in J2EE?
Foe e.g. , I have an application under the webapps folder in tomcat. Its name is XXXAssg. within it there are the web-inf folders,meta INF fodlers and my other jsp and html files. It works fine in Tomcat. However, I do not know how do I bring all this files to J2EE folder and run the J2EE server and host these servlets and JSP pages. I suspect I need to change it into a WAR file and enable the Deplyment tool to add this WAR file in its web component. In that case, how to i change an entire folder into a WAR file? (noticed there are several WAR files in my tomcat WEBAPPS folder as well)
Any help will be appreciated. Thanks ;)

To my limited knwoledge in J2EE, Yes, you need to run deploytool to create an E application and do all the deployement setps to add your components to it (as in the tutorial J2EE). during this process, the deployement tool will do what is needed to tell the J2ee server where to find your fils (jsp, ejb, html, etc).
hope this helps.

Small weblogic.jar for jms/j2ee clients of weblogic

          We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          I attempted to use the whitepaper document distributed by BEA for creating a smaller
          jar file, but it did not work. Has anyone else in the user community successfully
          created the jar file and if so could they give me some insight on how they did
          it.
          Thanks,
          Ashish


Hi Ashish,
          I've personally used the "URL" class loader option with success,
          and I know that several customers have also used this option, as
          well as the other options for years. Feel free to
          post more detail than "it did not work", and I may be able
          to help you out.
          Tom, BEA
          P.S. If 8.1 is an option, you may with to consider using the
          thin client jars it supplies.
          Ashish Bisarya wrote:
          > We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          > to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          > I attempted to use the whitepaper document distributed by BEA for creating a smaller
          > jar file, but it did not work. Has anyone else in the user community successfully
          > created the jar file and if so could they give me some insight on how they did
          > it.
          >
          > Thanks,
          > Ashish

JMS J2EE question

I am using 6.40, and am running JMS queue tests.
The J2EE engine dies frequently, I have to re-install about once a day.
However, I have consistently increased the size of the Data Volume when I install, and as I do this, the time between crashes increased from about 1 day to every 2 to three days. Now I only have to re-install about every 2 to 3 days.
I guess that means I am filling up the data logs or something. The default is about 400 MG, and I have currently set it to 9000 mg and am getting better response. IN fact I am not sure I will have to reinstall this latest implementation, the 9000 mg install seems to be hanging in there so far.
By the way, the crash behavior is that the broker will not accept send or receive JMS messages, and the J2EE engine will not come up, even if I restart the SAP System from the MMC.
Is there any way to periodically flush the data volume or the logs so it will never crash ?
Is there any way to do this in an automated manner?
Thanks, John

Hi John,
You should enable the "overwrite" mode for the log area. Open the Database Manager, go to Configuration -> Log Settings and choose the Overwrite Mode for the Log Area option.
Hope that helps!
Vladimir

TOMCAT & JMS?

Hi,
Does Tomcat supports JMS? If yes how do i configure it for this purpose?
If no then is there any free application server available which supports JMS?
Thanks.

Have a look at the Jakarta commons component called Messenger. It simplifies usage of any JMS product from a servlet level.

Connector for tomcat and j2ee

I have a login system created. It creates accounts into a mysql server at the moment. I want the users to be able to log in. I need the correct details in my "my-DB-plan.xml" file in order to be able to connect to the SQL server. Im not sur what to put in this file or whether im to use a server.xml file
Any Help.Please.

Our[b] login.html page is simple as follows:
<html><head><title>
J2EE SQL Security and Registry System Demo
</title></head><body>
<h1>LOGIN using Derby and J2EE declarative security!</h1>
<form method="POST" action="j_security_check">
Username:<br>
<input size="20" name="j_username">
<br><br>
Password:<br>
<input size="20" name="j_password" type="password">
<input name="submit" type="submit" value="Login">
</form>
</html>The connection is not made on the page but rather the username and password is authenticated by "j_security_check".
It's something to do with the my-db-plan.xml file I think, but I don't know if I'm to replace that file, change it or what..
It's setup for the Derby Database server rather than MySQL. I'm not sure how you'd change it. This login system we are using can be seen here: http://www-128.ibm.com/developerworks/opensource/library/os-ag-logreg2/

J2EE & Tomcat

I have an EJB deployed to the J2EE server and I'm trying to access this EJB from a servlet in a standalone tomcat container. I'm aware of the J2EE server having a servlet container but I want to have servlets and jsp's running in its own container.
How do I get the InitialContext to the J2EE server? What are the values for the following properties? Do I need other properties that I haven't listed?
Hashtable env =new Hashtable()
env.put.(Context.PROVIDER_URL, "myserver:9191"); // should the port be were ejb is listening?
env.put(Context.INITIAL_CONTEXT_FACTORY, "????????????");
Context ctx = new InitialContext(env);

You might try asking this question on the Tomcat user mailing list. There's been some recent discussion about Tomcat and J2EE integration.
(One of the) searchable archives is at http://marc.theaimsgroup.com/?l=tomcat-user&r=1&w=2.
Main mailing list subscribe/unsubscribe page is http://jakarta.apache.org/site/mail2.html.

J2EE Tomcat vs. Tomcat

I need some information regarding the integrated Tomcat.
Does it have all features of the full Tomcat ? And can you update it normally from Apache or do you need a special J2EE Tomcat update ?
In short, I need to know if there is any downside to using J2EE Tomcat compared to Full Tomcat.

The J2EE Tomcat is the same as the regular Tomcat. However, keep in mind that Tomcat comes out with patches fairly often, whereas the J2EE reference implementation is pretty stable and no updates are issued unless there is a critical issue. If I'm not mistaken, the integrated Tomcat in the J2EE 1.3 reference implementation is version 4.0 beta 7. If you go to Jakarta's website, you will notice that Tomcat 4.0 is already past beta and at version 4.0.4.

JWSDP and J2EE Integration: Doesn't work. What's the point?

My problems involve the integration of JWSDP and J2EE as described in these two documents:
http://developer.java.sun.com/developer/technicalArticles/WebServices/wsj2ee/
http://java.sun.com/j2ee/documentation/windows_guide.html
It looks like a long one, but it�s really not that bad. All comments are appreciated.
I�ve numbered each line-paragraph-section for easy reference later.
(1) My ultimate goal is to setup a website that displays data from a database. I will use Java, Apache, Oracle, and whatever else I need to create a website that uses servlets, JavaServer Pages (JSP), and JDBC.
(2) I�ve got four Pentium III computers:
1. Windows 2000 Server to be the web server (MyWebServer, IP = 10.10.1.1).
2. Windows 2000 Professional to be the database server (MyDatabaseServer, IP = 10.10.1.2).
3. Windows 2000 Professional that I use to develop and test (MyDeveloperPC, IP = 10.10.1.3).
4. Windows 2000 Professional that I use as a client to connect to the website (MyClientPC, IP = 10.10.1.4).
(3) On MyWebServer I installed the following:
Java 2 Standard Edition (J2SE)
Java 2 Enterprise Edition (J2EE)
Java Web Services Developer Pack (JWSDP)
The JWSDP tutorial
Apache HTTP Server
(4) The files I downloaded and installed are as follows:
j2sdk-1_4_0-rc-win.exe
j2sdkee-1_3_1-win.exe
jwsdp-1_0-ea1-win.exe
jwsdp-1_0-ea1_01-tutorial.zip
apache_1.3.23-win32-x86-no_src.exe
(5) After installing these products, I set the environment variables as follows:
JAVA_HOME = c:\j2se
J2EE_HOME = c:\j2ee
JWSDP_HOME = c:\jwsdp
Path = c:\j2se\bin;c:\j2ee\bin;c:\jwsdp\bin; [and other previous statements]
(6) I checked to see that Apache is running as a service. It is.
On MyWebServer I start Tomcat and J2EE. Both start properly and are operating simultaneously.
(7) From MyClientPC I open Internet Explorer and in the address box I type:
http://10.10.1.1
This displays the page c:\ApacheHTTP\apache\htdocs\index.html.en (The Apache default server installation page.)
(8) I then enter this address in IE:
http://10.10.1.1:8080
This displays the page c:\jwsdp\webapps\root\index.html (The default JWSDP page).
(9) I then enter this address in IE:
http://10.10.1.1:8000
This displays the page c:\j2ee\public_html\index.html (The J2EE 1.3 Default Home Page).
(10) So far so good. Now I want to test JWSDP as a container for JSP pages.
(11) I use ant to build the converter app found in the tutorial examples (in folder c:\jwsdp\�\tutorial\examples\gs). I then deploy the converter app to the c:\jwsdp\webapps\gs folder.
(12) From MyClientPC I open Internet Explorer and in the address box I type:
http://10.10.1.1:8080/gs
The converter app works perfectly.
(13) To eliminate the need to enter the port number, I create a link from the Apache default server installation page to the converter app. From MyClientPC and enter this address into IE:
http://10.10.1.1
I then click on the link to the converter app and it works perfectly.
(14) Question: Is this the best way to display JSP pages without having to enter the port number?
(15) Now it�s time to integrate JWSDP and J2EE as described in these two documents:
http://developer.java.sun.com/developer/technicalArticles/WebServices/wsj2ee/
http://java.sun.com/j2ee/documentation/windows_guide.html
(16) After I complete this integration I cannot start both Tomcat and J2EE at the same time. This makes sense because they both share port 8080.
I start Tomcat.
(17) From MyClientPC and use Internet Explorer to test the various relevant addresses. Everything works the same as it did before except this one:
http://10.10.1.1:8000
The page cannot be displayed. The J2EE default home page is not displayed, which makes sense because the J2EE port is no longer 8000; it has been changed to 8080.
(18) Now I shutdown Tomcat and start J2EE.
From MyClientPC and use Internet Explorer to test the various relevant addresses:
(19) http://10.10.1.1:8080
Displays the JWSDP default home page.
(20) http://10.10.1.1:8080/gs
The page cannot be displayed. The converter app no longer works.
(21) From MyWebServer and use Internet Explorer to test localhost:
http://localhost:8080
This displays the J2EE default home page.
(22) Question: Why does localhost give me a different page than the IP address?
(23) Question: What was the point of integrating JWSDP and J2EE?
(24) I want to get the converter app working, so I create a .war file and attempt to add it to the J2EE deploytool (see the two integration documents listed above at section 15.) I create the .war file following the instructions in the JWSDP tutorial:
http://java.sun.com/webservices/docs/ea1/tutorial/doc/WebApp3.html#64606
(25) I change to the c:\jwsdp\�\tutorial\examples\gs\build folder.
I then type:
jar cvf converter.war .
A .war file is created.
(26) I open the deploytool: File, New, Application, and I name it �converter�.
I attempt to add the .war file: File, Add to Application, Web WAR.
(27) When I attempt to add the converter.war file I get this error:
�converter.war does not appear to be a valid web JAR.�
I tried a few different attempts, all with the same result. I�m stuck.
(28) I ask again, What was the point of integrating JWSDP and J2EE?
(29) If this is the preferred configuration, how do I display my JSP pages like the converter app?
Please help!!!

The JWSDP tutorial says to be in the �build� folder of the example when issuing the jar command to create the .war file. The build folder is created when I run the �ant build� command.
Attempt 1 from the command prompt in folder c:\jwsdp\tutorial\examples\gs\build>
I typed this command:
jar cvf c:\jaxmservices\converter.war .
In this case I directed the .war file to be placed in a different folder as you suggested. Here�s the output:
added manifest
adding: index.jsp(in = 921) (out= 525)(deflated 42%)
adding: WEB-INF/(in = 0) (out= 0)(stored 0%)
adding: WEB-INF/classes/(in = 0) (out= 0)(stored 0%)
adding: WEB-INF/classes/Converter.class(in = 582) (out= 358)(deflated 38%)
Didn�t work. Same error as before.
Attempt 2 from the same folder:
I typed this command as you suggested (I tried it with and without the final dot):
jar tvf converter.war
Here is the output:
java.io.FileNotFoundException: converter.war (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at sun.tools.jar.Main.run(Main.java:185)
at sun.tools.jar.Main.main(Main.java:904)
I tried a few other variations on these attempts with no luck. I�m stuck.
I�m attempting to create a .war file out of two files: index.jsp and converter.class.
Now that I�ve integrated JWSDP and J2EE, is there some other way that I can run the converter app instead of a .war file and the deploytool? In other words, if I go back to using ant to build and deploy converter, where would I deploy it so that it will work with J2EE?
By the way, it doesn�t have to be converter. I�d be happy if I could get any JSP page to work in J2EE after the integration.
Forever grateful,
Logan

JMS Wrappers can't cache JNDI lookups when using secured queues

Hi All!
We are working on a jms client, inside a webapp(servlets), using Weblogic 9.2 and Weblogic 10.3.
As we want to use secured queues and keep being efficient we tryed to use Weblogic JMS Wrappers, that should work according to the docs:
Enhanced Support for Using WebLogic JMS with EJBs and Servlets
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jms/j2ee.html
But we are facing a problem:
When we define a JMS Wrapper and try to cache JNDI lookups for the QueueConnectionFactory and Queue, as the docs recommend for efficiency, the connection to the queue is ignoring the user/pwd.
The JMS Wrapper is using <res-auth>Application</res-auth>.
We are creating the connection using createQueueConnection(user, pwd) from QueueConnectionFactory and after several tests it seems that the user and password are ingored unless a jndi lookup is made in the same thread, as if when there are not any thread credentials present user and password are ignored for the connection...
so the question is:
That behaviour goes against Weblogic JMS Wrapper documentation, doesn't it?
Is there then any other way to access efficiently secured queues using a servlet as a client? (iit's not an option for us to use mdbs, or ejbs).
If it helps, this seems related to this still opened spring-weblogic issue: SPR-2941 --> http://jira.springframework.org/browse/SPR-2941 and SPR-4720 --> http://jira.springframework.org/browse/SPR-4720
Thanxs
And here goes our DDs and code to reproduce:
First in pretty format:
web.xml --> http://pastebin.com/f5f85e8d4
weblogic.xml --> http://pastebin.com/f2fbe10cc
Client code --> http://pastebin.com/f586d32d9
And now emmebded in the msg:
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app
xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
    <description>WebLogic Descriptor</description>
    <resource-description>
        <res-ref-name>jms/QCF</res-ref-name>
        <jndi-name>weblogic.jms.ConnectionFactory</jndi-name>
    </resource-description>
</weblogic-web-app>weblogic.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
      <display-name> QCFWrapperCredentialsTest </display-name>
      <description> QCFWrapperCredentialsTest </description>
      <servlet id="Servlet_1">
         <servlet-name>QCFWrapperCredentialsTest</servlet-name>
         <servlet-class>QCFWrapperCredentialsTest</servlet-class>
         <load-on-startup>1</load-on-startup>
      </servlet>
      <servlet-mapping id="ServletMapping_1">
         <servlet-name>QCFWrapperCredentialsTest</servlet-name>
         <url-pattern>/Test</url-pattern>
      </servlet-mapping>
     <resource-ref>
        <res-ref-name>jms/QCF</res-ref-name>
        <res-type>javax.jms.QueueConnectionFactory</res-type>
        <res-auth>Application</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
</web-app>And our test client:
import java.io.*;
import java.util.Properties;
import javax.jms.*;
import javax.naming.*;
import javax.servlet.http.*;
public class QCFWrapperCredentialsTest extends HttpServlet {
    QueueConnectionFactory factory = null;
    Queue queue = null;
    String jndiName = "java:comp/env/jms/QCF";
    String queueName= "jms/ColaEntradaConsultas";
    String user = "usuarioColas";
    String pwd = "12345678";
    String userjndi = "usuarioColas";
    String pwdjndi = "12345678";
    String serverT3URL="t3://127.0.0.1:7007";
    public void init() {
        setupJNDIResources();
    private void setupJNDIResources(){
        try {
            Properties props = new Properties();
            props.put("java.naming.factory.initial",
                    "weblogic.jndi.WLInitialContextFactory");
            props.put("java.naming.provider.url",serverT3URL );
            props.put("java.naming.security.principal", userjndi);// usr
            props.put("java.naming.security.credentials", pwdjndi);// pwd
            InitialContext ic = new InitialContext(props);
            factory = (QueueConnectionFactory) ic.lookup(jndiName);
            queue = (Queue) ic.lookup(queueName);
        } catch (NamingException e) {
            e.printStackTrace();
    public void service(HttpServletRequest req, HttpServletResponse res) {
        res.setContentType("text/html");
        Writer wr = null;
        try {
            wr = res.getWriter();
            //Comment this out, do a lookup for each request and it will work
            //setupJNDIResources();
            String user = this.user;
            String pwd = this.pwd;
            //read users and passwords from the request in case they are present
            if (req.getParameter("user") != null) {
                user = req.getParameter("user");
            if (req.getParameter("pwd") != null) {
                pwd = req.getParameter("pwd");
            wr.write("JNDI User: *" + userjndi + "* y pwd: *" + pwdjndi + "*<p>");
            wr.write("Queue User: *" + user + "* y pwd: *" + pwd + "*<p>");
            //Obtain a connection using user/pwd
            QueueConnection conn = factory.createQueueConnection(user, pwd);
            QueueSession ses = conn.createQueueSession(true,
                    Session.SESSION_TRANSACTED);
            QueueSender sender = ses.createSender(queue);
            TextMessage msg = ses.createTextMessage();
            msg.setText("Hi there!");
            conn.start();
            sender.send(msg);
            ses.commit();
            sender.close();
            ses.close();
            conn.close();
        } catch (Exception e) {
            e.printStackTrace();
            try {
                wr.write(e.toString());
            } catch (Exception e2) {
                e2.printStackTrace();
        finally{
            try {
                wr.close();
            } catch (IOException e) {
                e.printStackTrace();
}Edited by: user2525402 on Feb 9, 2010 7:14 PM

Thanks Tom,
Quite a useful response .-)
Leaving aside the fact that weblogic behaviour with jms wrappers and secured queues seems to not be working as the docs says...
Talking about workarounds:
Both workarounds you suggest works, but as you already noted, creating a new JNDI context just to inject credentials into the threads is overkill when high performance is needed.
I also found more information about the same issue here: http://sleeplessinslc.blogspot.com/2009/04/weblogic-jms-standalone-multi-threaded.html
And he suggest the same workaround, injecting credentials
So I tried the second approach, successfully, injecting credentials into the thread using the security API.
This way, using JMS wrappers and injecting credentials into the thread we get the best performance available, caching resource using wrappers and using credentials in a somewhat efficient way.
Now the test snippet looks like this:
import java.io.*;
import java.security.PrivilegedAction;
import java.util.Properties;
import javax.jms.*;
import javax.naming.*;
import javax.security.auth.Subject;
import javax.security.auth.login.LoginException;
import javax.servlet.http.*;
import weblogic.jndi.Environment;
import weblogic.security.auth.Authenticate;
public class JMSWrapperCredentialsTest extends HttpServlet {
    QueueConnectionFactory factory = null;
    Queue queue = null;
    String jndiName = "java:comp/env/jms/QCF";
    String queueName= "jms/ColaEntradaConsultas";
    String user = "usuarioColas";
    String pwd = "12345678";
    String userjndi = "usuarioColas";
    String pwdjndi = "12345678";
    String serverT3URL="t3://127.0.0.1:7007";
    public void init() {
        setupJNDIResources();
    private void setupJNDIResources(){
        try {
            Properties props = new Properties();
            props.put("java.naming.factory.initial",
                    "weblogic.jndi.WLInitialContextFactory");
            props.put("java.naming.provider.url",serverT3URL );
            props.put("java.naming.security.principal", userjndi);// usr
            props.put("java.naming.security.credentials", pwdjndi);// pwd
            InitialContext ic = new InitialContext(props);
            factory = (QueueConnectionFactory) ic.lookup(jndiName);
            queue = (Queue) ic.lookup(queueName);
        } catch (NamingException e) {
            e.printStackTrace();
    public void service(HttpServletRequest req, HttpServletResponse res) {
        final HttpServletRequest fReq=req;
        final HttpServletResponse fRes=res;
        PrivilegedAction action = new java.security.PrivilegedAction() {
            public java.lang.Object run() {
                performRequest(fReq,fRes);
                return null;
        try {
            Subject subject=createSingleSubject(serverT3URL,user,pwd);
            weblogic.security.Security.runAs(subject, action);
        } catch (Exception e) {
            e.printStackTrace();
    public void performRequest(HttpServletRequest req, HttpServletResponse res) {
        res.setContentType("text/html");
        Writer wr = null;
        try {
            wr = res.getWriter();
            //Comment this out, do a lookup for each request and it will work
            //setupJNDIResources();
            String user = this.user;
            String pwd = this.pwd;
            //read users and passwords from the request in case they are present
            if (req.getParameter("user") != null) {
                user = req.getParameter("user");
            if (req.getParameter("pwd") != null) {
                pwd = req.getParameter("pwd");
            wr.write("JNDI User: *" + userjndi + "* y pwd: *" + pwdjndi + "*<p>");
            wr.write("Queue User: *" + user + "* y pwd: *" + pwd + "*<p>");
            //Obtain a connection using user/pwd
            QueueConnection conn = factory.createQueueConnection(user, pwd);
            QueueSession ses = conn.createQueueSession(true,
                    Session.SESSION_TRANSACTED);
            QueueSender sender = ses.createSender(queue);
            TextMessage msg = ses.createTextMessage();
            msg.setText("Hi there!");
            conn.start();
            sender.send(msg);
            ses.commit();
            sender.close();
            ses.close();
            conn.close();
        } catch (Exception e) {
            e.printStackTrace();
            try {
                wr.write(e.toString());
            } catch (Exception e2) {
                e2.printStackTrace();
        finally{
            try {
                wr.close();
            } catch (IOException e) {
                e.printStackTrace();
    private Subject createSingleSubject(String providerUrl, String userName, String password) {
        Subject subject = new Subject();
        // Weblogic env class
        Environment env = new Environment();
        if(providerUrl!=null)
            env.setProviderUrl(providerUrl);
        env.setSecurityPrincipal(userName);
        env.setSecurityCredentials(password);
        try {
          // Weblogic Authenticate class will populate and Seal the subject
          Authenticate.authenticate(env, subject);
          return subject;
        catch (LoginException e) {
          throw new RuntimeException("Unable to Authenticate User", e);
        catch (Exception e) {
          throw new RuntimeException("Error authenticating user", e);
}Thanks a lot for the help

Foreign JMS not enlisting XA Transactions

I'm working on implementing an XA interface layer to an implementation of a foreign JMS provider and am having a problem with enlisting XA transactions in WebLogic.
I implemented a simple JNDI that stores and retrieves serialized versions of classes in the local filesystem.
I create an XATopicConnectionFactory named ambxatcf and a Topic named ChatterTopic and store them in there.
The XATopicConnection implements XAConnection.
I put a client jar in bea/weblogic91/samples/domains/wl_server/lib/ which contains the JNDI code and all of my XA classes which call the JMS.
That gets picked up by the server on startup.
In the Web Logic Admin Console:
I create a Foreign Server under JMS Modules, ambrosiaServer.
I set the JNDI Initial Context Factory set to my JNDI InitialContext class and the JNDI Properties is the path to my JNDI filestore so that it can find the serialized objects.
I create a Foreign Destination in this server which has a Local JNDI Name: Chatter and Remote JNDI Name: ChatterTopic
And then also in this server, I create a Foreign Connection Factory, Local JNDI Name: ambxatcf and Remote JNDI Name: XATopicConnectionFactory.
Then in Deployments, I Install the jar containing my bean and Start it.
Then I run the client and the bean prints out the XATopicConnectionFactory and it's the one that came out my JNDI.
I have messages in my XATopicConnectionFactory, XATopicConnection and XATopicSession code so I know they're getting called.
What's not getting called is XATopicSession.getXAResource() or my XAResourceImpl.start() or XAResourceImpl.commit().
This happens whether I have the bean set up for bean managed or container managed transactions.
I'm testing against WebLogic 9.1.
Thanks,
Don Hermes

Hi Tom,
          Thank you for your response.
          I saw the article in the 8.1 documentation but I also found the following in the 9.1 docs.
          So, I assumed it would work.
          Was that assumption wrong?
          Thanks,
          Don
          =====================
          http://e-docs.bea.com/wls/docs91/jms/j2ee.html
          Automatically Enlisting Transactions
          This feature works for either WebLogic JMS implementations or for third-party JMS providers that support two-phase commit transactions (XA protocol). If a wrapped JMS connection sends or receives a message inside a transaction context, the JMS session being used to send or receive the message is automatically enlisted in the transaction through the XA capabilities of the JMS provider. This is the case whether the transaction was started implicitly because the JMS code was invoked inside an EJB with container-managed transactions enabled, or whether the transaction was started manually using the UserTransaction interface in a servlet or an EJB that supports bean-managed transactions.

Foreign JMS and Enlisting Transactions?

I'm working on implementing an XA interface layer to an implementation of a foreign JMS provider and am having a problem with enlisting XA transactions in WebLogic.
          I implemented a simple JNDI that stores and retrieves serialized versions of classes in the local filesystem.
          I create an XATopicConnectionFactory named ambxatcf and a Topic named ChatterTopic and store them in there.
          The XATopicConnection implements XAConnection.
          I put a client jar in bea/weblogic91/samples/domains/wl_server/lib/ which contains the JNDI code and all of my XA classes which call the JMS.
          That gets picked up by the server on startup.
          In the Web Logic Admin Console:
          I create a Foreign Server under JMS Modules, ambrosiaServer.
          I set the JNDI Initial Context Factory set to my JNDI InitialContext class and the JNDI Properties is the path to my JNDI filestore so that it can find the serialized objects.
          I create a Foreign Destination in this server which has a Local JNDI Name: Chatter and Remote JNDI Name: ChatterTopic
          And then also in this server, I create a Foreign Connection Factory, Local JNDI Name: ambxatcf and Remote JNDI Name: XATopicConnectionFactory.
          Then in Deployments, I Install the jar containing my bean and Start it.
          Then I run the client and the bean prints out the XATopicConnectionFactory and it's the one that came out my JNDI.
          I have messages in my XATopicConnectionFactory, XATopicConnection and XATopicSession code so I know they're getting called.
          What's not getting called is XATopicSession.getXAResource() or my XAResourceImpl.start() or XAResourceImpl.commit().
          This happens whether I have the bean set up for bean managed or container managed transactions.
          I'm testing against WebLogic 9.1.
          Thanks,
          Don Hermes

Hi Tom,
          Thank you for your response.
          I saw the article in the 8.1 documentation but I also found the following in the 9.1 docs.
          So, I assumed it would work.
          Was that assumption wrong?
          Thanks,
          Don
          =====================
          http://e-docs.bea.com/wls/docs91/jms/j2ee.html
          Automatically Enlisting Transactions
          This feature works for either WebLogic JMS implementations or for third-party JMS providers that support two-phase commit transactions (XA protocol). If a wrapped JMS connection sends or receives a message inside a transaction context, the JMS session being used to send or receive the message is automatically enlisted in the transaction through the XA capabilities of the JMS provider. This is the case whether the transaction was started implicitly because the JMS code was invoked inside an EJB with container-managed transactions enabled, or whether the transaction was started manually using the UserTransaction interface in a servlet or an EJB that supports bean-managed transactions.

What server comes with J2EE download?(URGENT)

I've been trying to install jive Forum but always faced problem with it and it seems like J2EE original server don't support it.
How can I used other servers like Tomcat with J2EE?
Please help URGENT!

Ok. I'm installing jive forums (www.jivesoftware.com).
By now, I've successfully run this forum on Tomcat server and HSQLDB provided by the forum itself. So I supposed that I've got the right settings. Before going on further, let me explain abit of the forum installation. First of all, the home directory for the forum must be set.After that, it's deploy. After deploying, user must access the setup which is jsp pages.
So I can access the setup page deploying the forum using Tomcat but not J2EE server. And the error I got is that the home directory has not been set when I run it with J2EE server but it's fine with Tomcat server.
In the command prompt, this is the errors I get:
java.security.AccessControlException: access denied (java.lang.RuntimePermission getClassLoader)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
at java.security.AccessController.checkPermission(AccessController.java:401)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
at java.lang.Thread.getContextClassLoader(Thread.java:1182)
at org.apache.jsp.index$jsp._jspService(index$jsp.java:187)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
ava:247)
at org.apache.catalina.core.ApplicationFilterChain.access$0(ApplicationFilterChain.java:197)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)
at com.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java
:40)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
ava:213)
at org.apache.catalina.core.ApplicationFilterChain.access$0(ApplicationFilterChain.java:197)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:368)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:534)
If your project assignment was to deploy this forum
app on J2EE RI server, then I suppose it can be
installed on it.I'm wonder what is RI server. Is it the same with Tomcat? I found the configurations file of Tomcat and J2EE server almost the same.
Obviously the forum software relies on a database. Is
the database running? Is the jdbc driver for the
database included in the forum application or have you
configured your server to find it?For your information, the forum supports Cloudscape database which comes with J2EE1.3.1. The setting up of the database is in the setup pages.
Do you have any indication what's wrong with the
setup? Are there errors and stacktraces in the console
output? Can you access the application on your own
machine at all?The errors is above. Yes I can access the application on my machine using Tomcat server but not J2EE server.
Please help. Thanks

Tomcat , JMS & J2ee RI

Similar Messages

Maybe you are looking for