Re: [JBoss-user] http session clustering
On Sunday 08 June 2003 06:21, Sacha Labourey wrote: Hello Stefano, Thanks, it works. great just a suggestion add this on your very good JBoss Clustering docs. And another thing: I read in jbossbook3.2.1 draft docs in chapter Using Clustering with Tomcat this phrase: If you are using a load balancer, make sure that your setup uses sticky session. I'm agree that's better to use it to reduce the overload on JBoss, but it is not necessary. Isn't it? It may be if you are using multiple-frames for example. Of course, you are right. BTW we are using since 2 year LVS (LinuxVirtualServer) as load balancer with JBoss, are you interested in my experience to integrate something about LVS in your docs exactly as you did for apache? Yes, sure, no need to write text! A few hints and configuratino should do it! Thanks Difficult to say it in few words. I'll take some time to write something in deep and I'll send you. Or to ML? or to dev ML? regards Cheers, Sacha --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user -- --- all work and no play makes Jack a dull boy --- bye Stefano [EMAIL PROTECTED] www.javalinux.it MSN messanger: [EMAIL PROTECTED] ICQ uin: 122192578 Jabber: canezen Yahoo MSN: canezen #jedit IRC channel as maeste --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JBoss XA transaction with WebSphere MQ
In MQSeries 5.2, you could only use the XAConnectionFactory if you configured the MQSeries JMS API to use 'bindings mode' instead of 'client mode'. The upshot of this is that the MQSeries Queue Manager and your Application Server needed to be on the same box, because bindings mode uses shared memory to communicate. Rgds, Dan. -- Danny Yates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 08 June 2003 08:07 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the reply. I am working on a complete readme to configure WebSphere MQ in JBoss. I will submit it as a patch once I am done, no problem. I am not sure to understand what you are referring to when talking about JNDI. If this is about bringing the WebSphere MQ queue/topic and connection factory object in the JBoss namespace, I actually wrote my own custom MBeans, wrapped them in a sar file and deploy it. The nice thing about it is that I have a jboss-service.xml in the sar which is similar to the jbossmq-destinations file and which allows me to declare as many WSMQ object as I need. The xa-connectionfalse/xa-connection is something that I have to do to have a WS MQ MDB working. I am not able to make the XA connection factory of WS MQ working. If I try to use it, the MDB never receives any messages, I am not sure to know why yet. Any suggestions at what I might need to look at? The MDB gets deployed without any errors; my client application is sending the message fine (I can see them in the WSMQ queue through the WSMQ admin tool), but the MDB never receives them. I think something wrong is happening because JBoss does not shutdown properly after that. It hangs in the stopping of the MDB, I think. I managed to create a new JMS resource adapter as you suggested. It seems to work fine. I need to check if I can send a message to a JBoss and a WSMQ queue using my two resource adapters but all in one transaction. I did experience some problems if I change the following value in my new JMS resource adapter: adapter-display-nameJMS Adapter/adapter-display-name If it is not set to JMS Adapter, then JBoss complains about the deployment being incomplete because of some dependencies with ConnectionManager and pool (or something like that. I can try to find the exact message if needed). Any ideas why? Thanks again for the help. Thomas -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2003 8:07 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Hi Thomas, Sounds like you have it nearly correct. If you can post the working configuration as a patch at www.sf.net/projects/jboss I will include them in docs/examples/jms, I don't have MQSeries so I can't test it. For JNDI you have three options. 1) Bind the external context into jboss's jndi 2 Use the following attribute in the provider config attribute name=ProviderUrlwhatever/ProviderUrl 3) Write your own provider adapter Re: xa-connectionfalse/xa-connection You will need to specify this when the connection factory you chose in the JMS provider is not an XAConnectionFactory. Re: JMS resource adapter You don't need to change ra.xml, these are just default values. If you want a new JMS resource adapter, you should make a new configuration (just like when you make a new data source). You can specify the provider adapter as a property on the connection manager. 3.2 style - 3.0 is too long winded :-) but the idea is the same. !-- JMS XA Resource adapter, use this to get transacted JMS in beans -- tx-connection-factory jndi-nameMQJmsXA/jndi-name xa-transaction/ adapter-display-nameMQ JMS Adapter/adapter-display-name config-property name=JmsProviderAdapterJNDI type=java.lang.Stringjava:MQJMSProvider/config-property config-property name=SessionDefaultType type=java.lang.Stringjavax.jms.Topic/config-property security-domain-and-applicationJmsXARealm/security-domain-and-applica tion /tx-connection-factory Regards, Adrian Adrian Brock Director of Support Back Office JBoss Group, LLC -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 06 June 2003 05:59 To: [EMAIL PROTECTED] Subject: [JBoss-user] JBoss XA transaction with WebSphere MQ I have been playing with JBoss 3.0.5 and WebSphere MQ 5.3 (ex-MQSeries) for a while now. I managed to create a new JMS provider in JBoss for WebSphere MQ: In jms-service.xml, duplicate the org.jboss.jms.jndi.JMSProviderLoader mbean. Change the ProviderName to WebSphereMQJMSProvider, change the QueueFactoryRef to WSMQConnectionFactory (I also changed the TopicFactoryRef to WSMQConnectionFactory, but I did not play with topics). I am passing the details on how to add the WSMQConnectionFactory to the JBoss JNDI space. I managed to create a new configuration
Re: [JBoss-user] problem with DuplicateClass and LocaleBUndle
hi All, Does any one have a solution for this problem I am bundling the LocaleBundle.properties files in two jar files NetServer.jar and WorkServer.jar and deploying it in the Jboss-tomcat-3.2.1.everything works fine except for if there are some duplicate classes in the two jar files but why does it look in to the other jar files ...like NetServer and WorkServer should be two different contexts and it does not bother if there are same classes in both these jar files.as it was doing in the earlier Jboss versions. The problem with LocaleBundle.properties is both are exisiting with the same name in the above said jar fiels and i am using ResourceBundle to locate them ...but it could not find these filesbut it was working fine with the Jboss-2.2.2 version and i dont know why it is not working with the new Jboss-Tomcat-3.2.1 version can any one help me regarding this i tried a lot but failed to solve this . Java version used is - jdk-1.3.1_04 regards jani Mauricio De Diana wrote: I had the same error when I had a deployed ear with another name but the same classes. Regards, Mauricio --- Janardhan Burugupalli [EMAIL PROTECTED] escreveu: HI guys, I get the java.lang.ClassCastException: $Proxy320 exception when i deploy the jar file while the jboss is running that is the hot deploy...and then if i again try to get the Home interface it gives the above exception on JBoss-tomcat-3.2.1 can any one explain this regards jani --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ Yahoo! Mail Mais espao, mais segurana e gratuito: caixa postal de 6MB, antivrus, proteo contra spam. http://br.mail.yahoo.com/ --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Call an EJB from an Oracle Java Stored Procedure
On Saturday 07 June 2003 01:20, Nicholas wrote:
Stefano;
The keys are the following:
1. Defer resolution until the second pass. (set
resolve=on)
Already done.
2. Recompile all classes when you are done. You can
generate a script to do this as follows:
select 'ALTER JAVA CLASS USER NAME.' || object_name
|| ' COMPILE;' from ALL_OBJECTS where object_type in
('JAVA CLASS', 'JAVA SOURCE') and OWNER = 'USER
NAME'
nothing changed. Class not compiled (resolved) in loading don't compile also
after loading.
Anyways, email me off line and I'll send you the Ant
tasks, examples and doc.
Yes please. In particular some example.
//Nicholas
Thanks a lot
--
--- all work and no play makes Jack a dull boy ---
bye Stefano
[EMAIL PROTECTED]
www.javalinux.it
MSN messanger: [EMAIL PROTECTED]
ICQ uin: 122192578
Jabber: canezen
Yahoo MSN: canezen
#jedit IRC channel as maeste
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] HOWTO: Call an EJB from an Oracle Java Stored Procedure
I went back to reproducs this, and the process was
this using
Windows XP Professional
JBoss jboss-3.2.0_tomcat-4.1.24
Oracle Enterprise Version 9.2.0.1.0
1. LoadJava the entire JBoss Client Jar collection
into SCOTT.
project name=OracleLoadJavaExample default=all
basedir=.
taskdef name=OracleLoadJava
classname=org.apache.tools.ant.taskdefs.optional.oraclejava.OracleLoadJava/
/target
target name=all
patternset id=all.jars
include name=**/*.jar/
/patternset
OracleLoadJava oci=on user=SCOTT/[EMAIL PROTECTED]
resolve=on debug=on force=no noverify=on
verbose=on noserverside=on schema=scott
synonym=on time=on
fileset dir=C:/jboss-3.2.0_tomcat-4.1.24/client
patternset refid=all.jars/
/fileset
/OracleLoadJava
/target
/project
2. Recompile all the invalid classes. To do this,
generate a script with this SQL logged in as SCOTT:
select 'ALTER JAVA CLASS SCOTT.' || object_name || '
COMPILE;' from USER_OBJECTS where object_type in
('JAVA CLASS', 'JAVA SOURCE') and status = 'INVALID'
Run the script that is generated.
3. Grant the following rights to SCOTT:
dbms_java.grant_permission( 'SCOTT',
'SYS:java.net.SocketPermission', 'IP ADDRESS:1024-',
'listen,resolve' );
dbms_java.grant_permission( 'SCOTT',
'SYS:java.net.SocketPermission', 'IP ADDRESS:3495',
'connect,accept,resolve' );
dbms_java.grant_permission(
'SCOTT','SYS:java.lang.RuntimePermission','org.jboss.security.SecurityAssociation.getPrincipalInfo',
'' );
dbms_java.grant_permission(
'SCOTT','SYS:java.io.SerializablePermission',
'enableSubstitution', '' );
dbms_java.grant_permission( 'SCOTT',
'SYS:java.net.SocketPermission','IP ADDRESS:8093',
'connect,resolve' );
There may be some extra ones in there. I was also
trying to communicate with some JMS processes, but
generally, Oracle will tell you exactly which
permissions you need in the error message if you fail
to have one.
3. Load EJB. Again, I used the Ant task and loaded the
JAR I deployed to JBoss and a simple test client of a
simple EJB:
EJB:
import javax.ejb.*;
public class StringLibBean implements SessionBean {
SessionContext sessionContext;
public void ejbCreate() throws CreateException {
}
public void ejbRemove() {
}
public void ejbActivate() {
}
public void ejbPassivate() {
}
public void setSessionContext(SessionContext
sessionContext) {
this.sessionContext = sessionContext;
}
public String reverse(java.lang.String a) {
return new StringBuffer(a).reverse().toString();
}
}
Client Code:
public static String reverse(String ejbName, String
message) {
System.out.println(reverse( + ejbName + , +
message + ););
try {
if(ctx==null) {
ctx = getJBossContext();
System.out.println(Aha! Connnected To : +
ctx.getEnvironment().get(ctx.PROVIDER_URL));
}
if(home == null) {
System.out.println(Looking Up: + ejbName);
Object obj = ctx.lookup(ejbName);
System.out.println(Found Object Ref: + obj);
home = (StringLibHome)obj;
System.out.println(Cast to Home);
}
remote = home.create();
String tmp = remote.reverse(message);
System.out.println(StringLib.reverse Result: +
tmp);
return tmp;
}
catch (Exception ex) {
System.err.println(Exception: + ex);
ex.printStackTrace();
return null;
}
}
public static Context getJBossContext() throws
Exception {
Properties p = new Properties();
p.put(Context.PROVIDER_URL, localhost:1099);
p.put(Context.INITIAL_CONTEXT_FACTORY,org.jnp.interfaces.NamingContextFactory);
return new InitialContext(p);
}
4. Recompiled invalid Java Classes again.
5. Created test SQL Script (testreverse.sql):
connect scott/[EMAIL PROTECTED]
SET SERVEROUTPUT ON
DECLARE
AA VARCHAR2(30) := 'NULL';
BEGIN
dbms_java.set_output(1);
AA := REVERSE('StringLib', 'Calling JBoss From
PLSQL');
dbms_output.put_line('Reversed ='|| AA);
END;
/
exit
/
6. Created test command file (reverse.cmd):
@echo off
cls
sqlplus /NOLOG @testreverse.sql
7. Ran the command file:
C:\testreverse
SQL*Plus: Release 9.2.0.1.0 - Production on Mon Jun 9
06:07:03 2003
Copyright (c) 1982, 2002, Oracle Corporation. All
rights reserved.
Connected.
reverse(StringLib,Calling JBoss From PLSQL);
Aha! Connnected To :localhost:1099
Looking Up:StringLib
Found Object Ref:StringLibHome
Cast to Home
StringLib.reverse Result:LQSLP morF ssoBJ gnillaC
Reversed =LQSLP morF ssoBJ gnillaC
PL/SQL procedure successfully completed.
Disconnected from Oracle9i Enterprise Edition Release
9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining
options
JServer Release 9.2.0.1.0 - Production
I found Oracle to be a little unstable when testing
this, but once it is loaded and all the
Re: [JBoss-user] problem with DuplicateClass and LocaleBUndle
Jani, Since (I think) about JBoss 3.0.5 there has been a new class loader mechanism. The benefits are that by default all JARs share the same class loader. For much more than I can explain or understand, check the documentation: http://prdownloads.sourceforge.net/jboss/ClassLoading.pdf?download This also explains how to fix your problem. Ciao, Jonathan O'Connor Development Manager XCOM Dublin Phone: +353 1 872 3305 Mobile: +353 86 824 0736 [EMAIL PROTECTED] (Janardhan Burugupalli) Sent by: [EMAIL PROTECTED] 09.06.2003 10:32 Please respond to jboss-user To: [EMAIL PROTECTED] cc: Subject:Re: [JBoss-user] problem with DuplicateClass and LocaleBUndle hi All, Does any one have a solution for this problem I am bundling the LocaleBundle.properties files in two jar files NetServer.jar and WorkServer.jar and deploying it in the Jboss-tomcat-3.2.1.everything works fine except for if there are some duplicate classes in the two jar files but why does it look in to the other jar files ...like NetServer and WorkServer should be two different contexts and it does not bother if there are same classes in both these jar files.as it was doing in the earlier Jboss versions. The problem with LocaleBundle.properties is both are exisiting with the same name in the above said jar fiels and i am using ResourceBundle to locate them ...but it could not find these filesbut it was working fine with the Jboss-2.2.2 version and i dont know why it is not working with the new Jboss-Tomcat-3.2.1 version can any one help me regarding this i tried a lot but failed to solve this . Java version used is - jdk-1.3.1_04 regards jani Mauricio De Diana wrote: I had the same error when I had a deployed ear with another name but the same classes. Regards, Mauricio --- Janardhan Burugupalli [EMAIL PROTECTED] escreveu: HI guys, I get the java.lang.ClassCastException: $Proxy320 exception when i deploy the jar file while the jboss is running that is the hot deploy...and then if i again try to get the Home interface it gives the above exception on JBoss-tomcat-3.2.1 can any one explain this regards jani --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ Yahoo! Mail Mais espaço, mais segurança e gratuito: caixa postal de 6MB, antivírus, proteção contra spam. http://br.mail.yahoo.com/ --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] MBean deployment ignores depends tag
Did anyone have a chance to look at the log files I sent on thursday last week? The deployment order seems to be ignoring the dependencies. Alex. --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JBoss XA transaction with WebSphere MQ
Title: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the information. I went through this pain already until I discovered that with MQ 5.3, service pack 3 (CSD03) and what IBM is calling the Extended Transaction Client, you are now supposed to be able to make XA work with the 'client mode' of the MQ JMS API (and this is what I am currently trying). Did you manage to make XA work with MQ 5.2 binding mode and JBoss? I tried that as well with MQ 5.3 and I get the same problem as I currently have, the MDB is not receiving any messages. If you have a configuration which is working, I am interested, if possible, to get some details. Thanks Thomas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, June 09, 2003 3:47 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ In MQSeries 5.2, you could only use the XAConnectionFactory if you configured the MQSeries JMS API to use 'bindings mode' instead of 'client mode'. The upshot of this is that the MQSeries Queue Manager and your Application Server needed to be on the same box, because bindings mode uses shared memory to communicate. Rgds, Dan. -- Danny Yates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 08 June 2003 08:07 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the reply. I am working on a complete readme to configure WebSphere MQ in JBoss. I will submit it as a patch once I am done, no problem. I am not sure to understand what you are referring to when talking about JNDI. If this is about bringing the WebSphere MQ queue/topic and connection factory object in the JBoss namespace, I actually wrote my own custom MBeans, wrapped them in a sar file and deploy it. The nice thing about it is that I have a jboss-service.xml in the sar which is similar to the jbossmq-destinations file and which allows me to declare as many WSMQ object as I need. The xa-connectionfalse/xa-connection is something that I have to do to have a WS MQ MDB working. I am not able to make the XA connection factory of WS MQ working. If I try to use it, the MDB never receives any messages, I am not sure to know why yet. Any suggestions at what I might need to look at? The MDB gets deployed without any errors; my client application is sending the message fine (I can see them in the WSMQ queue through the WSMQ admin tool), but the MDB never receives them. I think something wrong is happening because JBoss does not shutdown properly after that. It hangs in the stopping of the MDB, I think. I managed to create a new JMS resource adapter as you suggested. It seems to work fine. I need to check if I can send a message to a JBoss and a WSMQ queue using my two resource adapters but all in one transaction. I did experience some problems if I change the following value in my new JMS resource adapter: adapter-display-nameJMS Adapter/adapter-display-name If it is not set to JMS Adapter, then JBoss complains about the deployment being incomplete because of some dependencies with ConnectionManager and pool (or something like that. I can try to find the exact message if needed). Any ideas why? Thanks again for the help. Thomas -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Friday, June 06, 2003 8:07 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Hi Thomas, Sounds like you have it nearly correct. If you can post the working configuration as a patch at www.sf.net/projects/jboss I will include them in docs/examples/jms, I don't have MQSeries so I can't test it. For JNDI you have three options. 1) Bind the external context into jboss's jndi 2 Use the following attribute in the provider config attribute name=ProviderUrlwhatever/ProviderUrl 3) Write your own provider adapter Re: xa-connectionfalse/xa-connection You will need to specify this when the connection factory you chose in the JMS provider is not an XAConnectionFactory. Re: JMS resource adapter You don't need to change ra.xml, these are just default values. If you want a new JMS resource adapter, you should make a new configuration (just like when you make a new data source). You can specify the provider adapter as a property on the connection manager. 3.2 style - 3.0 is too long winded :-) but the idea is the same. !-- JMS XA Resource adapter, use this to get transacted JMS in beans -- tx-connection-factory jndi-nameMQJmsXA/jndi-name xa-transaction/ adapter-display-nameMQ JMS Adapter/adapter-display-name config-property name=JmsProviderAdapterJNDI type=java.lang.Stringjava:MQJMSProvider/config-property config-property name=SessionDefaultType type=java.lang.Stringjavax.jms.Topic/config-property security-domain-and-applicationJmsXARealm/security-domain-and-applica tion /tx-connection-factory Regards, Adrian
RE: [JBoss-user] JBoss XA transaction with WebSphere MQ
Title: Message I'm afraid I never tried MQ with JBoss at all (XA or otherwise). We were using WebLogic and doing JTS transactions in client mode against a remote MQ server. -- Danny Yates -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 June 2003 13:11To: [EMAIL PROTECTED]Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the information. I went through this pain already until I discovered that with MQ 5.3, service pack 3 (CSD03) and what IBM is calling the Extended Transaction Client, you are now supposed to be able to make XA work with the 'client mode' of the MQ JMS API (and this is what I am currently trying). Did you manage to make XA work with MQ 5.2 binding mode and JBoss? I tried that as well with MQ 5.3 and I get the same problem as I currently have, the MDB is not receiving any messages. If you have a configuration which is working, I am interested, if possible, to get some details. Thanks Thomas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, June 09, 2003 3:47 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ In MQSeries 5.2, you could only use the XAConnectionFactory if you configured the MQSeries JMS API to use 'bindings mode' instead of 'client mode'. The upshot of this is that the MQSeries Queue Manager and your Application Server needed to be on the same box, because bindings mode uses shared memory to communicate. Rgds, Dan. -- Danny Yates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 08 June 2003 08:07 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the reply. I am working on a complete readme to configure WebSphere MQ in JBoss. I will submit it as a patch once I am done, no problem. I am not sure to understand what you are referring to when talking about JNDI. If this is about bringing the WebSphere MQ queue/topic and connection factory object in the JBoss namespace, I actually wrote my own custom MBeans, wrapped them in a sar file and deploy it. The nice thing about it is that I have a jboss-service.xml in the sar which is similar to the jbossmq-destinations file and which allows me to declare as many WSMQ object as I need. The xa-connectionfalse/xa-connection is something that I have to do to have a WS MQ MDB working. I am not able to make the XA connection factory of WS MQ working. If I try to use it, the MDB never receives any messages, I am not sure to know why yet. Any suggestions at what I might need to look at? The MDB gets deployed without any errors; my client application is sending the message fine (I can see them in the WSMQ queue through the WSMQ admin tool), but the MDB never receives them. I think something wrong is happening because JBoss does not shutdown properly after that. It hangs in the stopping of the MDB, I think. I managed to create a new JMS resource adapter as you suggested. It seems to work fine. I need to check if I can send a message to a JBoss and a WSMQ queue using my two resource adapters but all in one transaction. I did experience some problems if I change the following value in my new JMS resource adapter: adapter-display-nameJMS Adapter/adapter-display-name If it is not set to "JMS Adapter", then JBoss complains about the deployment being incomplete because of some dependencies with ConnectionManager and pool (or something like that. I can try to find the exact message if needed). Any ideas why? Thanks again for the help. Thomas -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Friday, June 06, 2003 8:07 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Hi Thomas, Sounds like you have it nearly correct. If you can post the working configuration as a patch at www.sf.net/projects/jboss I will include them in docs/examples/jms, I don't have MQSeries so I can't test it. For JNDI you have three options. 1) Bind the external context into jboss's jndi 2 Use the following attribute in the provider config attribute name="ProviderUrl"whatever/ProviderUrl 3) Write your own provider adapter Re: xa-connectionfalse/xa-connection You will need to specify this when the connection factory you chose in the JMS provider is not an XAConnectionFactory. Re: JMS resource adapter You don't need to change ra.xml, these are just default values. If you want a new JMS resource adapter, you should make a new configuration (just like when you make a new data source). You can specify the provider adapter as a property on the connection manager. 3.2 style - 3.0 is too long winded :-) but the idea
RE: [JBoss-user] Some J2EE Design Questions
Title: RE: [JBoss-user] Some J2EE Design Questions Sorry, connectionless was admittedly a poor choice of words. Typically, that applies to UDP protocols (SNMP, TFTP, and the like). In most applications of RMI, a client-server RMI connection is not a long-lasting one. By long-lasting, I mean a connection that survives across multiple method invocations. The client opens the connection, makes a call, gets the result, and closes the connection. Unlike a typical database connection, where the connection lives across requests. Therefore, there is really no simple way to trap 'disconnects' from the server. mike -Original Message- From: Richard Stack [mailto:[EMAIL PROTECTED]] Sent: Friday, June 06, 2003 1:31 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Some J2EE Design Questions Hello Mike, Could you explain what you mean when you say RMI is a connectionless protocol (not a persistent connection) Richard Finn, Michael wrote: 1. If EJB Timer (2.1) does not fit the bill for you, an MBean is a typically a good solution for this problem. Depends on what you mean by service. 2. Since RMI is a connectionless protocol (not a persistent connection), there is really no 'disconnect' event. Your best bet is probably to use shutdown hooks in your client, and make last ditch effort to do the logout there. mike -Original Message- From: Sasidharan, Manoj [mailto:[EMAIL PROTECTED]] Sent: Friday, June 06, 2003 3:33 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] Some J2EE Design Questions Hello All, 1. How can a daemon process/service implemented in J2EE world? Any design pattern? 2. Is there any way to trap J2EE client disconnect events - we want to timeout user sessions if they fail to logout properly from our J2EE app and disconnect from App Server Thanks in advance for your time in helping me with these design issues. MS --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] MBean deployment ignores depends tag
On Mon, 2003-06-09 at 14:25, Nicholas wrote: Can you send them again ? I could not find them in the archive. Hmmm, looks like the sourceforge archive strips off attachments. Here is the body of my reply to Scott and the attachment again: I've attached a gzip'd jboss log from a jboss 3.2.1 startup showing that the jboss-anvilmarket2-service.xml file is deployed before any of the EJBs in the ejb-anvil-market.jar are deployed, resulting in class not found error. I think the depends tags in jboss-anvilmarket2-service.xml should make the mbean deployment wait until after the named EJB has deployed, however this is not happening. The very same ejb jar and -service.xml work fine if I force the deployment order by copying them into the deploy directory manually one by one. Cheers, Alex. jboss.log.gz Description: GNU Zip compressed data ?xml version=1.0 encoding=UTF-8? server classpath codebase=lib archives=quickfix.jar/ mbean code=com.anvil.ate.market.common.ApplicationConstants name=com.anvil.ate.market:service=ApplicationConstants dependsjboss:service=Naming/depends dependsjboss.j2ee:jndiName=market/MarketData,service=EJB/depends attribute name=ServerNamelocalhost/attribute attribute name=InOrderQinboundOrderQueue/attribute attribute name=InQuoteQinboundQuoteQueue/attribute attribute name=InSessionQinboundSessionQueue/attribute attribute name=OutQoutboundQueue/attribute /mbean /server
RE: [JBoss-user] JBoss XA transaction with WebSphere MQ
Title: Message WebLogic is one of my options as well. Does it mean that you managed to have a MQ JMS provider working within WebLogic (including having Message Driven Bean deployed listening to MQ queues/topics) with XA/JTS support? If yes, I am interested to know which version of WebLogic you are using and any kind of information you can share on setting this up in WebLogic (I do not have too much experience with WebLogic, but I was going to try that, at some point). Thomas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 8:36 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ I'm afraid I never tried MQ with JBoss at all (XA or otherwise). We were using WebLogic and doing JTS transactions in client mode against a remote MQ server. -- Danny Yates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 June 2003 13:11 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the information. I went through this pain already until I discovered that with MQ 5.3, service pack 3 (CSD03) and what IBM is calling the Extended Transaction Client, you are now supposed to be able to make XA work with the 'client mode' of the MQ JMS API (and this is what I am currently trying). Did you manage to make XA work with MQ 5.2 binding mode and JBoss? I tried that as well with MQ 5.3 and I get the same problem as I currently have, the MDB is not receiving any messages. If you have a configuration which is working, I am interested, if possible, to get some details. Thanks Thomas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, June 09, 2003 3:47 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ In MQSeries 5.2, you could only use the XAConnectionFactory if you configured the MQSeries JMS API to use 'bindings mode' instead of 'client mode'. The upshot of this is that the MQSeries Queue Manager and your Application Server needed to be on the same box, because bindings mode uses shared memory to communicate. Rgds, Dan. -- Danny Yates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 08 June 2003 08:07 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the reply. I am working on a complete readme to configure WebSphere MQ in JBoss. I will submit it as a patch once I am done, no problem. I am not sure to understand what you are referring to when talking about JNDI. If this is about bringing the WebSphere MQ queue/topic and connection factory object in the JBoss namespace, I actually wrote my own custom MBeans, wrapped them in a sar file and deploy it. The nice thing about it is that I have a jboss-service.xml in the sar which is similar to the jbossmq-destinations file and which allows me to declare as many WSMQ object as I need. The xa-connectionfalse/xa-connection is something that I have to do to have a WS MQ MDB working. I am not able to make the XA connection factory of WS MQ working. If I try to use it, the MDB never receives any messages, I am not sure to know why yet. Any suggestions at what I might need to look at? The MDB gets deployed without any errors; my client application is sending the message fine (I can see them in the WSMQ queue through the WSMQ admin tool), but the MDB never receives them. I think something wrong is happening because JBoss does not shutdown properly after that. It hangs in the stopping of the MDB, I think. I managed to create a new JMS resource adapter as you suggested. It seems to work fine. I need to check if I can send a message to a JBoss and a WSMQ queue using my two resource adapters but all in one transaction. I did experience some problems if I change the following value in my new JMS resource adapter: adapter-display-nameJMS Adapter/adapter-display-name If it is not set to JMS Adapter, then JBoss complains about the deployment being incomplete because of some dependencies with ConnectionManager and pool (or something like that. I can try to find the exact message if needed). Any ideas why? Thanks again for the help. Thomas -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Friday, June 06, 2003 8:07 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Hi Thomas, Sounds like you have it nearly correct. If you can post the working configuration as a patch at www.sf.net/projects/jboss I will include them in docs/examples/jms, I don't have MQSeries so I can't test it. For JNDI you have three options. 1) Bind the external context into jboss's jndi 2 Use the following attribute in the provider config attribute name=ProviderUrlwhatever/ProviderUrl 3) Write your own
RE: [JBoss-user] JBoss XA transaction with WebSphere MQ
Title: Message A while back I had it working in WebLogic 6 with JTS transaction (NOT XA transactions). At least I think it was JTS transactions. Essential you set the transactional flag to true when creating a session, and have to do session.commit for your writes to appear. This works in WLS 6.1 sp 4 onwards using their MessagingBridge (they will tell you they back-ported the MessagingBridge to sp2 or sp3. They only did half a job - it only works from sp4), or WLS7. In WLS7, I think MDBs have properties which allow you to connect them to any JNDI tree using a URL and Context Factory. In this case, you use the Sun FileSystem JNDI implementation and IBM's jmsadmin (???) tool to manage the FileSystem JNDI. There are plenty of papers on the web about doing this. Good luck! Dan. -- Danny Yates -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 June 2003 14:52To: [EMAIL PROTECTED]Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ WebLogic is one of my options as well. Does it mean that you managed to have a MQ JMS provider working within WebLogic (including having Message Driven Bean deployed listening to MQ queues/topics) with XA/JTS support? If yes, I am interested to know which version of WebLogic you are using and any kind of information you can share on setting this up in WebLogic (I do not have too much experience with WebLogic, but I was going to try that, at some point). Thomas -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 8:36 AMTo: [EMAIL PROTECTED]Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ I'm afraid I never tried MQ with JBoss at all (XA or otherwise). We were using WebLogic and doing JTS transactions in client mode against a remote MQ server. -- Danny Yates -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 June 2003 13:11To: [EMAIL PROTECTED]Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the information. I went through this pain already until I discovered that with MQ 5.3, service pack 3 (CSD03) and what IBM is calling the Extended Transaction Client, you are now supposed to be able to make XA work with the 'client mode' of the MQ JMS API (and this is what I am currently trying). Did you manage to make XA work with MQ 5.2 binding mode and JBoss? I tried that as well with MQ 5.3 and I get the same problem as I currently have, the MDB is not receiving any messages. If you have a configuration which is working, I am interested, if possible, to get some details. Thanks Thomas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, June 09, 2003 3:47 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ In MQSeries 5.2, you could only use the XAConnectionFactory if you configured the MQSeries JMS API to use 'bindings mode' instead of 'client mode'. The upshot of this is that the MQSeries Queue Manager and your Application Server needed to be on the same box, because bindings mode uses shared memory to communicate. Rgds, Dan. -- Danny Yates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 08 June 2003 08:07 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the reply. I am working on a complete readme to configure WebSphere MQ in JBoss. I will submit it as a patch once I am done, no problem. I am not sure to understand what you are referring to when talking about JNDI. If this is about bringing the WebSphere MQ queue/topic and connection factory object in the JBoss namespace, I actually wrote my own custom MBeans, wrapped them in a sar file and deploy it. The nice thing about it is that I have a jboss-service.xml in the sar which is similar to the jbossmq-destinations file and which allows me to declare as many WSMQ object as I need. The xa-connectionfalse/xa-connection is something that I have to do to have a WS MQ MDB working. I am not able to make the XA connection factory of WS MQ working. If I try to use it, the MDB never receives any messages, I am not sure to know why yet. Any suggestions at what I might need to look at? The MDB gets deployed without any errors; my client application is sending the message fine (I can see them in the WSMQ queue through the WSMQ admin tool), but the MDB never receives them. I think something wrong is happening because JBoss does not shutdown properly after that. It hangs in the stopping of the MDB, I
AW: AW: [JBoss-user] Confused about Web Service Security...
Hi,
I am trying to get basic auth to work. I am at the point where got my
Java cleint passing the Authorization: Basic details and JBoss throwing back
an error:
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultString: javax.ejb.EJBException: checkSecurityAssociation;
CausedByException is:
Authentication exception, principal=null faultActor: null
faultDetail:
stackTrace: javax.ejb.EJBException: checkSecurityAssociation;
CausedByException is:
Authentication exception, principal=null
I have my deployment descriptor generated by XDoclet and use a custom jaas
module which I am trying to use both for Web Services and EJB.
I changed the jboss-net.sar\jboss-net.war\WEB-INF\jboss-web.xml and the
jboss-net.sar\axis-config.xml to use my module. (What is the role of each
one?)
The deployment file is:
?xml version=1.0 encoding=UTF-8?
!-- --
!-- This JBoss.Net Web Service Descriptor has been generated by
Doclet --
!-- and brought to you by F. M. Brier, C. G. Jung and J.
ton --
!-- --
deployment
name=Test
xmlns=http://xml.apache.org/axis/wsdd/;
targetNamespace=http://net.jboss.org/Test;
xmlns:test=http://net.jboss.org/Test;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
!-- The following are declarations of service endpoints targetted to
session beans --
service name=Test provider=Handler
parameter name=handlerClass
value=org.jboss.net.axis.server.EJBProvider/
parameter name=beanJndiName
value=EJB/Session/TestEJB/Session/Local/Test/
parameter name=allowedMethods value=hello /
requestFlow name=TestRequest
handler
type=java:org.jboss.net.axis.server.TransactionRequestHandler/
/requestFlow
responseFlow name=TestResponse
handler
type=java:org.jboss.net.axis.server.SerialisationResponseHandler/
handler
type=java:org.jboss.net.axis.server.TransactionResponseHandler/
/responseFlow
/service
!-- The following are typemappings for entity beans for implementing
the implicit web-service value-object pattern --
!-- The following are typemappings for bean-type value-objects --
/deployment
Thank you!!!
Simone
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JBoss XA transaction with WebSphere MQ
Title: Message Thanks for the extra information. I appreciate. Thomas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 10:19 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ A while back I had it working in WebLogic 6 with JTS transaction (NOT XA transactions). At least I think it was JTS transactions. Essential you set the transactional flag to true when creating a session, and have to do session.commit for your writes to appear. This works in WLS 6.1 sp 4 onwards using their MessagingBridge (they will tell you they back-ported the MessagingBridge to sp2 or sp3. They only did half a job - it only works from sp4), or WLS7. In WLS7, I think MDBs have properties which allow you to connect them to any JNDI tree using a URL and Context Factory. In this case, you use the Sun FileSystem JNDI implementation and IBM's jmsadmin (???) tool to manage the FileSystem JNDI. There are plenty of papers on the web about doing this. Good luck! Dan. -- Danny Yates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 June 2003 14:52 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ WebLogic is one of my options as well. Does it mean that you managed to have a MQ JMS provider working within WebLogic (including having Message Driven Bean deployed listening to MQ queues/topics) with XA/JTS support? If yes, I am interested to know which version of WebLogic you are using and any kind of information you can share on setting this up in WebLogic (I do not have too much experience with WebLogic, but I was going to try that, at some point). Thomas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 8:36 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ I'm afraid I never tried MQ with JBoss at all (XA or otherwise). We were using WebLogic and doing JTS transactions in client mode against a remote MQ server. -- Danny Yates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 June 2003 13:11 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the information. I went through this pain already until I discovered that with MQ 5.3, service pack 3 (CSD03) and what IBM is calling the Extended Transaction Client, you are now supposed to be able to make XA work with the 'client mode' of the MQ JMS API (and this is what I am currently trying). Did you manage to make XA work with MQ 5.2 binding mode and JBoss? I tried that as well with MQ 5.3 and I get the same problem as I currently have, the MDB is not receiving any messages. If you have a configuration which is working, I am interested, if possible, to get some details. Thanks Thomas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, June 09, 2003 3:47 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ In MQSeries 5.2, you could only use the XAConnectionFactory if you configured the MQSeries JMS API to use 'bindings mode' instead of 'client mode'. The upshot of this is that the MQSeries Queue Manager and your Application Server needed to be on the same box, because bindings mode uses shared memory to communicate. Rgds, Dan. -- Danny Yates -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 08 June 2003 08:07 To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the reply. I am working on a complete readme to configure WebSphere MQ in JBoss. I will submit it as a patch once I am done, no problem. I am not sure to understand what you are referring to when talking about JNDI. If this is about bringing the WebSphere MQ queue/topic and connection factory object in the JBoss namespace, I actually wrote my own custom MBeans, wrapped them in a sar file and deploy it. The nice thing about it is that I have a jboss-service.xml in the sar which is similar to the jbossmq-destinations file and which allows me to declare as many WSMQ object as I need. The xa-connectionfalse/xa-connection is something that I have to do to have a WS MQ MDB working. I am not able to make the XA connection factory of WS MQ working. If I try to use it, the MDB never receives any messages, I am not sure to know why yet. Any suggestions at what I might need to look at? The MDB gets deployed without any errors; my client application is sending the message fine (I can see them in the WSMQ queue through the WSMQ admin tool), but the MDB never receives them. I think something wrong is happening because JBoss does not shutdown properly after that. It hangs in the stopping of the MDB, I think. I
RE: [JBoss-user] JBoss XA transaction with WebSphere MQ
Title: Message A while back I had it working in WebLogic 6 with JTS transaction (NOT XA transactions). At least I think it was JTS transactions. Essential you set the transactional flag to true when creating a session, and have to do session.commit for your writes to appear. This works in WLS 6.1 sp 4 onwards using their MessagingBridge (they will tell you they back-ported the MessagingBridge to sp2 or sp3. They only did half a job - it only works from sp4), or WLS7. In WLS7, I think MDBs have properties which allow you to connect them to any JNDI tree using a URL and Context Factory. In this case, you use the Sun FileSystem JNDI implementation and IBM's jmsadmin (???) tool to manage the FileSystem JNDI. There are plenty of papers on the web about doing this. Good luck! Dan. -- Danny Yates -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 June 2003 14:52To: [EMAIL PROTECTED]Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ WebLogic is one of my options as well. Does it mean that you managed to have a MQ JMS provider working within WebLogic (including having Message Driven Bean deployed listening to MQ queues/topics) with XA/JTS support? If yes, I am interested to know which version of WebLogic you are using and any kind of information you can share on setting this up in WebLogic (I do not have too much experience with WebLogic, but I was going to try that, at some point). Thomas -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 8:36 AMTo: [EMAIL PROTECTED]Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ I'm afraid I never tried MQ with JBoss at all (XA or otherwise). We were using WebLogic and doing JTS transactions in client mode against a remote MQ server. -- Danny Yates -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 June 2003 13:11To: [EMAIL PROTECTED]Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ Thanks for the information. I went through this pain already until I discovered that with MQ 5.3, service pack 3 (CSD03) and what IBM is calling the Extended Transaction Client, you are now supposed to be able to make XA work with the 'client mode' of the MQ JMS API (and this is what I am currently trying). Did you manage to make XA work with MQ 5.2 binding mode and JBoss? I tried that as well with MQ 5.3 and I get the same problem as I currently have, the MDB is not receiving any messages. If you have a configuration which is working, I am interested, if possible, to get some details. Thanks Thomas _ Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch, Banc of America Securities Limited and Banc of America Futures Incorporated are regulated by the Financial Services Authority. _
[JBoss-user] Classloaders and the jboss-app.xml
Title: Message Hi everyone, I've just encountered the dreaded ClassCastException error that's thrown due to the fact that the type of the java class is now a function of the class loader as well as the name. I read the Classloader excerpt from the 3.x documentation thatJonathan recommended. (Thanks again for that Jonathan). My problem is as follows for those who have a minute. I'm developing a small workflow engine comprised of a number of beans deployed in JBoss3.2.1. A number of remote components that perform the work externally of the engine may or may not be deployedwitihin the same instance of the server. However they must be able to communicate events back to my with my engine so I put all the interfaces for the engine into a jar called client-interfaces.jar and bundled it within an remote components ear file that that would need to talk to my interact with the workflow.. Inevitably I got ahugeClassCastException when attempting to run the overall process due to so many versions of the same interface classes being deployed. I've thought about it and I can see two possible solutions. 1 Take all the interfaces out from everywhere including the workflow engine itself and deploy them in a separate interfaces-jar file. If I do I should have only one version of the class deployed although the engine would be fragmented. Also if I do this by deploying say interfaces.jar will this make the classes available to the remote components that are deployed along side it? If not then how do I specify that this jar file is part of the classpath? 2. The second involves the use of hte jboss-app.xml file described in the Classloader excerpt. Unfortunately I have no experience writing classloaders whatsoever. And can't get my head around where the jboss-app file should be included and whether or not I have to actually write a class loader for each remote component. Any explanation of the jboss-app.xml file or indeed any help in answering any of the above questions would be greatly appreciated. Thanks again, Mark.
AW: AW: [JBoss-user] Confused about Web Service Security...
Hi,
I managed to do it, thank you anyway :)
Simone
Hi,
I am trying to get basic auth to work. I am at the point where got my
Java cleint passing the Authorization: Basic details and JBoss throwing
back
an error:
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultString: javax.ejb.EJBException: checkSecurityAssociation;
CausedByException is:
Authentication exception, principal=null faultActor: null
faultDetail:
stackTrace: javax.ejb.EJBException: checkSecurityAssociation;
CausedByException is:
Authentication exception, principal=null
I have my deployment descriptor generated by XDoclet and use a custom jaas
module which I am trying to use both for Web Services and EJB.
I changed the jboss-net.sar\jboss-net.war\WEB-INF\jboss-web.xml and the
jboss-net.sar\axis-config.xml to use my module. (What is the role of each
one?)
The deployment file is:
?xml version=1.0 encoding=UTF-8?
!-- --
!-- This JBoss.Net Web Service Descriptor has been generated by
Doclet --
!-- and brought to you by F. M. Brier, C. G. Jung and J.
ton --
!-- --
deployment
name=Test
xmlns=http://xml.apache.org/axis/wsdd/;
targetNamespace=http://net.jboss.org/Test;
xmlns:test=http://net.jboss.org/Test;
xmlns:java=http://xml.apache.org/axis/wsdd/providers/java;
!-- The following are declarations of service endpoints targetted to
session beans --
service name=Test provider=Handler
parameter name=handlerClass
value=org.jboss.net.axis.server.EJBProvider/
parameter name=beanJndiName
value=EJB/Session/TestEJB/Session/Local/Test/
parameter name=allowedMethods value=hello /
requestFlow name=TestRequest
handler
type=java:org.jboss.net.axis.server.TransactionRequestHandler/
/requestFlow
responseFlow name=TestResponse
handler
type=java:org.jboss.net.axis.server.SerialisationResponseHandler/
handler
type=java:org.jboss.net.axis.server.TransactionResponseHandler/
/responseFlow
/service
!-- The following are typemappings for entity beans for implementing
the implicit web-service value-object pattern --
!-- The following are typemappings for bean-type value-objects --
/deployment
Thank you!!!
Simone
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JBoss XA transaction with WebSphere MQ
Title: Message Thanks for the extra information. I appreciate. Thomas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 10:19 AM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss XA transaction with WebSphere MQ A while back I had it working in WebLogic 6 with JTS transaction (NOT XA transactions). At least I think it was JTS transactions. Essential you set the transactional flag to true when creating a session, and have to do session.commit for your writes to appear. This works in WLS 6.1 sp 4 onwards using their MessagingBridge (they will tell you they back-ported the MessagingBridge to sp2 or sp3. They only did half a job - it only works from sp4), or WLS7. In WLS7, I think MDBs have properties which allow you to connect them to any JNDI tree using a URL and Context Factory. In this case, you use the Sun FileSystem JNDI implementation and IBM's jmsadmin (???) tool to manage the FileSystem JNDI. There are plenty of papers on the web about doing this. Good luck! Dan. _ Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch, Banc of America Securities Limited and Banc of America Futures Incorporated are regulated by the Financial Services Authority. _
RE: [JBoss-user] CMP2.0 and inheritance.
Mark, I found this series of articles to be informative: http://www.onjava.com/pub/a/onjava/2002/09/04/ejbinherit.html Peter -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2003 9:53 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] CMP2.0 and inheritance. Hi folks, If I have an entity bean say ManEJB that inherits from the person class, what restrictions must be imposed on the superclass in order for the inheritance to be valid? Maybe if someone could get perhaps answer the following quick questions if they had the time that would be fantastic. 1. Must the superclass also be declared abstract? 2. Must the superclass implement EntityBean? 3. Must the superclass's fields I wish to persist be declared in the normal fashion? i.e. with abstract accessor methods and the cmp-field elements in the descriptor of the subclass? Thanks, Mark. --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Hello ! The problem of JNDI in JSP !
Dear all ,
Hello ! I am a beginner of JBoss 3.0.7. I encounter a problem of JNDI in JSP . The file structure like follow :
E:\JBoss3T\test_EJB\com\sample\HelloWorld.class
E:\JBoss3T\test_EJB\com\sample\HelloWorldBean.class
E:\JBoss3T\test_EJB\com\sample\HelloWorldHome.class
And the ejb-jar.xml like follow :
?xml version="1.0" encoding="UTF-8"?ejb-jar descriptionJBoss Hello World Application/description display-nameHello World EJB/display-name enterprise-beans session ejb-nameHelloWorld/ejb-name homecom.sample.HelloWorldHome/home remotecom.sample.HelloWorld/remote ejb-classcom.sample.HelloWorldBean/ejb-class session-typeStateless/session-type transaction-typeContainer/transaction-type /session /enterprise-beans/ejb-jar
The jboss.xml like follow :
jboss enterprise-beans session ejb-nameHelloWorld/ejb-name jndi-namecom/sample/HelloWorld/jndi-name /session /enterprise-beans/jboss
The JSP is as follow :
%@ page session="false" isThreadSafe="true" isErrorPage="false" import="javax.naming.*, com.sample.*"%% try { Context lContext = new InitialContext(); HelloWorldHome lHome = (HelloWorldHome) lContext.lookup( "java:comp/env/com/sample/HelloWorld"); HelloWorld lSession = lHome.create(); out.println( "" + lSession.hello() ); } catch( Exception e ) { out.println( "Caugth exception: " + e.getMessage() ); e.printStackTrace(); }%
I alsoresidethe jndi.properties with WEB-INF ( I use the standalone Tomcat ) . The JNDI is displayed in global JNDI Namespace in jmx-console . However , the Tomcat says "Name com is not bound in this Context" .Therefore , what should I further configue ? Jonathan (Wong Yat Sing) Jonathan StudioM.P (852) - 91235947 NetMeeting : [EMAIL PROTECTED]ICQ# 57646152
Do you Yahoo!?
Free online calendar with sync to Outlook(TM).
RE: [JBoss-user] Hello ! The problem of JNDI in JSP !
You should change
your lookup from "java:comp/env/com/sample/HelloWorld" to
"java:/com/sample/HelloWorld". The "comp/env" scope is only used to lookup
bean specific environment attributes that are defined in ejb-jar.xml that is
deployed with the ejb.
Hope that
helps,
Dustin
-Original Message-From: jonathan wong
[mailto:[EMAIL PROTECTED]Sent: Monday, June 09, 2003 1:57
PMTo: [EMAIL PROTECTED]Subject:
[JBoss-user] Hello ! The problem of JNDI in JSP !
Dear all ,
Hello ! I am a beginner of JBoss 3.0.7. I encounter a problem
of JNDI in JSP . The file structure like follow :
E:\JBoss3T\test_EJB\com\sample\HelloWorld.class
E:\JBoss3T\test_EJB\com\sample\HelloWorldBean.class
E:\JBoss3T\test_EJB\com\sample\HelloWorldHome.class
And the ejb-jar.xml like follow :
?xml version="1.0"
encoding="UTF-8"?ejb-jar
descriptionJBoss Hello World
Application/description
display-nameHello World EJB/display-name
enterprise-beans
session
ejb-nameHelloWorld/ejb-name
homecom.sample.HelloWorldHome/home
remotecom.sample.HelloWorld/remote
ejb-classcom.sample.HelloWorldBean/ejb-class
session-typeStateless/session-type!
transaction-typeContainer/transaction-type
/session
/enterprise-beans/ejb-jar
The jboss.xml like follow :
jboss
enterprise-beans
session
ejb-nameHelloWorld/ejb-name
jndi-namecom/sample/HelloWorld/jndi-name
/session
/enterprise-beans/jboss
The JSP is as follow :
%@ page session="false"
isThreadSafe="true" isErrorPage="false"
import="javax.naming.*,
com.sample.*"%% try
{ Context lContext = new
InitialContext(); HelloWorldHome lHome =
(HelloWorldHome)
lContext.lookup(
"java:comp/env/com/sample/HelloWorld");
HelloWorld lSession = lHome.create();
out.println( "" + lSession.hello() ); } catch(
Exception e ) { out.println( "Caugth
exception: " + e.getMessage() );
e.printStackTrace(); }%
I alsoresidethe jndi.properties with WEB-INF ( I use the
standalone Tomcat ) . The JNDI is displayed in global JNDI Namespace in
jmx-console . However , the Tomcat says "Name com is not bound in this
Context" .Therefore , what should I further configue ?
Jonathan (Wong Yat Sing) Jonathan StudioM.P (852) -
91235947 NetMeeting : [EMAIL PROTECTED]ICQ#
57646152
Do you Yahoo!?Free online
calendar with sync to Outlook(TM).
[JBoss-user] @jboss-net:xml-schema
hi i am using xdoclet to generate my entity and session beans but i also
want it to generate my webservices.
i have the part where it generates the web-service.xml defining my
services and mapping them to the correct jndi entries of my session
beans. my session bean methods return custom data objects. the problem
is that xdoclet is not adding the data mapping for my data objects. i
assume i have to use @jboss-net:xml-schema right? where should i add
this entry? my data objects are generated automatically by xdoclet so i
don't think it's there. any ideas anyone? dr jung?
the only source files i have for now is the Payment.java where the
entity bean is generated from and PaymentSession.java where my session
bean is generated from.
this is my ant task:
target name=ejbdoclet depends=prepare
mkdir dir=${build.dir}/xdoclet-classes/
mkdir dir=${build.dir}/webservices/
mkdir dir=${build.dir}/webservices/META-INF/
taskdef
name=ejbdoclet
classname=xdoclet.modules.ejb.EjbDocletTask
classpathref=project.class.path
/
tstamp
format property=TODAY pattern=d-MM-yy/
/tstamp
ejbdoclet
destdir=${build.dir}/xdoclet-classes
excludedtags=@version,@author
addedtags=@xdoclet-generated at ${TODAY}
ejbspec=2.0
fileset dir=${src.dir}
include name=**/*.java/
/fileset
fileset dir=${build.dir}/xdoclet-classes
include name=**/*.java/
/fileset
dataobject/
packageSubstitution packages=persistence
substituteWith=interfaces/
remoteinterface/
localinterface/
homeinterface/
localhomeinterface/
entitypk/
entitycmp/
deploymentdescriptor
destdir=${build.dir}/xdoclet-classes/META-INF/
jboss version=3.0
preferredRelationMapping=relation-table
datasource=java:/ForeclosureFreeSearchPool
datasourcemapping=MS SQLSERVER
destdir=${build.dir}/xdoclet-classes/META-INF/
jbossnet webDeploymentName=HelixWebService prefix=degPrefix
destdir=${build.dir}/webservices/META-INF
targetNameSpace=http://webservices.deg.cc/HelixWebService; /
/ejbdoclet
/target
thanks,
felipe
ps: i am running jvm 1.4, jboss-3.2.1.
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Hello ! The problem of JNDI in JSP !
A couple of considerations:
1) If your JSP is running from a context different
from Jboss, then you should create the InitialContext using the jndi.properties
file like:
InitialContext context = new InitialContext(properties);
2) The jndi name of your bean could be
probablylooked upas:
com/sample/HelloWorld (jboss.xml jndi-name element)
3) The jndi.properties file could(should?) reside
under WEB-INF/classes (but I could be wrong on it!)
Hope it will help,
Marco
- Original Message -
From:
jonathan
wong
To: [EMAIL PROTECTED]
Sent: Monday, June 09, 2003 6:56 PM
Subject: [JBoss-user] Hello ! The problem
of JNDI in JSP !
Dear all ,
Hello ! I am a beginner of JBoss 3.0.7. I encounter a problem
of JNDI in JSP . The file structure like follow :
E:\JBoss3T\test_EJB\com\sample\HelloWorld.class
E:\JBoss3T\test_EJB\com\sample\HelloWorldBean.class
E:\JBoss3T\test_EJB\com\sample\HelloWorldHome.class
And the ejb-jar.xml like follow :
?xml version="1.0"
encoding="UTF-8"?ejb-jar
descriptionJBoss Hello World
Application/description
display-nameHello World EJB/display-name
enterprise-beans
session
ejb-nameHelloWorld/ejb-name
homecom.sample.HelloWorldHome/home
remotecom.sample.HelloWorld/remote
ejb-classcom.sample.HelloWorldBean/ejb-class
session-typeStateless/session-type
transaction-typeContainer/transaction-type
/session
/enterprise-beans/ejb-jar
The jboss.xml like follow :
jboss
enterprise-beans
session
ejb-nameHelloWorld/ejb-name
jndi-namecom/sample/HelloWorld/jndi-name
/session
/enterprise-beans/jboss
The JSP is as follow :
%@ page session="false"
isThreadSafe="true" isErrorPage="false"
import="javax.naming.*,
com.sample.*"%% try
{ Context lContext = new
InitialContext(); HelloWorldHome lHome =
(HelloWorldHome)
lContext.lookup(
"java:comp/env/com/sample/HelloWorld");
HelloWorld lSession = lHome.create();
out.println( "" + lSession.hello() ); } catch(
Exception e ) { out.println( "Caugth
exception: " + e.getMessage() );
e.printStackTrace(); }%
I alsoresidethe jndi.properties with WEB-INF ( I use the
standalone Tomcat ) . The JNDI is displayed in global JNDI Namespace in
jmx-console . However , the Tomcat says "Name com is not bound in this
Context" .Therefore , what should I further configue ?
Jonathan (Wong Yat Sing) Jonathan StudioM.P (852) -
91235947 NetMeeting : [EMAIL PROTECTED]ICQ#
57646152
Do you Yahoo!?Free online
calendar with sync to Outlook(TM).
[JBoss-user] jBoss Remoting limitation
Is there any way to have a remote invocation returna remote referenceinstead of a serialized result?Edward FlickEnterprise Applications Designer / Database Administrator / Web AdministratorCDF, Inc. Do you Yahoo!? Free online calendar with sync to Outlook(TM).
[JBoss-user] Retrieving a mail session object from Jboss [3.2.1]
Hi, I would like to retrieve a javax.mail.Session object from within a class running under Tomcat. I would like to user the javax.mail.Session provided by Jboss. In the jmx-console, I can see that under the java Namespace there is the 'Mail' name; however, from within my class, when I do the following: //setJbossProperties() returns a Properties object set for Jboss. It works as another class uses it and my entity/session //beans work greatly InitialContext context = new InitialContext(JbossService.newInstance().setJbossProperties()); //jndiName contains java:comp/env/Mail Object node = context.lookup(jndiName); session = (Session)PortableRemoteObject.narrow(node, Session.class); I receive the following exception: ERROR 09 Jun 2003 22:37:41,859 framework.MailService -- NamingException while creating a JavaMail Session: comp not bound or, if I set jndiName with java:/Mail ERROR 09 Jun 2003 22:37:41,859 framework.MailService -- NamingException while creating a JavaMail Session: Mail not bound I also tried simply with the following: InitialContext context = new InitialContext(JbossService.newInstance().setJbossProperties()); session = (Session)context.lookup(jndiName); Two questions: 1) Is it possible from an external class (let's say under Tomcat) to retrieve a Session object by simply lookup the Jboss JNDI namespace? 2) Is the source I wrote correct? Thanks for any help, Marco --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] XA connection factory for an MDB
Title: XA connection factory for an MDB My limited knowledge of MDB internals and XA is getting me confused. The basic question that I have is "for what purpose do I need an XA connection factory for an MDB?" Initially, my answer was as follow: If I deploy my MDB with container managed transaction and transaction required, and if the implementation of my onMessage method is accessing an external resource that I want to synchronize through XA with the reading of the message by the MDB, then I need the MDB to use an XA connection factory (so all the resources involved in the transaction are XA "enabled"). I did some testing with JBoss and it seems that even if my MDB is not using an XA transaction, everything is working ok: - I have a MDB listening to a WebSphere MQ queue and not using an XA connection factory. - My onMessage operation is sending a message to a JBoss queue in a transacted session using the JmsXA connection factory. - If I generate an abort in my onMessage method (mdbContext.setRollbackOnly ()), then the rollback is done on the JBoss queue and on the MDB queue. So, either I do not need an XA connection factory for my MDB (and then is there any cases where I will need one), either the fact that it is working on JBoss is for some kind of other reason and I am not doing true XA between the MDB queue and the JBoss one and in some cases (according to where/when the abort is occurring), my transaction integrity between the 2 queues might not be respected. Anyone with a good answer/explanation? Thomas
Re: [JBoss-user] XA connection factory for an MDB
Hi Thomas, [EMAIL PROTECTED] wrote: My limited knowledge of MDB internals and XA is getting me confused. The basic question that I have is for what purpose do I need an XA connection factory for an MDB? To get a 2 phase commit between all the resources involved in the tranasaction. Initially, my answer was as follow: If I deploy my MDB with container managed transaction and transaction required, and if the implementation of my onMessage method is accessing an external resource that I want to synchronize through XA with the reading of the message by the MDB, then I need the MDB to use an XA connection factory (so all the resources involved in the transaction are XA enabled). yes you are correct. I did some testing with JBoss and it seems that even if my MDB is not using an XA transaction, everything is working ok: - I have a MDB listening to a WebSphere MQ queue and not using an XA connection factory. good job. - My onMessage operation is sending a message to a JBoss queue in a transacted session using the JmsXA connection factory. - If I generate an abort in my onMessage method (mdbContext.setRollbackOnly ()), then the rollback is done on the JBoss queue and on the MDB queue. That is correct. The JBoss MDB contaier was created knowing that it would not allways be able to work with an XA connection to get it's messages. If the MDB does not have XA jms provider, it will manually commit/rollback the jms transaction (using Session.commit()/Session.rollback()). So, either I do not need an XA connection factory for my MDB (and then is there any cases where I will need one), either the fact that it is Not strictly needed. working on JBoss is for some kind of other reason and I am not doing true XA between the MDB queue and the JBoss one and in some cases (according to where/when the abort is occurring), my transaction integrity between the 2 queues might not be respected. That's exactly what is going on. The XA transaction is being commited/rolledback and then the MQSeries TX is being commited/rolledback. So you do run the risk of of lossing integrity. Anyone with a good answer/explanation? Thomas Regards, Hiram --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] XA connection factory for an MDB
Thanks a lot I really appreciate the answer. I was not so confused after all :-) As soon as I am trying to use a WebSphere MQ XA connection factory, my MDB never receive any messages. Any pointers on which JBoss classes I should look at/trace through to understand where the problem might be? I do believe that it is an MDB related problem since I am able to do 2PC with a WebSphere MQ queue using an XA connection factory when it is done from within the MDB onMessage method (I configured an XA connector like the JmsXA one but for WS MQ). Thomas -Original Message- From: hiram [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 6:43 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] XA connection factory for an MDB Hi Thomas, [EMAIL PROTECTED] wrote: My limited knowledge of MDB internals and XA is getting me confused. The basic question that I have is for what purpose do I need an XA connection factory for an MDB? To get a 2 phase commit between all the resources involved in the tranasaction. Initially, my answer was as follow: If I deploy my MDB with container managed transaction and transaction required, and if the implementation of my onMessage method is accessing an external resource that I want to synchronize through XA with the reading of the message by the MDB, then I need the MDB to use an XA connection factory (so all the resources involved in the transaction are XA enabled). yes you are correct. I did some testing with JBoss and it seems that even if my MDB is not using an XA transaction, everything is working ok: - I have a MDB listening to a WebSphere MQ queue and not using an XA connection factory. good job. - My onMessage operation is sending a message to a JBoss queue in a transacted session using the JmsXA connection factory. - If I generate an abort in my onMessage method (mdbContext.setRollbackOnly ()), then the rollback is done on the JBoss queue and on the MDB queue. That is correct. The JBoss MDB contaier was created knowing that it would not allways be able to work with an XA connection to get it's messages. If the MDB does not have XA jms provider, it will manually commit/rollback the jms transaction (using Session.commit()/Session.rollback()). So, either I do not need an XA connection factory for my MDB (and then is there any cases where I will need one), either the fact that it is Not strictly needed. working on JBoss is for some kind of other reason and I am not doing true XA between the MDB queue and the JBoss one and in some cases (according to where/when the abort is occurring), my transaction integrity between the 2 queues might not be respected. That's exactly what is going on. The XA transaction is being commited/rolledback and then the MQSeries TX is being commited/rolledback. So you do run the risk of of lossing integrity. Anyone with a good answer/explanation? Thomas Regards, Hiram --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] @jboss-net:xml-schema
On Monday, June 9, 2003, at 01:00 PM, Felipe Oliveira wrote: hi i am using xdoclet to generate my entity and session beans but i also want it to generate my webservices. i have the part where it generates the web-service.xml defining my services and mapping them to the correct jndi entries of my session beans. my session bean methods return custom data objects. the problem is that xdoclet is not adding the data mapping for my data objects. i assume i have to use @jboss-net:xml-schema right? where should i add this entry? my data objects are generated automatically by xdoclet so i don't think it's there. any ideas anyone? dr jung? ya, I have an Idea :-) I am doing something like: * object * name = Symbol * match = * * schema * type=value But that is using value objects (and a hacked template file). If you want to map your dataobjects, it is a simple matter of doing something like: * schema * data-object=true * urn=symbol of course you'll have to grab the xdoclet-module-jboss-net.jar (from the jboss.net/output/lib directory after you've built jboss from source) and place it where ever the rest of your xdoclet jar files are. your ejb-doclet task looks set up o.k. to make it all work -jason
Re: [JBoss-user] Hello ! The problem of JNDI in JSP !
Dear all ,
Hello ! Thank you for all your help . I try to rewrite the JSP like follow :
%@ page session="false" isThreadSafe="true" isErrorPage="false" import="javax.naming.*,java.util.*, com.sample.*"%
% try { Properties properties = new Properties();properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); properties.put(Context.PROVIDER_URL, "localhost:1099"); Context lContext = new InitialContext(properties); HelloWorldHome lHome = (HelloWorldHome) lContext.lookup( "java:/com/sample/HelloWorld"); HelloWorld lSession = lHome.create(); out.println( "" + lSession.hello() ); } catch( Exception e ) { out.println( "Caugth exception: " + e.getMessage() ); e.printStackTrace(); }%
Also , the "jndi.properties" resides the WEB-INF\classes , the structure as follow :
E:\jboss\tomcat-4.1.x\webapps\test\WEB-INF\classes
E:\jboss\tomcat-4.1.x\webapps\test\WEB-INF\classes\jndi.properties
However , the Tomcat still says "Name com is not bound in this Context " if I load the JSP ? Therefore , should I have the futher configurations ? ( I so confuse to place and use jndi.properties and JNDI )Thank you !
Marco Tedone [EMAIL PROTECTED] wrote:
A couple of considerations:
1) If your JSP is running from a context different from Jboss, then you should create the InitialContext using the jndi.properties file like:
InitialContext context = new InitialContext(properties);
2) The jndi name of your bean could be probablylooked upas:
com/sample/HelloWorld (jboss.xml jndi-name element)
3) The jndi.properties file could(should?) reside under WEB-INF/classes (but I could be wrong on it!)
Hope it will help,
Marco
- Original Message -
From: jonathan wong
To: [EMAIL PROTECTED]
Sent: Monday, June 09, 2003 6:56 PM
Subject: [JBoss-user] Hello ! The problem of JNDI in JSP !
Dear all ,
Hello ! I am a beginner of JBoss 3.0.7. I encounter a problem of JNDI in JSP . The file structure like follow :
E:\JBoss3T\test_EJB\com\sample\HelloWorld.class
E:\JBoss3T\test_EJB\com\sample\HelloWorldBean.class
E:\JBoss3T\test_EJB\com\sample\HelloWorldHome.class
And the ejb-jar.xml like follow :
?xml version="1.0" encoding="UTF-8"?ejb-jar descriptionJBoss Hello World Application/description display-nameHello World EJB/display-name enterprise-beans session ejb-nameHelloWorld/ejb-name homecom.sample.HelloWorldHome/home remotecom.sample.HelloWorld/remote ejb-classcom.sample.HelloWorldBean/ejb-class session-typeStateless/session-type transaction-typeContainer/transaction-type /session /enterprise-beans/ejb-jar
The jboss.xml like follow :
jboss enterprise-beans session ejb-nameHelloWorld/ejb-name jndi-namecom/sample/HelloWorld/jndi-name /session /enterprise-beans/jboss
The JSP is as follow :
%@ page session="false" isThreadSafe="true" isErrorPage="false" import="javax.naming.*, com.sample.*"%% try { Context lContext = new InitialContext(); HelloWorldHome lHome = (HelloWorldHome) lContext.lookup( "java:comp/env/com/sample/HelloWorld"); HelloWorld lSession = lHome.create(); out.println( "" + lSession.hello() ); } catch( Exception e ) { out.println( "Caugth exception: " + e.getMessage() ); e.printStackTrace(); }%
I alsoresidethe jndi.properties with WEB-INF ( I use the standalone Tomcat ) . The JNDI is displayed in global JNDI Namespace in jmx-console . However , the Tomcat says "Name com is not bound in this Context" .Therefore , what should I further configue ? Jonathan (Wong Yat Sing) Jonathan StudioM.P (852) - 91235947 NetMeeting : [EMAIL PROTECTED]ICQ# 57646152
Do you Yahoo!?Free online calendar with sync to Outlook(TM).Jonathan (Wong Yat Sing) Jonathan StudioM.P (852) - 91235947 NetMeeting : [EMAIL PROTECTED]ICQ# 57646152
Do you Yahoo!?
Free online calendar with sync to Outlook(TM).
Re: [JBoss-user] XA connection factory for an MDB
Hi Thomas, I have done the Websphere MQ integration with jboss in the past and ran into the same issues. It's not you and it's not jboss. The JMS ASF spec is a little weak in describing who/how the inbound XA transaction gets started. The only way JBossMQ was able to implement the ASF spec was by starting the transaction without an associated XID. Once the message gets delivered to the container, JBossMQ allows the container to associate an XID with the session. The session then assigns the XID to the TX that delivered the message. JBossMQ had to kind of jump through hoops to get this to work. It would have been much easier to allow JBossMQ to assign an XID to the transaction to begin with. WebSphere MQ might be trying to do something like that. But since it's not in the JMS ASF spec, IBM would need to tell us what MQ is expecting (outside the spec) to get the asynch message delivery to work. Other ways to skin this cat: - Don't use the current MDB container invoker (which uses the ASF to do asynch message delivery). Write a new MDB container invoker that does synchronous Receiver.receive() calls to get messages. The problem with this approach is that you need to start a JTA TX before you do the receive() and our current TM will timeout the TXs that take too long. A solution my be to use receiveNoWait() instead. - Implement a MDB conatiner invoker using the new JCA TX inflow stuff. I have not had time to look into this yet or if MQ has a JCA resource adapter but this would be the best solution. Regards, Hiram [EMAIL PROTECTED] wrote: Thanks a lot I really appreciate the answer. I was not so confused after all :-) As soon as I am trying to use a WebSphere MQ XA connection factory, my MDB never receive any messages. Any pointers on which JBoss classes I should look at/trace through to understand where the problem might be? I do believe that it is an MDB related problem since I am able to do 2PC with a WebSphere MQ queue using an XA connection factory when it is done from within the MDB onMessage method (I configured an XA connector like the JmsXA one but for WS MQ). Thomas -Original Message- From: hiram [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 6:43 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] XA connection factory for an MDB Hi Thomas, [EMAIL PROTECTED] wrote: My limited knowledge of MDB internals and XA is getting me confused. The basic question that I have is for what purpose do I need an XA connection factory for an MDB? To get a 2 phase commit between all the resources involved in the tranasaction. Initially, my answer was as follow: If I deploy my MDB with container managed transaction and transaction required, and if the implementation of my onMessage method is accessing an external resource that I want to synchronize through XA with the reading of the message by the MDB, then I need the MDB to use an XA connection factory (so all the resources involved in the transaction are XA enabled). yes you are correct. I did some testing with JBoss and it seems that even if my MDB is not using an XA transaction, everything is working ok: - I have a MDB listening to a WebSphere MQ queue and not using an XA connection factory. good job. - My onMessage operation is sending a message to a JBoss queue in a transacted session using the JmsXA connection factory. - If I generate an abort in my onMessage method (mdbContext.setRollbackOnly ()), then the rollback is done on the JBoss queue and on the MDB queue. That is correct. The JBoss MDB contaier was created knowing that it would not allways be able to work with an XA connection to get it's messages. If the MDB does not have XA jms provider, it will manually commit/rollback the jms transaction (using Session.commit()/Session.rollback()). So, either I do not need an XA connection factory for my MDB (and then is there any cases where I will need one), either the fact that it is Not strictly needed. working on JBoss is for some kind of other reason and I am not doing true XA between the MDB queue and the JBoss one and in some cases (according to where/when the abort is occurring), my transaction integrity between the 2 queues might not be respected. That's exactly what is going on. The XA transaction is being commited/rolledback and then the MQSeries TX is being commited/rolledback. So you do run the risk of of lossing integrity. Anyone with a good answer/explanation? Thomas Regards, Hiram --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Retrieving a mail session object from Jboss [3.2.1]
Here is what I did under 2.4.3. The same thing should work in 3.2.1, as I see mail-service.xml is in the default server. Check your server (either the logs or jmx-console) to make sure the mail service has started properly. Source: Session session = ((Session) new InitialContext().lookup(java:comp/env/mail/Mail)); ejb-jar.xml: resource-ref descriptionA mail session for the Email bean/description res-ref-namemail/Mail/res-ref-name res-typejavax.mail.Session/res-type res-authContainer/res-auth /resource-ref jboss.xml: resource-managers resource-manager res-jndi-namejava:/Mail/res-jndi-name res-namemail/Mail/res-name /resource-manager /resource-managers Marco Tedone wrote: Hi, I would like to retrieve a javax.mail.Session object from within a class running under Tomcat. I would like to user the javax.mail.Session provided by Jboss. In the jmx-console, I can see that under the java Namespace there is the 'Mail' name; however, from within my class, when I do the following: //setJbossProperties() returns a Properties object set for Jboss. It works as another class uses it and my entity/session //beans work greatly InitialContext context = new InitialContext(JbossService.newInstance().setJbossProperties()); //jndiName contains java:comp/env/Mail Object node = context.lookup(jndiName); session = (Session)PortableRemoteObject.narrow(node, Session.class); I receive the following exception: ERROR 09 Jun 2003 22:37:41,859 framework.MailService -- NamingException while creating a JavaMail Session: comp not bound or, if I set jndiName with java:/Mail ERROR 09 Jun 2003 22:37:41,859 framework.MailService -- NamingException while creating a JavaMail Session: Mail not bound I also tried simply with the following: InitialContext context = new InitialContext(JbossService.newInstance().setJbossProperties()); session = (Session)context.lookup(jndiName); Two questions: 1) Is it possible from an external class (let's say under Tomcat) to retrieve a Session object by simply lookup the Jboss JNDI namespace? 2) Is the source I wrote correct? Thanks for any help, Marco --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user -- Guy Rouillier --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] XA connection factory for an MDB
Hiram, Again, thanks a lot for the answers. I supposed I could have spent days trying to understand what was happening. I will try to look into the two solutions you proposed. I am far from being a JBoss expert but I am more than willing to learn. I suppose that to get an idea on what the current code is doing I should look at the org.jboss.ejb.plugins.jms.JMSContainerInvoker and org.jboss.ejb.plugins.TxInterceptorCMT classes? I also do not believe that WSMQ has any JCA resource adapter but I will check. Thanks again for the help. Thomas -Original Message- From: hiram [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 11:01 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] XA connection factory for an MDB Hi Thomas, I have done the Websphere MQ integration with jboss in the past and ran into the same issues. It's not you and it's not jboss. The JMS ASF spec is a little weak in describing who/how the inbound XA transaction gets started. The only way JBossMQ was able to implement the ASF spec was by starting the transaction without an associated XID. Once the message gets delivered to the container, JBossMQ allows the container to associate an XID with the session. The session then assigns the XID to the TX that delivered the message. JBossMQ had to kind of jump through hoops to get this to work. It would have been much easier to allow JBossMQ to assign an XID to the transaction to begin with. WebSphere MQ might be trying to do something like that. But since it's not in the JMS ASF spec, IBM would need to tell us what MQ is expecting (outside the spec) to get the asynch message delivery to work. Other ways to skin this cat: - Don't use the current MDB container invoker (which uses the ASF to do asynch message delivery). Write a new MDB container invoker that does synchronous Receiver.receive() calls to get messages. The problem with this approach is that you need to start a JTA TX before you do the receive() and our current TM will timeout the TXs that take too long. A solution my be to use receiveNoWait() instead. - Implement a MDB conatiner invoker using the new JCA TX inflow stuff. I have not had time to look into this yet or if MQ has a JCA resource adapter but this would be the best solution. Regards, Hiram [EMAIL PROTECTED] wrote: Thanks a lot I really appreciate the answer. I was not so confused after all :-) As soon as I am trying to use a WebSphere MQ XA connection factory, my MDB never receive any messages. Any pointers on which JBoss classes I should look at/trace through to understand where the problem might be? I do believe that it is an MDB related problem since I am able to do 2PC with a WebSphere MQ queue using an XA connection factory when it is done from within the MDB onMessage method (I configured an XA connector like the JmsXA one but for WS MQ). Thomas -Original Message- From: hiram [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 6:43 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] XA connection factory for an MDB Hi Thomas, [EMAIL PROTECTED] wrote: My limited knowledge of MDB internals and XA is getting me confused. The basic question that I have is for what purpose do I need an XA connection factory for an MDB? To get a 2 phase commit between all the resources involved in the tranasaction. Initially, my answer was as follow: If I deploy my MDB with container managed transaction and transaction required, and if the implementation of my onMessage method is accessing an external resource that I want to synchronize through XA with the reading of the message by the MDB, then I need the MDB to use an XA connection factory (so all the resources involved in the transaction are XA enabled). yes you are correct. I did some testing with JBoss and it seems that even if my MDB is not using an XA transaction, everything is working ok: - I have a MDB listening to a WebSphere MQ queue and not using an XA connection factory. good job. - My onMessage operation is sending a message to a JBoss queue in a transacted session using the JmsXA connection factory. - If I generate an abort in my onMessage method (mdbContext.setRollbackOnly ()), then the rollback is done on the JBoss queue and on the MDB queue. That is correct. The JBoss MDB contaier was created knowing that it would not allways be able to work with an XA connection to get it's messages. If the MDB does not have XA jms provider, it will manually commit/rollback the jms transaction (using Session.commit()/Session.rollback()). So, either I do not need an XA connection factory for my MDB (and then is there any cases where I will need one), either the fact that it is Not strictly needed. working on JBoss is for some kind of other reason and I am not doing true XA between the MDB queue and the JBoss one and in some cases (according to
[JBoss-user] 13:15:47
,remove [EMAIL PROTECTED] www.mailfair.com --- [] 2000 http://www.freeway.cn/pages/agent.htm 13:15:47 --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
