[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 17-July-2002
Number of tests run: 669
Successful tests: 665
Errors:4
Failures: 0
[time of test: 17 July 2002 0:30 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
[java.vm.version: 1.3.1]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Mac OS X]
[os.arch: ppc]
[os.version: 10.1.5]
See http://lubega.com/testarchive/${build.uid} for details of this test.
See http://lubega.com for general test information.
NOTE: If there are any errors shown above - this mail is only highlighting
them - it is NOT indicating that they are being looked at by anyone.
Remember - if a test becomes broken after your changes - fix it or fix the test!
Oh dear - still got some errors!
Thanks for all your effort - we really do love you!
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-581847 ] lt;ejb-linkgt; doesn't work properly
Bugs item #581847, was opened at 2002-07-15 11:42
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=581847group_id=22866
Category: JBossSOAP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Mario Däpp (mdaepp)
Assigned to: Nobody/Anonymous (nobody)
Summary: lt;ejb-linkgt; doesn't work properly
Initial Comment:
System Info:
21:12:20,813 INFO [Server] JBoss Release: JBoss-3.0.0
CVSTag=JBoss_3_0_0
21:12:29,812 INFO [ServerInfo] Java version: 1.4.0,Sun
Microsystems Inc.
21:12:29,813 INFO [ServerInfo] Java VM: Java
HotSpot(TM) Server VM 1.4.0-b92,Sun Microsystems Inc.
21:12:29,814 INFO [ServerInfo] OS-System: SunOS 5.8,sparc
This is JBoss with Tomcat.
I'm using a slightly altered version of the original
jboss-net.sar (replaced AxisService to fix the /axis/*
context root problem with Catalina)
ejb-link in ejb-ref in web-service.xml doesn't work
propertly. If I enter the bean-name here (that's what
I think belongs here), then it doesn't work
(NamingException on the client side saying that
UppercaseService is not bound). If I enter the JNDI
name, it works.
I expect this bug to be reproducible if the JNDI name
in jboss.net.sample.hello.ejb.HelloBean is changed to
something else than Hello.
Excerpt from web-service.xml:
...
ejb-ref
ejb-ref-nameejb/UppercaseService/ejb-ref-name
!-- ejb-linkUppercaseService/ejb-link *DOESN'T
WORK* --
ejb-linklocal/oois/demo/UppercaseService/ejb-link
/ejb-ref
service name=Uppercase provider=Handler
parameter name=handlerClass
value=org.jboss.net.axis.server.EJBProvider
/
parameter name=beanJndiName
value=java:comp/env/ejb/UppercaseService /
parameter name=homeInterfaceName
value=ch.isbiel.oois.demo.UppercaseServ
iceLocalHome /
...
Excerpt from UppercaseServiceBean:
/**
* @ejb:bean name=UppercaseService type=Stateless
display-name=UppercaseServiceEJB view-type=local
local-jndi-name=local/oois/demo/UppercaseService
* @ejb:interface generate=local
* @ejb:util generate=logical
*/
public class UppercaseServiceBean implements SessionBean {
...
--
Comment By: Mario Däpp (mdaepp)
Date: 2002-07-17 02:00
Message:
Logged In: YES
user_id=136508
Sorry, there's a typo. What I meant to write was ejb-name
istead of bean-name.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=581847group_id=22866
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-581847 ] lt;ejb-linkgt; doesn't work properly
Bugs item #581847, was opened at 2002-07-15 21:42
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=581847group_id=22866
Category: JBossSOAP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: Remind
Priority: 5
Submitted By: Mario Däpp (mdaepp)
Assigned to: Dr. Christoph Georg Jung (cgjung)
Summary: lt;ejb-linkgt; doesn't work properly
Initial Comment:
System Info:
21:12:20,813 INFO [Server] JBoss Release: JBoss-3.0.0
CVSTag=JBoss_3_0_0
21:12:29,812 INFO [ServerInfo] Java version: 1.4.0,Sun
Microsystems Inc.
21:12:29,813 INFO [ServerInfo] Java VM: Java
HotSpot(TM) Server VM 1.4.0-b92,Sun Microsystems Inc.
21:12:29,814 INFO [ServerInfo] OS-System: SunOS 5.8,sparc
This is JBoss with Tomcat.
I'm using a slightly altered version of the original
jboss-net.sar (replaced AxisService to fix the /axis/*
context root problem with Catalina)
ejb-link in ejb-ref in web-service.xml doesn't work
propertly. If I enter the bean-name here (that's what
I think belongs here), then it doesn't work
(NamingException on the client side saying that
UppercaseService is not bound). If I enter the JNDI
name, it works.
I expect this bug to be reproducible if the JNDI name
in jboss.net.sample.hello.ejb.HelloBean is changed to
something else than Hello.
Excerpt from web-service.xml:
...
ejb-ref
ejb-ref-nameejb/UppercaseService/ejb-ref-name
!-- ejb-linkUppercaseService/ejb-link *DOESN'T
WORK* --
ejb-linklocal/oois/demo/UppercaseService/ejb-link
/ejb-ref
service name=Uppercase provider=Handler
parameter name=handlerClass
value=org.jboss.net.axis.server.EJBProvider
/
parameter name=beanJndiName
value=java:comp/env/ejb/UppercaseService /
parameter name=homeInterfaceName
value=ch.isbiel.oois.demo.UppercaseServ
iceLocalHome /
...
Excerpt from UppercaseServiceBean:
/**
* @ejb:bean name=UppercaseService type=Stateless
display-name=UppercaseServiceEJB view-type=local
local-jndi-name=local/oois/demo/UppercaseService
* @ejb:interface generate=local
* @ejb:util generate=logical
*/
public class UppercaseServiceBean implements SessionBean {
...
--
Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2002-07-17 12:23
Message:
Logged In: YES
user_id=175199
Hi,
I have to admit that I implemented the ejb-ref/ feature in
the web-service.xml by simple copyingpasting from the
WebContainer code.
Hence it follows the same semantics than ejb-ref/ in web-
application.xml (which could be different from ejb-ref/ in ejb-
jar.xml, me totally ignorant here)
In the meantime, I have come to the conclusion that the
feature doesn´t buy you anything in your web-service
implementation.
Unlike in a web-app: In your web-app, you will implement a
servlet, hence java code, that runs against the link names
instead of the mapped and changeable jndi names, right?
In your web-service there is no additional Java code involved
that hardcodes the JNDIname. Hence I would suggest that
you use the fully-qualified jndiname to your bean directly in
the EJBProvider service definition and leave the ejb-refs out. It
doesnt matter if you have to change the ejb-ref or the
jndiName entry in the web-service.xml, right?
So ejb-ref/ will vanish in one of the next versions of
jboss.net, unless you have another strong argument for it
(security? I really dunno).
CGJ
--
Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2002-07-17 12:22
Message:
Logged In: YES
user_id=175199
Hi,
I have to admit that I implemented the ejb-ref/ feature in
the web-service.xml by simple copyingpasting from the
WebContainer code.
Hence it follows the same semantics than ejb-ref/ in web-
application.xml (which could be different from ejb-ref/ in ejb-
jar.xml, me totally ignorant here)
In the meantime, I have come to the conclusion that the
feature doesn´t buy you anything in your web-service
implementation.
Unlike in a web-app: In your web-app, you will implement a
servlet, hence java code, that runs against the link names
instead of the mapped and changeable jndi names, right?
In your web-service there is no additional Java code involved
that hardcodes the JNDIname. Hence I would suggest that
you use the fully-qualified jndiname to your bean directly in
the EJBProvider service definition and leave the ejb-refs out. It
doesnt matter if you have to change the ejb-ref or the
jndiName entry in the web-service.xml, right?
So ejb-ref/ will vanish in one of the next versions of
jboss.net, unless you have another strong argument for it
(security? I really dunno).
CGJ
--
Comment By: Mario Däpp (mdaepp)
Date: 2002-07-17 12:00
Message:
Logged In: YES
user_id=136508
Sorry, there's a typo. What I meant to write was ejb-name
istead of bean-name.
[JBoss-dev] [ jboss-Bugs-581847 ] lt;ejb-linkgt; doesn't work properly
Bugs item #581847, was opened at 2002-07-15 21:42
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=581847group_id=22866
Category: JBossSOAP
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Mario Däpp (mdaepp)
Assigned to: Nobody/Anonymous (nobody)
Summary: lt;ejb-linkgt; doesn't work properly
Initial Comment:
System Info:
21:12:20,813 INFO [Server] JBoss Release: JBoss-3.0.0
CVSTag=JBoss_3_0_0
21:12:29,812 INFO [ServerInfo] Java version: 1.4.0,Sun
Microsystems Inc.
21:12:29,813 INFO [ServerInfo] Java VM: Java
HotSpot(TM) Server VM 1.4.0-b92,Sun Microsystems Inc.
21:12:29,814 INFO [ServerInfo] OS-System: SunOS 5.8,sparc
This is JBoss with Tomcat.
I'm using a slightly altered version of the original
jboss-net.sar (replaced AxisService to fix the /axis/*
context root problem with Catalina)
ejb-link in ejb-ref in web-service.xml doesn't work
propertly. If I enter the bean-name here (that's what
I think belongs here), then it doesn't work
(NamingException on the client side saying that
UppercaseService is not bound). If I enter the JNDI
name, it works.
I expect this bug to be reproducible if the JNDI name
in jboss.net.sample.hello.ejb.HelloBean is changed to
something else than Hello.
Excerpt from web-service.xml:
...
ejb-ref
ejb-ref-nameejb/UppercaseService/ejb-ref-name
!-- ejb-linkUppercaseService/ejb-link *DOESN'T
WORK* --
ejb-linklocal/oois/demo/UppercaseService/ejb-link
/ejb-ref
service name=Uppercase provider=Handler
parameter name=handlerClass
value=org.jboss.net.axis.server.EJBProvider
/
parameter name=beanJndiName
value=java:comp/env/ejb/UppercaseService /
parameter name=homeInterfaceName
value=ch.isbiel.oois.demo.UppercaseServ
iceLocalHome /
...
Excerpt from UppercaseServiceBean:
/**
* @ejb:bean name=UppercaseService type=Stateless
display-name=UppercaseServiceEJB view-type=local
local-jndi-name=local/oois/demo/UppercaseService
* @ejb:interface generate=local
* @ejb:util generate=logical
*/
public class UppercaseServiceBean implements SessionBean {
...
--
Comment By: Dr. Christoph Georg Jung (cgjung)
Date: 2002-07-17 12:22
Message:
Logged In: YES
user_id=175199
Hi,
I have to admit that I implemented the ejb-ref/ feature in
the web-service.xml by simple copyingpasting from the
WebContainer code.
Hence it follows the same semantics than ejb-ref/ in web-
application.xml (which could be different from ejb-ref/ in ejb-
jar.xml, me totally ignorant here)
In the meantime, I have come to the conclusion that the
feature doesn´t buy you anything in your web-service
implementation.
Unlike in a web-app: In your web-app, you will implement a
servlet, hence java code, that runs against the link names
instead of the mapped and changeable jndi names, right?
In your web-service there is no additional Java code involved
that hardcodes the JNDIname. Hence I would suggest that
you use the fully-qualified jndiname to your bean directly in
the EJBProvider service definition and leave the ejb-refs out. It
doesnt matter if you have to change the ejb-ref or the
jndiName entry in the web-service.xml, right?
So ejb-ref/ will vanish in one of the next versions of
jboss.net, unless you have another strong argument for it
(security? I really dunno).
CGJ
--
Comment By: Mario Däpp (mdaepp)
Date: 2002-07-17 12:00
Message:
Logged In: YES
user_id=136508
Sorry, there's a typo. What I meant to write was ejb-name
istead of bean-name.
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=376685aid=581847group_id=22866
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] code submission
I have a patch for bug [ 564890 ] JMS recover/redelivery errors that I have tested and am ready to submit for review. I just have a few questions. 1) What is the best way to submit code patches for bugs. Is diff output preferred or just include the entire method that is changed? 2) Is it best to submit the code through the sourceforge interface at the bug report, or just email it to the dev list? Thanks, Seth --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582766 ] 3.0.1RC1 - can't find data source
Bugs item #582766, was opened at 2002-07-17 12:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582766group_id=22866 Category: JBossCMP Group: v3.1 Status: Open Resolution: None Priority: 5 Submitted By: Udo Klinkmüller (ukkm) Assigned to: Nobody/Anonymous (nobody) Summary: 3.0.1RC1 - can't find data source Initial Comment: My environment: - Linux - JDK 1.4 - JBoss 3.0.1RC1 with Tomcat 4.0.4 I switched to the version 3.0.1 and now while the deployment process I get following error which didn't occurre in 3.0.0: org.jboss.deployment.DeploymentException: Error: can't find data source: java:CocoDS; - nested throwable: (javax.naming.NameNotFoundException: CocoDS not bound) When I have a look in the server.log, in my opinion the data source named CocoDS has been deployed correctly. But after that when the first EntityBean (CMP 2.0) is deployed the error occurres now. -- Comment By: Udo Klinkmüller (ukkm) Date: 2002-07-17 12:56 Message: Logged In: YES user_id=573151 Attached you find the server.log and my deployment descriptor files -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582766group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582766 ] 3.0.1RC1 - can't find data source
Bugs item #582766, was opened at 2002-07-17 12:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582766group_id=22866 Category: JBossCMP Group: v3.1 Status: Open Resolution: None Priority: 7 Submitted By: Udo Klinkmüller (ukkm) Assigned to: Nobody/Anonymous (nobody) Summary: 3.0.1RC1 - can't find data source Initial Comment: My environment: - Linux - JDK 1.4 - JBoss 3.0.1RC1 with Tomcat 4.0.4 I switched to the version 3.0.1 and now while the deployment process I get following error which didn't occurre in 3.0.0: org.jboss.deployment.DeploymentException: Error: can't find data source: java:CocoDS; - nested throwable: (javax.naming.NameNotFoundException: CocoDS not bound) When I have a look in the server.log, in my opinion the data source named CocoDS has been deployed correctly. But after that when the first EntityBean (CMP 2.0) is deployed the error occurres now. -- Comment By: Udo Klinkmüller (ukkm) Date: 2002-07-17 12:56 Message: Logged In: YES user_id=573151 Attached you find the server.log and my deployment descriptor files -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582766group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Realm TomcatJboss Configuration
Hello, i am trying to configure Tomcat to add a JDBC Realm, i have installed the TomcatJboss embedded version, i need to know what config file i need to change to add the realm... I would like too to have some tutorials or any kind of help about the Realms... Thanks good bye --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] code submission
diff posted to SF tracker or you can ask marcf for rw if you feel like fixing more bugs -- Juha On Wed, 17 Jul 2002, Seth Sites wrote: I have a patch for bug [ 564890 ] JMS recover/redelivery errors that I have tested and am ready to submit for review. I just have a few questions. 1) What is the best way to submit code patches for bugs. Is diff output preferred or just include the entire method that is changed? 2) Is it best to submit the code through the sourceforge interface at the bug report, or just email it to the dev list? Thanks, Seth --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- Juha Lindfors Author of JMX: Managing J2EE with Java Management Extensions Tel: +358 40 8656 751 (GSM) --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Realm TomcatJboss Configuration
Hello Ruben, Wednesday, July 17, 2002, 2:11:17 PM, you wrote: RN Hello, i am trying to configure Tomcat to add a JDBC Realm, i have installed Do you want to configure JDBC based loging module? It's done in login-config.xml. There are examples for datasource login configurations in docs directory. Or you want to configure DabaseServerLoginModule? alex RN the TomcatJboss embedded version, i need to know what config file i need to RN change to add the realm... RN I would like too to have some tutorials or any kind of help about the RN Realms... RN Thanks good bye RN --- RN This sf.net email is sponsored by:ThinkGeek RN Welcome to geek heaven. RN http://thinkgeek.com/sf RN ___ RN Jboss-development mailing list RN [EMAIL PROTECTED] RN https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] code submission
Submit a unified patch (diff -u) to the sourceforge jboss project, look for the 'patches' section, note submitting to this will cause sourceforge to send an e-mail to the dev-list anyway. On Wed, Jul 17, 2002 at 06:27:58AM -0400, Seth Sites wrote: I have a patch for bug [ 564890 ] JMS recover/redelivery errors that I have tested and am ready to submit for review. I just have a few questions. 1) What is the best way to submit code patches for bugs. Is diff output preferred or just include the entire method that is changed? 2) Is it best to submit the code through the sourceforge interface at the bug report, or just email it to the dev list? Thanks, Seth --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development -- regards Neale Swinnerton --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Realm TomcatJboss Configuration
hello Alex, thanks for your time... i havent found the login-config.xml... , and yes, i want to configure JDBC based loging module, i have readed that the realms are for this... i have found documentation for tomcat, but for the embedded installation nothing... Thanks again Ruben -Original Message- From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] Sent: 17 July 2002 13:30 To: Ruben Nistal Cc: '[EMAIL PROTECTED]' Subject: Re: [JBoss-dev] Realm TomcatJboss Configuration Hello Ruben, Wednesday, July 17, 2002, 2:11:17 PM, you wrote: RN Hello, i am trying to configure Tomcat to add a JDBC Realm, i have installed Do you want to configure JDBC based loging module? It's done in login-config.xml. There are examples for datasource login configurations in docs directory. Or you want to configure DabaseServerLoginModule? alex RN the TomcatJboss embedded version, i need to know what config file i need to RN change to add the realm... RN I would like too to have some tutorials or any kind of help about the RN Realms... RN Thanks good bye RN --- RN This sf.net email is sponsored by:ThinkGeek RN Welcome to geek heaven. RN http://thinkgeek.com/sf RN ___ RN Jboss-development mailing list RN [EMAIL PROTECTED] RN https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Realm TomcatJboss Configuration
Please take this to the forums for help, Alex in the future please redirect users to the forums and answer there. marcf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Ruben Nistal Sent: Wednesday, July 17, 2002 8:54 AM To: '[EMAIL PROTECTED]' Subject: RE: [JBoss-dev] Realm TomcatJboss Configuration hello Alex, thanks for your time... i havent found the login-config.xml... , and yes, i want to configure JDBC based loging module, i have readed that the realms are for this... i have found documentation for tomcat, but for the embedded installation nothing... Thanks again Ruben -Original Message- From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] Sent: 17 July 2002 13:30 To: Ruben Nistal Cc: '[EMAIL PROTECTED]' Subject: Re: [JBoss-dev] Realm TomcatJboss Configuration Hello Ruben, Wednesday, July 17, 2002, 2:11:17 PM, you wrote: RN Hello, i am trying to configure Tomcat to add a JDBC Realm, i have installed Do you want to configure JDBC based loging module? It's done in login-config.xml. There are examples for datasource login configurations in docs directory. Or you want to configure DabaseServerLoginModule? alex RN the TomcatJboss embedded version, i need to know what config file i need to RN change to add the realm... RN I would like too to have some tutorials or any kind of help about RN the Realms... RN Thanks good bye RN --- RN This sf.net email is sponsored by:ThinkGeek RN Welcome to geek heaven. RN http://thinkgeek.com/sf RN ___ RN Jboss-development mailing list RN [EMAIL PROTECTED] RN https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] Realm TomcatJboss Configuration
What JBoss version do you use? login-config.xml is used since 3.0. And you should find docs directory with examples for datasource configurations including login configuration. alex RN hello Alex, thanks for your time... i havent found the login-config.xml... , RN and yes, i want to configure JDBC based loging module, i have readed that RN the realms are for this... i have found documentation for tomcat, but for RN the embedded installation nothing... RN Thanks again RN Ruben RN -Original Message- RN From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] RN Sent: 17 July 2002 13:30 RN To: Ruben Nistal RN Cc: '[EMAIL PROTECTED]' RN Subject: Re: [JBoss-dev] Realm TomcatJboss Configuration RN Hello Ruben, RN Wednesday, July 17, 2002, 2:11:17 PM, you wrote: RN Hello, i am trying to configure Tomcat to add a JDBC Realm, i have RN installed RN Do you want to configure JDBC based loging module? RN It's done in login-config.xml. RN There are examples for datasource login configurations in docs RN directory. RN Or you want to configure DabaseServerLoginModule? RN alex RN the TomcatJboss embedded version, i need to know what config file i RN need to RN change to add the realm... RN I would like too to have some tutorials or any kind of help about the RN Realms... RN Thanks good bye RN --- RN This sf.net email is sponsored by:ThinkGeek RN Welcome to geek heaven. RN http://thinkgeek.com/sf RN ___ RN Jboss-development mailing list RN [EMAIL PROTECTED] RN https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: Re[2]: [JBoss-dev] Realm TomcatJboss Configuration
Hello, i am using tomcat 4.0.1Jboss2.4.4 embedded installation... Thanks again.. :D -Original Message- From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] Sent: 17 July 2002 15:11 To: Ruben Nistal Cc: '[EMAIL PROTECTED]' Subject: Re[2]: [JBoss-dev] Realm TomcatJboss Configuration What JBoss version do you use? login-config.xml is used since 3.0. And you should find docs directory with examples for datasource configurations including login configuration. alex RN hello Alex, thanks for your time... i havent found the login-config.xml... , RN and yes, i want to configure JDBC based loging module, i have readed that RN the realms are for this... i have found documentation for tomcat, but for RN the embedded installation nothing... RN Thanks again RN Ruben RN -Original Message- RN From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] RN Sent: 17 July 2002 13:30 RN To: Ruben Nistal RN Cc: '[EMAIL PROTECTED]' RN Subject: Re: [JBoss-dev] Realm TomcatJboss Configuration RN Hello Ruben, RN Wednesday, July 17, 2002, 2:11:17 PM, you wrote: RN Hello, i am trying to configure Tomcat to add a JDBC Realm, i have RN installed RN Do you want to configure JDBC based loging module? RN It's done in login-config.xml. RN There are examples for datasource login configurations in docs RN directory. RN Or you want to configure DabaseServerLoginModule? RN alex RN the TomcatJboss embedded version, i need to know what config file i RN need to RN change to add the realm... RN I would like too to have some tutorials or any kind of help about the RN Realms... RN Thanks good bye RN --- RN This sf.net email is sponsored by:ThinkGeek RN Welcome to geek heaven. RN http://thinkgeek.com/sf RN ___ RN Jboss-development mailing list RN [EMAIL PROTECTED] RN https://lists.sourceforge.net/lists/listinfo/jboss-development -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Feature Requests-582820 ] EJB-WEB Framework
Feature Requests item #582820, was opened at 2002-07-17 06:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376688aid=582820group_id=22866 Category: None Group: None Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: EJB-WEB Framework Initial Comment: I've written a very neat framework for EJB based applications (very good web support), where instead of having a bean for every table, I have a generic bean that takes care of all SQL operations and you do not have to write a single line of code. I was thinking to donate this framework to JBOSS projects; plus, the framework was successfully tested under JBOSS3.0 and MySQL. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376688aid=582820group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re[2]: [JBoss-dev] Realm TomcatJboss Configuration
Hello marc, I am sorry, guys. I haven't looked at the address. Yes, I'll do next time. --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] RE: InputStream and JarFile are not closed in getManifest()
The
problem seems more complicated than I thought initially. The suggested fix
alone does not solve the problem. I also found input or output streams are
not closed in more places spread in different packages.
One of
the causes of the problem, I think, is the wayhow the deployers
work. When an application is deployed, JAR files are opened by creating
new JarFile objects to peek the info of the JAR file. For example, in the
accept() method of the JARDeployer class, JarFile object is created to check if
the JAR file contains META-INF or *.xml file or not. But, the JarFile objects
never closes because they are returned by JarURLConnection objects and it
closing the JarFilecould cause the close of the application archive file
and therefore will break the deployment. Hence, the files are left
open. However, when the application is undeployed, there is no way to
check if the file is open or not in the deployer system and the opened files
never get closed. I think this is the reason why the temp files and directories
cannot be deleted during undeploying an application. And, it is also the
reason why repeated deploy and undeploy eventually causes "Too many open files"
problem.
Some
non-trivial work might need to sort this out.
Please
let me know if I am correct or not.
Regards
Qingxian
-Original
-Original Message-From: Scott M Stark
[mailto:[EMAIL PROTECTED]]Sent: 16 July 2002
18:29To: [EMAIL PROTECTED]Subject:
Re: [JBoss-dev] RE: InputStream and JarFile are not closed in
getManifest()
Have you verified that the suggested change fixes
the problem?
Scott StarkChief Technology
OfficerJBoss Group, LLC
- Original Message -
From:
Qingxian Wang
To: '[EMAIL PROTECTED]'
Sent: Tuesday, July 16, 2002 10:00
AM
Subject: [JBoss-dev] RE: InputStream
and JarFile are not closed in getManifest()
And this the reason why JBoss cannot delete the files after undeploy
EAR files or SAR files.
Qingxian
-Original Message-From: Qingxian Wang
Sent: 16 July 2002 17:55To: '[EMAIL PROTECTED]'Subject:
InputStream and JarFile are not closed in
getManifest()
The getManifest() method of DeploymentInfo class
in org.jboss.deployment package does not close FileInputStream and JarFile
after creating or getting a Manifest object. This perhaps is the
reason why JBoss cannot close JAR files when undeploying EAR or SAR files
and therefore "Too many open files" problem is caused.
The snipet of the JBoss (3.0.0) code is as
follows:
/** * getManifest returns
(if present) the deployment's manifest * it is lazy
loaded to work from the localURL */
public Manifest getManifest()
{ try
{ if (manifest ==
null)
{
File file = new
File(localUrl.getFile());
if
(file.isDirectory())
manifest= new Manifest(new FileInputStream(new File(file,
"META-INF/MANIFEST.MF")));
else // a
jar
manifest = new
JarFile(file).getManifest();
}
return
manifest;
} // It is ok to barf at any time in the
above, means no manifest catch
(Exception ignored) { return null;} }
The suggested changesare as
below:
public Manifest getManifest()
{ try
{ if (manifest ==
null)
{
File file = new
File(localUrl.getFile());
if
(file.isDirectory())
{
FileInputStream fis = null;
try
{
fis = new FileInputStream(new File(file,
"META-INF/MANIFEST.MF"));
manifest= new
Manifest(fis);
} finally {// close the input
stream
fis.close();
} }
else {// a
jar
JarFile jarFile = new
JarFile(file);
try
{
manifest =
jarFile.getManifest();
} finally { // close the
JarFile
jarFile.close();
}
}
}
return
manifest;
} // It is ok to barf at any time in the
above, means no manifest catch
(Exception ignored) { return null;} }
Regards
Qingxian
Wang
This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom it is addressed. If you have received this e-mail in error you must not copy, distribute or take any action in reliance on it. Please notify the sender by e-mail or telephone.
We utilise an anti-virus system and therefore any files sent via e-mail will have been checked for known viruses. You are however advised to run your own virus check before opening any attachments received as we will not in any
[JBoss-dev] [ jboss-Bugs-582766 ] 3.0.1RC1 - can't find data source
Bugs item #582766, was opened at 2002-07-17 03:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582766group_id=22866 Category: JBossCMP Group: v3.1 Status: Closed Resolution: Invalid Priority: 7 Submitted By: Udo Klinkmüller (ukkm) Assigned to: Nobody/Anonymous (nobody) Summary: 3.0.1RC1 - can't find data source Initial Comment: My environment: - Linux - JDK 1.4 - JBoss 3.0.1RC1 with Tomcat 4.0.4 I switched to the version 3.0.1 and now while the deployment process I get following error which didn't occurre in 3.0.0: org.jboss.deployment.DeploymentException: Error: can't find data source: java:CocoDS; - nested throwable: (javax.naming.NameNotFoundException: CocoDS not bound) When I have a look in the server.log, in my opinion the data source named CocoDS has been deployed correctly. But after that when the first EntityBean (CMP 2.0) is deployed the error occurres now. -- Comment By: Scott M Stark (starksm) Date: 2002-07-17 07:31 Message: Logged In: YES user_id=175228 The datasource dependency on the service named jboss.security:name=JaasSecurityManager in your service descriptor needs to be changed to jboss.security:service=JaasSecurityManager -- Comment By: Udo Klinkmüller (ukkm) Date: 2002-07-17 03:56 Message: Logged In: YES user_id=573151 Attached you find the server.log and my deployment descriptor files -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582766group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: [jboss-cvs] jboss-transaction/src/main/org/jboss/tm TransactionImpl.java
Ole Husgaard wrote:
+ // Using the construct
+ // try {
+ // txCapsule.doSomething();
+ // } catch (NullPointerException ex) {
+ // throw new IllegalStateException(No transaction.);
+ // }
+ // may look like bad programming style, but it is needed to avoid to
+ // synchronize on these methods. If we used a construct like
+ // if (txCapsule == null)
+ // throw new IllegalStateException(No transaction.);
+ // txCapsule.doSomething();
+ // we can get spurious NullPointerExceptions when racing with the
+ // transaction completion.
+
public void commit()
throws RollbackException,
@@ -68,9 +83,11 @@
java.lang.IllegalStateException,
SystemException
{
- if( txCapsule == null )
+ try {
+ txCapsule.commit();
+ } catch (NullPointerException ex) {
throw new IllegalStateException(No transaction.);
- txCapsule.commit();
+ }
Interesting... Is this actually faster then synchronizing? Have you
measured it?
About a month ago I saw a presentation on Hot Spot and they claim that
the synchronized keyword has very little over head (something like 3
extra stack pushed and a lock grab), but exception handling like this
can be very expensive because Hot Spot purposely does not optimize
exception handling (which means that an exception can cost 100-1000
times longer then the non-excetion code).
The only way I could see that this code be faster is if there is a lot
of contention. Is there?
--
Dain Sundstrom
Chief Architect JBossCMP
JBoss Group, LLC
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] RE: InputStream and JarFile are not closed in getManifest()
Title: Message
qingxian when you are ready to commit let me know I will give you
RW
marcf
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of
Qingxian WangSent: Wednesday, July 17, 2002 10:00
AMTo: '[EMAIL PROTECTED]'Cc: Theo
Harper; Lee StokesSubject: RE: [JBoss-dev] RE: InputStream and
JarFile are not closed in getManifest()
The
problem seems more complicated than I thought initially. The suggested
fix alone does not solve the problem. I also found input or output
streams are not closed in more places spread in different packages.
One
of the causes of the problem, I think, is the wayhow the deployers
work. When an application is deployed, JAR files are opened by creating
new JarFile objects to peek the info of the JAR file. For example, in
the accept() method of the JARDeployer class, JarFile object is created to
check if the JAR file contains META-INF or *.xml file or not. But, the JarFile
objects never closes because they are returned by JarURLConnection objects and
it closing the JarFilecould cause the close of the application archive
file and therefore will break the deployment. Hence, the files are left
open. However, when the application is undeployed, there is no way to
check if the file is open or not in the deployer system and the opened files
never get closed. I think this is the reason why the temp files and
directories cannot be deleted during undeploying an application. And, it
is also the reason why repeated deploy and undeploy eventually causes "Too
many open files" problem.
Some
non-trivial work might need to sort this out.
Please let me know if I am correct or not.
Regards
Qingxian
-Original
-Original Message-From: Scott M Stark
[mailto:[EMAIL PROTECTED]]Sent: 16 July 2002
18:29To:
[EMAIL PROTECTED]Subject: Re: [JBoss-dev]
RE: InputStream and JarFile are not closed in
getManifest()
Have you verified that the suggested change
fixes the problem?
Scott StarkChief Technology
OfficerJBoss Group, LLC
- Original Message -
From:
Qingxian Wang
To: '[EMAIL PROTECTED]'
Sent: Tuesday, July 16, 2002 10:00
AM
Subject: [JBoss-dev] RE: InputStream
and JarFile are not closed in getManifest()
And this the reason why JBoss cannot delete the files after
undeploy EAR files or SAR files.
Qingxian
-Original Message-From: Qingxian Wang
Sent: 16 July 2002 17:55To: '[EMAIL PROTECTED]'Subject:
InputStream and JarFile are not closed in
getManifest()
The getManifest() method of DeploymentInfo
class in org.jboss.deployment package does not close FileInputStream and
JarFile after creating or getting a Manifest object. This perhaps
is the reason why JBoss cannot close JAR files when undeploying EAR or
SAR files and therefore "Too many open files" problem is caused.
The snipet of the JBoss (3.0.0) code is as
follows:
/** * getManifest returns
(if present) the deployment's manifest * it is
lazy loaded to work from the localURL
*/ public Manifest getManifest()
{ try
{ if (manifest ==
null)
{
File file = new
File(localUrl.getFile());
if (file.isDirectory())
manifest= new Manifest(new FileInputStream(new File(file,
"META-INF/MANIFEST.MF")));
else // a
jar
manifest = new
JarFile(file).getManifest();
}
return
manifest;
} // It is ok to barf at any time in
the above, means no manifest catch
(Exception ignored) { return null;}
}
The suggested changesare as
below:
public Manifest getManifest()
{ try
{ if (manifest ==
null)
{
File file = new
File(localUrl.getFile());
if (file.isDirectory())
{
FileInputStream fis = null;
try
{
fis = new FileInputStream(new File(file,
"META-INF/MANIFEST.MF"));
manifest= new
Manifest(fis);
} finally {// close the input
stream
fis.close();
}
} else {// a
jar
JarFile jarFile = new
JarFile(file);
try
{
manifest =
jarFile.getManifest();
} finally { // close the
JarFile
jarFile.close();
}
}
}
return
manifest;
} // It is ok
RE: [JBoss-dev] Re: [jboss-cvs] jboss-transaction/src/main/org/jboss/tm TransactionImpl.java
Ole Husgaard wrote:
+ // Using the construct
+ // try {
+ // txCapsule.doSomething();
+ // } catch (NullPointerException ex) {
+ // throw new IllegalStateException(No transaction.);
+ // }
+ // may look like bad programming style, but it is
needed to avoid to
+ // synchronize on these methods. If we used a construct like
+ // if (txCapsule == null)
+ // throw new IllegalStateException(No transaction.);
+ // txCapsule.doSomething();
+ // we can get spurious NullPointerExceptions when
racing with the
+ // transaction completion.
+
public void commit()
throws RollbackException,
@@ -68,9 +83,11 @@
java.lang.IllegalStateException,
SystemException
{
- if( txCapsule == null )
+ try {
+ txCapsule.commit();
+ } catch (NullPointerException ex) {
throw new IllegalStateException(No transaction.);
- txCapsule.commit();
+ }
Interesting... Is this actually faster then synchronizing? Have you
measured it?
How about:
public void commit()
{
final TxCapsule localTxCapsule = txCapsule ;
if (localTxCapsule == null)
throw new IllegalStateException(No transaction.) ;
localTxCapsule.commit() ;
}
Kev
Kevin Conner
Orchard Information Systems Limited
Newcastle Technopole, Kings Manor
Newcastle Upon Tyne, NE1 6PA. United Kingdom
Registered in England, Number 1900078
Tel: +44 (0) 191-2032536 Fax: +44 (0) 191 2302515
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582965 ] Cluster Member Starvation
Bugs item #582965, was opened at 2002-07-17 11:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582965group_id=22866 Category: Clustering Group: v3.1 Status: Open Resolution: None Priority: 5 Submitted By: Matt Cleveland (groovesoftware) Assigned to: Nobody/Anonymous (nobody) Summary: Cluster Member Starvation Initial Comment: The Round Robin algorithm on home interfaces is causing starvation of some servers in the cluster. In other words, some servers receive no create calls. I am using jboss_3.0.1RC1-tomcat_4.0.4 with Java 1.3.1. The following steps will reproduce the error. - un-jar the attached bug.jar - Create 6 jboss server instances on the same computer. These servers can be the same configuration as 'default'. You will need to change port numbers for each server so that none conflict. - In 5 of the configurations place the attached ejb-cluster-service.xml (it's in the attached bug.jar) file. I call these servers EJB servers. - The 6th server I call the web server. - In all 6 servers place the attached jndi-cluster-service.xml file (it's in the attached bug.jar). You will need to change the port in this file for each server so that there are no conflicts. - un-jar the attached rr.jar (it's in the attached bug.jar). Change the jnp url in rr/resources/war/jnpport/WEB-INF/jboss-web.xml to use the port specified for HA-JNDI on the web server. - run Ant in rr. - copy rr/build/jnpport/jnpport.jar to the deploy directory of the EJB servers. - copy rr/build/jnpport/jnpport.war to the deploy directory of the web server. - start all 6 servers - To test you can use a URL of the form http://server:port/jnpport/hello.jsp?homeCount=1beanCount=1callCount=1 You can change the parameters to change the behavior. The JSP looks up the home interface to an ejb homeCount times. For each home it looks up it creates beanCount beans. For each bean it creates it calls a method callCount times. All the bean does is log some output so that you can see which server handled the call by looking at the log files. I have found the following behavior with this example. - homeCount=50 beanCount=1 callCount=1 All calls go to the same server. This is expected and I do not believe it is a bug because there is no round-robin for HA-JNDI when it resolves a name to the local JNDI on a server. - homeCount=1 beanCount=1 callCount=50 All calls are evenly distrubuted to all EJB servers. - homeCount=1 beanCount=50 callCount=50 Calls are not evenly distrubuted to the EJB servers. 1 or more servers will not receive any calls at all. This is a bug because some of the servers are being left out of the load balancing. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582965group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582965 ] Cluster Member Starvation
Bugs item #582965, was opened at 2002-07-17 11:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582965group_id=22866 Category: Clustering Group: v3.1 Status: Open Resolution: None Priority: 7 Submitted By: Matt Cleveland (groovesoftware) Assigned to: Sacha Labourey (slaboure) Summary: Cluster Member Starvation Initial Comment: The Round Robin algorithm on home interfaces is causing starvation of some servers in the cluster. In other words, some servers receive no create calls. I am using jboss_3.0.1RC1-tomcat_4.0.4 with Java 1.3.1. The following steps will reproduce the error. - un-jar the attached bug.jar - Create 6 jboss server instances on the same computer. These servers can be the same configuration as 'default'. You will need to change port numbers for each server so that none conflict. - In 5 of the configurations place the attached ejb-cluster-service.xml (it's in the attached bug.jar) file. I call these servers EJB servers. - The 6th server I call the web server. - In all 6 servers place the attached jndi-cluster-service.xml file (it's in the attached bug.jar). You will need to change the port in this file for each server so that there are no conflicts. - un-jar the attached rr.jar (it's in the attached bug.jar). Change the jnp url in rr/resources/war/jnpport/WEB-INF/jboss-web.xml to use the port specified for HA-JNDI on the web server. - run Ant in rr. - copy rr/build/jnpport/jnpport.jar to the deploy directory of the EJB servers. - copy rr/build/jnpport/jnpport.war to the deploy directory of the web server. - start all 6 servers - To test you can use a URL of the form http://server:port/jnpport/hello.jsp?homeCount=1beanCount=1callCount=1 You can change the parameters to change the behavior. The JSP looks up the home interface to an ejb homeCount times. For each home it looks up it creates beanCount beans. For each bean it creates it calls a method callCount times. All the bean does is log some output so that you can see which server handled the call by looking at the log files. I have found the following behavior with this example. - homeCount=50 beanCount=1 callCount=1 All calls go to the same server. This is expected and I do not believe it is a bug because there is no round-robin for HA-JNDI when it resolves a name to the local JNDI on a server. - homeCount=1 beanCount=1 callCount=50 All calls are evenly distrubuted to all EJB servers. - homeCount=1 beanCount=50 callCount=50 Calls are not evenly distrubuted to the EJB servers. 1 or more servers will not receive any calls at all. This is a bug because some of the servers are being left out of the load balancing. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582965group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 17-July-2002
Number of tests run: 669
Successful tests: 664
Errors:4
Failures: 1
[time of test: 17 July 2002 12:52 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
[java.vm.version: 1.3.1]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Mac OS X]
[os.arch: ppc]
[os.version: 10.1.5]
See http://lubega.com/testarchive/${build.uid} for details of this test.
See http://lubega.com for general test information.
NOTE: If there are any errors shown above - this mail is only highlighting
them - it is NOT indicating that they are being looked at by anyone.
Remember - if a test becomes broken after your changes - fix it or fix the test!
Oh dear - still got some errors!
Thanks for all your effort - we really do love you!
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-583039 ] service descriptor for SapDB
Patches item #583039, was opened at 2002-07-17 20:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=583039group_id=22866 Category: JBossDoc Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Kurt Stam (jkurt) Assigned to: Nobody/Anonymous (nobody) Summary: service descriptor for SapDB Initial Comment: You may want to add this file to the docs/examples/jca directory. This works for me and it may save others some time. --Kurt -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376687aid=583039group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-583066 ] xml comments in ejb-ql cause error
Bugs item #583066, was opened at 2002-07-17 17:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=583066group_id=22866 Category: JBossCMP Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Jonathan Tobias (javamartini) Assigned to: Nobody/Anonymous (nobody) Summary: xml comments in ejb-ql cause error Initial Comment: Here is a contrived query tag from an entity bean. When I comment out the WHERE clause as you see, it causes the error below on deployment. When I remove this comment, it deploys fine. query query-method method-namefindByUsername/method-name method-params/ /query-method ejb-ql SELECT OBJECT(c) FROM CoreRequest c !-- WHERE c.user.username = x -- /ejb-ql /query 17:06:09,284 ERROR [EjbModule] Starting failed org.jboss.deployment.DeploymentException: Error compiling ejbql; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered null at line 3, column 21. Was expecting one of: EOF , ... ) at org.jboss.ejb.plugins.cmp.jdbc.JDBCEJBQLQuery.init(JDBCEJBQLQuery.java:46) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createEJBQLQuery(JDBCCommandFactory.java:44) at org.jboss.ejb.plugins.cmp.jdbc.JDBCQueryManager.start(JDBCQueryManager.java:214) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:389) at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:198) at org.jboss.ejb.EntityContainer.start(EntityContainer.java:376) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=583066group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-501972 ] Messages can not be resent
Bugs item #501972, was opened at 2002-01-10 11:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=501972group_id=22866 Category: JBossMQ Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Corby (corby) Assigned to: Andreas Schaefer (schaefera) Summary: Messages can not be resent Initial Comment: When a message is received from a queue, if it is placed in another queue, acknowledgement of the message will fail. This occurs in JBoss 2.4.4-Catalina on Windows 2000. The following code fragment replicates the problem. mapMessage is a message that was received from a queue. queueConnection = JMSHelper.getQueueConnection( JMSHelper.NONXA_CONNECTION_FACTORY ); queueSession = JMSHelper.getQueueSession( queueConnection ); queueSender = JMSHelper.getQueueSender( queueSession, JMSHelper.FAILED_ALLOCATIONS_QUEUE ); queueConnection.start(); queueSender.send( mapMessage ); With this code, the message is forwarded into the new queue, but acknowledgement fails. When JBoss is restarted, the message will be delivered. Acknowlegement will succeed when I manually copy the message, like so: queueConnection = JMSHelper.getQueueConnection( JMSHelper.NONXA_CONNECTION_FACTORY ); queueSession = JMSHelper.getQueueSession( queueConnection ); queueSender = JMSHelper.getQueueSender( queueSession, JMSHelper.FAILED_ALLOCATIONS_QUEUE ); // NOTE: I am copying this message because of a bug in the current version // of JBossMQ. In future versions, we should be able to forward the message // without copying it. MapMessage sentMessage = JMSHelper.createMapMessage( queueSession ); sentMessage.setString( ACCOUNTING_LOCATION_NUMBER, mapMessage.getString( ACCOUNTING_LOCATION_NUMBER )); sentMessage.setString( DIRECTION_OF_FLOW, mapMessage.getString( DIRECTION_OF_FLOW )); sentMessage.setLong( BEGIN_PRODUCTION_TIME, mapMessage.getLong( BEGIN_PRODUCTION_TIME )); sentMessage.setLong( END_PRODUCTION_TIME, mapMessage.getLong( END_PRODUCTION_TIME )); queueConnection.start(); queueSender.send( sentMessage ); Peter claimed at the beginning of November that this problem had been fixed in CVS: http://www.jboss.org/forums/thread.jsp? forum=48thread=3789message=254709 However, subsequent build of the system, including the JBoss 2.4.4-Catalina distribution, continue to have this problem. -- Comment By: Christian Riege (lqd) Date: 2002-01-11 03:32 Message: Logged In: YES user_id=176671 pls. see attached patch file which is versus the Branch_2_4 CVS. This is the 2.4 backport of the fix from HEAD. Corby, can you apply the patch and give us feedback of whether this solves your problem? if you don't have JBoss 2.4.4 CVS sources drop me a note and I will send the MQ .jar files. -- Comment By: Peter Antman (pra) Date: 2002-01-11 00:03 Message: Logged In: YES user_id=84651 This was (and is fixed) in the main trunk of JBossMQ (http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jbossmq/src/main/org/jboss/mq/SpyMessage.java.diff?r1=1.3r2=1.4), but has never been backported to the 2.4 version of JBossMQ. Therefore: it works in 3.0, but the 2.4.4 is broken. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=501972group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-519680 ] Exception when unregistering durable su
Bugs item #519680, was opened at 2002-02-18 15:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=519680group_id=22866 Category: JBossMQ Group: v2.4 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Todd Huss (thuss) Assigned to: Andreas Schaefer (schaefera) Summary: Exception when unregistering durable su Initial Comment: When I try to unregister a durable subscription in JBoss 2.4.4.with the following code: topicsubscriber.close(); topicsession.unsubscribe(assignedName); I get the following exception: javax.jms.JMSException: Invalid configuration. at org.jboss.mq.pm.rollinglogged.PersistenceManager.destroyQueue(PersistenceManager.java:233) at org.jboss.mq.server.PersistentQueue.destroy(PersistentQueue.java:29) at org.jboss.mq.server.JMSTopic.destoryDurableSubscription(JMSTopic.java:142) at org.jboss.mq.server.StateManager.setDurableSubscription(StateManager.java:115) at org.jboss.mq.server.JMSServer.destroySubscription(JMSServer.java:471) at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:301) at java.lang.Thread.run(Thread.java:498) Just to make sure it wasn't just something wrong with my code I took the example from the JBoss book: jboss/chap4/ex1/DurableTopicClient.java and then in the stop method I added the two lines to stop the TopicSubscriber and then unregister and it caused the same exception on the server. I suspect there's not a problem with the configuration since it's out of the box JBoss. Thanks, Todd -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 14:38 Message: Logged In: YES user_id=70434 This problem is due to a coding error in JBossMQ PM. The fix is going into release 2.4.7. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=519680group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-520232 ] subscription does not exist exception
Bugs item #520232, was opened at 2002-02-19 15:40 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=520232group_id=22866 Category: JBossMQ Group: None Status: Open Resolution: None Priority: 5 Submitted By: Doug Beeman (dbeeman) Assigned to: Andreas Schaefer (schaefera) Summary: subscription does not exist exception Initial Comment: javax.jms.JMSException: The provided subscription does not exist occurs when (re)registering with a new selector. This is intermittant and happens with the new 2.4.4 build as well. [Default] JBoss 2.5 ALPHA Started in 0m:6s [OILServerILService] The OILClientIL Connection is set up [OILServerILService] The OILClientIL Connection is set up [JMSServer] Server: subscribe(dest=TOPIC.TRAPS,idConnection=ID2) [ClientConsumer:ID2] ClientConsumer:ID2-run() [ClientConsumer:ID2] Adding subscription for: org.jboss.mq.Subscription@409554 [ClientConsumer:ID2] ClientConsumer:ID2-setEnabled(enabled=true) [JMSServer] Server: unsubscribe(idConnection=ID2) [ClientConsumer:ID2] ClientConsumer:ID2-removeSubscription(subscriberId=-2147483648) [ClientConsumer:ID2] ClientConsumer:ID2-setEnabled(enabled=false) [JMSServer] Server: subscribe(dest=TOPIC.TRAPS,idConnection=ID2) [ClientConsumer:ID2] Adding subscription for: org.jboss.mq.Subscription@56f631 [ClientConsumer:ID2] ClientConsumer:ID2-setEnabled(enabled=true) [OILServerILService] Client request resulted in a server exception: javax.jms.JMSException: The provided subscription does not exist at org.jboss.mq.server.ClientConsumer.receive(Unknown Source) at org.jboss.mq.server.JMSServer.receive(Unknown Source) at org.jboss.mq.il.oil.OILServerILService.run(Unknown Source) at java.lang.Thread.run(Thread.java:484) [JMSServer] Server: unsubscribe(idConnection=ID2) [ClientConsumer:ID2] ClientConsumer:ID2-removeSubscription(subscriberId=-2147483647) [ClientConsumer:ID2] ClientConsumer:ID2-setEnabled(enabled=false) [JMSServer] Server: subscribe(dest=TOPIC.TRAPS,idConnection=ID2) [ClientConsumer:ID2] Adding subscription for: org.jboss.mq.Subscription@6c6b00 [OILServerILService] Client request resulted in a server exception: javax.jms.JMSException: The provided subscription does not exist at org.jboss.mq.server.ClientConsumer.receive(Unknown Source) at org.jboss.mq.server.JMSServer.receive(Unknown Source) at org.jboss.mq.il.oil.OILServerILService.run(Unknown Source) at java.lang.Thread.run(Thread.java:484) [ClientConsumer:ID2] ClientConsumer:ID2-setEnabled(enabled=true) [JMSServer] Server: unsubscribe(idConnection=ID2) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=520232group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-526696 ] session.recover() doesn't work
Bugs item #526696, was opened at 2002-03-06 15:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=526696group_id=22866 Category: JBossMQ Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kelly McTiernan (kellymct) Assigned to: Andreas Schaefer (schaefera) Summary: session.recover() doesn't work Initial Comment: All operating systems. Any version of Java. N/A. Call session.recover(). According to the JMS spec, a call to session.recover() from a transacted session should return an IllegalStateException. This it does, with the message: The session is trasacted. When called with a non-transacted session, however, recover still throws an IllegalStateException, this time with the message: The session is not transacted. Looking into the code a little, it turns out that the recover() method does a check for the session being transacted, and throws the IllegalStateException with the second message if it is. Then it proceeds to call rollback(), which does a check for the session NOT being transacted, and throws the IllegalStateException with the second message if it's not. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=526696group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-542365 ] OIL ConnectionFactory Not working
Bugs item #542365, was opened at 2002-04-11 00:09 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=542365group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 9 Submitted By: Peter Luttrell (objec) Assigned to: Andreas Schaefer (schaefera) Summary: OIL ConnectionFactory Not working Initial Comment: I attempted to get the following classes from the example set HelloSubscriber25 and HelloPublisher25 working with JBoss3.0 beta2 (cvs build 2002.04.11 ~12:10am cst), but when I publish the messages, jboss pukes. If I switch the connectionfactory to RMIConnectionFactory, the messages work. Here's the output when it failes: 2002-04-11 01:06:13,841 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [3.0.0beta2 Date:200204110050] Started in 0m:33s:578ms 2002-04-11 01:55:57,482 DEBUG [org.jboss.mq.il.oil.OILClientIL] ConnectionReceiverOILClient is connecting to: 192.168.46.8:55612 2002-04-11 01:55:57,488 ERROR [org.jboss.mq.il.oil.OILClientIL] Cannot connect to the ConnectionReceiver/Server java.net.SocketException: errno: 97, error: Address family not supported by protocol for fd: 28 at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:355) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:142) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:129) at java.net.Socket.init(Socket.java:273) at java.net.Socket.init(Socket.java:127) at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:175) at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156) at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112) at org.jboss.mq.server.JMSServer.ping(JMSServer.java:926) at org.jboss.mq.server.JMSServerInvokerSupport.ping(JMSServerInvokerSupport.java:300) at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:308) at java.lang.Thread.run(Thread.java:484) 2002-04-11 01:55:57,492 WARN [org.jboss.mq.il.oil.OILServerILService] Client request resulted in a server exception: org.jboss.mq.SpyJMSException: Could not pong at org.jboss.mq.server.JMSServer.ping(JMSServer.java:930) at org.jboss.mq.server.JMSServerInvokerSupport.ping(JMSServerInvokerSupport.java:300) at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:308) at java.lang.Thread.run(Thread.java:484) linked exception is: java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:183) at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156) at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112) at org.jboss.mq.server.JMSServer.ping(JMSServer.java:926) at org.jboss.mq.server.JMSServerInvokerSupport.ping(JMSServerInvokerSupport.java:300) at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:308) at java.lang.Thread.run(Thread.java:484) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=542365group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Spec question regaurding MDB...
Does anyone know what the transactional behavior of an MDB with NOT_SUPPORTED will be with respect to the message which it is processing? For example, should the message be ack'd and committed before onMessage() is called, or after as it would if it was REQUIRED. It seems that if it is done after, then there is a tx. which contradicts the NOT_SUPPORTED declaration. Does anyone know how the message tx works when the MDB is bean managed instead of container managed either? Basically I am trying to get an MDB to ack a message mid-way through onMessage() to indicate that the message should not be redelivered, but I need onMessage() to block afterwards to wait for a long lived process to do some work. Anyone had to do this before? I believe this works fine with JBossMQ, but SwiftMQ will hang on the ack. waiting for the tx to commit (which it will never do as the MDB is locked now). MDB really pisses me off. I should just stop using them. but that is entirely too much work at the moment. =( --jason --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-565472 ] Can't access JMS from external app/MBEAN
Bugs item #565472, was opened at 2002-06-06 11:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=565472group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Andreas Schaefer (schaefera) Summary: Can't access JMS from external app/MBEAN Initial Comment: I'm trying to access a queue defined in jboss from an external java-application. I thought that with the default-security-config I just had to insert user/password in jbossmq-state.xml and securityconf in the queue-mbean. I get this error: WARN [OILServerILService] Client request resulted in a server exception: javax.jms.JMSSecurityException: Connection not authorized to subscribe to destination: SMSUt at org.jboss.mq.security.ServerSecurityInterceptor.subscribe(ServerSecurityInterceptor.java:141) at org.jboss.mq.server.TracingInterceptor.subscribe(TracingInterceptor.java:599) at org.jboss.mq.server.JMSServerInvoker.subscribe(JMSServerInvoker.java:298) at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:287) at java.lang.Thread.run(Thread.java:498) Definition of the queue: mbean code=org.jboss.mq.server.jmx.Queue name=jboss.mq.destination:service=Queue,name=SMSUt depends optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends depends optional-attribute-name=SecurityManagerjboss.mq:service=SecurityManager/depends attribute name=SecurityConf security role name=smssender read=false write=true/ role name=smsdispatcher read=true write=true create=true / /security /attribute /mbean Default in login-config.xml: !-- Security domain for JBossMQ -- application-policy name = jbossmq authentication login-module code = org.jboss.mq.sm.file.DynamicLoginModule flag = sufficient module-option name = unauthenticatedIdentityguest/module-option module-option name = sm.objectnamjboss.mq:service=StateManager/module-option /login-module /authentication /application-policy In jbossmq-state.xml: User Nameboost/Name Passwordpassword/Password /User Lookup-code: Object o = ictxt.lookup(ConnectionFactory); connFactory = (QueueConnectionFactory) o; queueConnection = connFactory.createQueueConnection(boost,***password*); The same happens when I try the same from a MBean using INVM connectionfactory. I have no problem publishing messages to the queue from an ordinary session-bean using similar sequrity settings. -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 16:28 Message: Logged In: YES user_id=70434 The problem with the login-config.xml is fixed in 3.0 branch and CVS Head. Andy -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 16:28 Message: Logged In: YES user_id=70434 The problem with the login-config.xml is fixed in 3.0 branch and CVS Head. Andy -- Comment By: Marius Kotsbak (mkotsbak) Date: 2002-06-07 06:53 Message: Logged In: YES user_id=366650 I'm sorry, but I found that the error was because of a mismatch in my role names. But anyway, I think it is a typing-error in login-config.xml (see my last post). It works both when I fix this, and when I don't. -- Comment By: Marius Kotsbak (mkotsbak) Date: 2002-06-07 04:37 Message: Logged In: YES user_id=366650 I think I have found a typing error in the default login-config.xml: module-option name = sm.objectnamjboss.mq:service=StateManager/module-option It should probably be sm.objectname. It is the same in cvs HEAD! Unfortunately, it doesn't seem to solve my problem. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=565472group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-565472 ] Can't access JMS from external app/MBEAN
Bugs item #565472, was opened at 2002-06-06 11:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=565472group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Marius Kotsbak (mkotsbak) Assigned to: Andreas Schaefer (schaefera) Summary: Can't access JMS from external app/MBEAN Initial Comment: I'm trying to access a queue defined in jboss from an external java-application. I thought that with the default-security-config I just had to insert user/password in jbossmq-state.xml and securityconf in the queue-mbean. I get this error: WARN [OILServerILService] Client request resulted in a server exception: javax.jms.JMSSecurityException: Connection not authorized to subscribe to destination: SMSUt at org.jboss.mq.security.ServerSecurityInterceptor.subscribe(ServerSecurityInterceptor.java:141) at org.jboss.mq.server.TracingInterceptor.subscribe(TracingInterceptor.java:599) at org.jboss.mq.server.JMSServerInvoker.subscribe(JMSServerInvoker.java:298) at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:287) at java.lang.Thread.run(Thread.java:498) Definition of the queue: mbean code=org.jboss.mq.server.jmx.Queue name=jboss.mq.destination:service=Queue,name=SMSUt depends optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends depends optional-attribute-name=SecurityManagerjboss.mq:service=SecurityManager/depends attribute name=SecurityConf security role name=smssender read=false write=true/ role name=smsdispatcher read=true write=true create=true / /security /attribute /mbean Default in login-config.xml: !-- Security domain for JBossMQ -- application-policy name = jbossmq authentication login-module code = org.jboss.mq.sm.file.DynamicLoginModule flag = sufficient module-option name = unauthenticatedIdentityguest/module-option module-option name = sm.objectnamjboss.mq:service=StateManager/module-option /login-module /authentication /application-policy In jbossmq-state.xml: User Nameboost/Name Passwordpassword/Password /User Lookup-code: Object o = ictxt.lookup(ConnectionFactory); connFactory = (QueueConnectionFactory) o; queueConnection = connFactory.createQueueConnection(boost,***password*); The same happens when I try the same from a MBean using INVM connectionfactory. I have no problem publishing messages to the queue from an ordinary session-bean using similar sequrity settings. -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 16:28 Message: Logged In: YES user_id=70434 The problem with the login-config.xml is fixed in 3.0 branch and CVS Head. Andy -- Comment By: Marius Kotsbak (mkotsbak) Date: 2002-06-07 06:53 Message: Logged In: YES user_id=366650 I'm sorry, but I found that the error was because of a mismatch in my role names. But anyway, I think it is a typing-error in login-config.xml (see my last post). It works both when I fix this, and when I don't. -- Comment By: Marius Kotsbak (mkotsbak) Date: 2002-06-07 04:37 Message: Logged In: YES user_id=366650 I think I have found a typing error in the default login-config.xml: module-option name = sm.objectnamjboss.mq:service=StateManager/module-option It should probably be sm.objectname. It is the same in cvs HEAD! Unfortunately, it doesn't seem to solve my problem. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=565472group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-580207 ] Message expiration
Bugs item #580207, was opened at 2002-07-11 11:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=580207group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Gary Capps (gary_capps) Assigned to: Andreas Schaefer (schaefera) Summary: Message expiration Initial Comment: When a message with a timeToLive value is generated by one workstation but consumed by different workstation, the message will often be incorrectly considered as expired by the consuming workstation if the two workstations' clocks are not synchronized. The problem appears to be that it is the *client* and not the *server* that calculates the expiration time and determines if that time has been reached. For example, if workstation A places messages in the queue with a 5000ms timeToLiveValue and the messages are consumed by workstation B (whose clock is 1 minute slower than workstation A's), the messages will always be discarded as expired by B. Both the originating time of the message and the determination of expiration should be done by the server, not the client. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=580207group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-580449 ] build failure
Bugs item #580449, was opened at 2002-07-12 00:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=580449group_id=22866 Category: JBossMQ Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Shlomi Hazan (shlomi) Assigned to: Nobody/Anonymous (nobody) Summary: build failure Initial Comment: The build fails complaining about line 769 in the build file, where it attempts to copy jbossmq-service.xml files into the server installation folder. The problem is that these is very easy to fix but later on, yet another copy (line 794) uses the same folder but with a wild-card. I couldn't possibly guess what files are used at runtime, so I guess you guys will have to write a task that actually creates this folder after copilation is done, and copy whatever is expected to be there into it... Hope that helps... [EMAIL PROTECTED] [EMAIL PROTECTED] -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 16:32 Message: Logged In: YES user_id=70434 Which version, what OS, CVS or download. Andy -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=580449group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582005 ] org.jboss.mq.pm.rollinglogged
Bugs item #582005, was opened at 2002-07-15 16:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582005group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Elias Ross (genman) Assigned to: Andreas Schaefer (schaefera) Summary: org.jboss.mq.pm.rollinglogged Initial Comment: According to the documentation regarding rollinglogged PM: http://www.jboss.org/online-manual/HTML/ch06s07.html I should be able to run the rollinglogged PM: !-- The PersistenceManager is used to store messages to disk. -- mbean code=org.jboss.mq.pm.rollinglogged.PersistenceManager name=jboss.mq:service=PersistenceManager attribute name=DataDirectory/tmp/db/jbossmq/file/attribute depends optional-attribute-name=MessageCachejboss.mq:service=MessageCache/depends /mbean However, it fails: 16:45:36,151 INFO [PersistenceManager] Starting 16:45:36,159 ERROR [PersistenceManager] Starting failed ReflectionException: null Cause: java.lang.NoSuchMethodException: Unable to locate method for: getInstance() at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:288) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.mq.pm.rollinglogged.PersistenceManager.startService(PersistenceManager.java:268) Apparently, the getInstance method now takes no parameters: Changes (not tested): messageCache = (MessageCache) getServer().getAttribute(messageCacheName, Instance); /* messageCache = (MessageCache) getServer().invoke(messageCacheName, getInstance, new Object[0], new String[0]); */ -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582005group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582011 ] Specifying cache relative to root direct
Bugs item #582011, was opened at 2002-07-15 17:01 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582011group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Elias Ross (genman) Assigned to: Andreas Schaefer (schaefera) Summary: Specifying cache relative to root direct Initial Comment: If I specify a cache directory, such as /tmp/jbossmq, the cache used is not /tmp, but actually the cache it tries to write arrives underneath $JBOSS/.../tmp mbean code=org.jboss.mq.pm.file.CacheStore name=jboss.mq:service=CacheStore attribute name=DataDirectory/tmp/jbossmq/attribute /mbean For read-only filesystems and the like, this is undesirable. The work-around requires being able to create symbolic links. -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 16:36 Message: Logged In: YES user_id=70434 I suggest the following fix: - a path starting with file: is treated as absult path and a valid URL representation must be inserted - all other are treated relative Andy -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582011group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-583139 ] clustering issue with Linux and Windows
Bugs item #583139, was opened at 2002-07-17 16:36 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=583139group_id=22866 Category: Clustering Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Ulrich Romahn (diggermaus) Assigned to: Nobody/Anonymous (nobody) Summary: clustering issue with Linux and Windows Initial Comment: When starting an instance of JBoss 3.0.0 on either Linux or Win2k, it does not joind the default cluster partition of another JBoss 3.0.0 instance that has already been started on another Linux server. It works, however, between two JBoss instances started on two Windows boxes (Win2k and/or WinME). My test configuration was: SuSE Linux 7.3 (with latest patches) Windows 2000 Server SP2 Windows ME (with latest patches) LAN with multicast enabled (verified!) Sun JDK1.3.1_03 on Linux Sun JDK1.4.0 and 1.3.1_02 on Windows (both tested) How to reproduce: Start one JBoss instance on a SuSE 7.3 Start a second JBoss instance on either Win2k or another SuSE 7.3 Identified issue: 1. There must be an issue with the javagroups-2.0.jar that is bundeled with the current JBoss3.0.0 download package from May 31st. If I get the latest javagroups source from CVS, compile it and replace the 'old' jar with the newly compiled, everything seems to be OK and working in any configuration/combination ... except, 2. when running on Linux, a paramter bind_addr should be used to use 'eth0' instead of 'lo' in my case. When I initially installed Linux, I didn't have an active network connection. In this case, only 'lo' got activated on Linux and this will be the first network interface. Now, javagroups seems to always try to bind to this 'first' interface, 'lo' in my case. As a result, no multicast were send to the network :(. So, I added the following parameters to my 'cluster-service.xml' to make it work: mbean code=org.jboss.ha.framework.server.ClusterPartition name=jboss:service=DefaultPartition attribute name=PartitionProperties UDP(mcast_addr=228.8.8.8;mcast_port=45566;bind_addr=ip-addr-of-your-if;ip_ttl=32;mcast_send_buf_size=32000;mcast_recv_buf_size=64000):PING(timeout=2000;num_initial_members=3):MERGE2(min_interval=5000;max_interval=1):FD:VERIFY_SUSPECT(timeout=1500):pbcast.STABLE(desired_avg_gossip=2):pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800):UNICAST(timeout=1200):FRAG(down_thread=false;up_thread=false):pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;shun=false;print_local_addr=true) /attribute /mbean Please note that these are the exact default protocol parameters as given in JBoss' ClusterPartition.java, except for the additional paramter 'bind_addr='. After making these changes, everything works, i.e. two JBoss instances on the same LAN join the cluster, regardless of OS and JDK version. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=583139group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-583152 ] Wrong base for MANIFEST classpath
Bugs item #583152, was opened at 2002-07-17 20:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=583152group_id=22866 Category: JBossServer Group: v3.1 Status: Open Resolution: None Priority: 5 Submitted By: David Bergman (davber) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong base for MANIFEST classpath Initial Comment: I know that the class loading works even though the manifest dependencies (via Class-Path) are not handled correctly (and you get WARNings). But (don't hate me now): would it not be nice to have MainDeployer look in the right place, by treating JARs in the Class-Path the same way as directories, thereby getting correct deployment behavior. The diff to get that proper behavior is diff -r1.41 MainDeployer.java 897c897 File parentDir = new File (sdi.localUrl.getPath()+-contents); --- File parentDir = new File (sdi.localUrl.getPath() + -contents).getParentFile(); A full description of this bug (yes, I know it is not crucial right now...) follows. When deploying modules in an EAR with MANIFEST- relations between modules and utility libraries, the utility libraries are searched for in the module JAR, instead of at the application root, which is the correct behavior. The manifest file looks like this: Manifest-Version: 1.0 Class-Path: BarTools.jar My EAR, FooApp.ear, has the following structure: FooApp.ear META-INF application.xml FooEJB.jar META-INF MANIFEST.MF this is the manifest file above org foo UsefulEJB.class ... other working EJB stuff ... BarTools.jar org toolmaker NiftyTool.class ... other cool tools ... I get the following output when deploying the application: 19:08:40,764 INFO [EARDeployer] Init J2EE application: file:/C:/lang/java/jboss /build/output/jboss- 3.1.0alpha/server/default/deploy/FooBar.ear 19:08:41,755 INFO [EJBDeployer] looking for nested deployments in : file:/C:/la ng/java/jboss/build/output/jboss- 3.1.0alpha/server/FooBatr/tmp/deploy/server/FooApp/dep loy/FooApp.ear/75.FooApp.ear/FooEJB.jar 19:08:41,775 WARN [MainDeployer] The manifest entry in file:/C:/lang/java/jboss/build/output/jboss- 3.1.0alpha/server/FooApp/tmp/deploy/server/FooApp/depl oy/FooApp.ear/75.FooApp.ear-contents/FooEJB.jar references URL file:/C:/lang/java/jboss/build/output/jboss- 3.1.0alpha/server/FooApp/tmp/deploy/server/FooApp/depl oy/FooApp.ear/75.FooApp.ear-contents/FooEJB.jar- contents/BarTools.jar which could not be opened, entry ignored The solution: treat directory and JAR equal in MainDeployer, so that the parent directory of the module is used as the base for the relative URLs in the manifest file. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=583152group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss org.jboss.Shutdown does not work
= ==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS= = JAVA VERSION DETAILS java version 1.3.1_03 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) Java HotSpot(TM) Server VM (build 1.3.1_03-b03, mixed mode) = HERE ARE THE LAST 50 LINES OF THE LOG FILE Hello, The org.jboss.Shutdown class does not seem to work. That is, the jboss_redhat_init.sh script called it and the jboss server did not stop... Please could we get this fixed... Or tell me what I should be calling to get the server shutdown... Now I will return to the old faithful method - kill -9 See ya, Chris PS This is automated - just to make it really annoying... --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582011 ] Specifying cache relative to root direct
Bugs item #582011, was opened at 2002-07-15 17:01 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582011group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Elias Ross (genman) Assigned to: Andreas Schaefer (schaefera) Summary: Specifying cache relative to root direct Initial Comment: If I specify a cache directory, such as /tmp/jbossmq, the cache used is not /tmp, but actually the cache it tries to write arrives underneath $JBOSS/.../tmp mbean code=org.jboss.mq.pm.file.CacheStore name=jboss.mq:service=CacheStore attribute name=DataDirectory/tmp/jbossmq/attribute /mbean For read-only filesystems and the like, this is undesirable. The work-around requires being able to create symbolic links. -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 19:26 Message: Logged In: YES user_id=70434 I suggest the following fix: - a path starting with file: is treated as absult path and a valid URL representation must be inserted - all other are treated relative Andy -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 16:36 Message: Logged In: YES user_id=70434 I suggest the following fix: - a path starting with file: is treated as absult path and a valid URL representation must be inserted - all other are treated relative Andy -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582011group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582011 ] Specifying cache relative to root direct
Bugs item #582011, was opened at 2002-07-15 17:01 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582011group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Elias Ross (genman) Assigned to: Andreas Schaefer (schaefera) Summary: Specifying cache relative to root direct Initial Comment: If I specify a cache directory, such as /tmp/jbossmq, the cache used is not /tmp, but actually the cache it tries to write arrives underneath $JBOSS/.../tmp mbean code=org.jboss.mq.pm.file.CacheStore name=jboss.mq:service=CacheStore attribute name=DataDirectory/tmp/jbossmq/attribute /mbean For read-only filesystems and the like, this is undesirable. The work-around requires being able to create symbolic links. -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 19:26 Message: Logged In: YES user_id=70434 Fixed as suggested. Andy -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 19:26 Message: Logged In: YES user_id=70434 I suggest the following fix: - a path starting with file: is treated as absult path and a valid URL representation must be inserted - all other are treated relative Andy -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 16:36 Message: Logged In: YES user_id=70434 I suggest the following fix: - a path starting with file: is treated as absult path and a valid URL representation must be inserted - all other are treated relative Andy -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582011group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-582005 ] org.jboss.mq.pm.rollinglogged
Bugs item #582005, was opened at 2002-07-15 16:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582005group_id=22866 Category: JBossMQ Group: v3.0 Rabbit Hole Status: Closed Resolution: Fixed Priority: 5 Submitted By: Elias Ross (genman) Assigned to: Andreas Schaefer (schaefera) Summary: org.jboss.mq.pm.rollinglogged Initial Comment: According to the documentation regarding rollinglogged PM: http://www.jboss.org/online-manual/HTML/ch06s07.html I should be able to run the rollinglogged PM: !-- The PersistenceManager is used to store messages to disk. -- mbean code=org.jboss.mq.pm.rollinglogged.PersistenceManager name=jboss.mq:service=PersistenceManager attribute name=DataDirectory/tmp/db/jbossmq/file/attribute depends optional-attribute-name=MessageCachejboss.mq:service=MessageCache/depends /mbean However, it fails: 16:45:36,151 INFO [PersistenceManager] Starting 16:45:36,159 ERROR [PersistenceManager] Starting failed ReflectionException: null Cause: java.lang.NoSuchMethodException: Unable to locate method for: getInstance() at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:288) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.mq.pm.rollinglogged.PersistenceManager.startService(PersistenceManager.java:268) Apparently, the getInstance method now takes no parameters: Changes (not tested): messageCache = (MessageCache) getServer().getAttribute(messageCacheName, Instance); /* messageCache = (MessageCache) getServer().invoke(messageCacheName, getInstance, new Object[0], new String[0]); */ -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-17 19:27 Message: Logged In: YES user_id=70434 Fixed as suggested. Andy -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=582005group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-580449 ] build failure
Bugs item #580449, was opened at 2002-07-12 10:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=580449group_id=22866 Category: JBossMQ Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: Shlomi Hazan (shlomi) Assigned to: Nobody/Anonymous (nobody) Summary: build failure Initial Comment: The build fails complaining about line 769 in the build file, where it attempts to copy jbossmq-service.xml files into the server installation folder. The problem is that these is very easy to fix but later on, yet another copy (line 794) uses the same folder but with a wild-card. I couldn't possibly guess what files are used at runtime, so I guess you guys will have to write a task that actually creates this folder after copilation is done, and copy whatever is expected to be there into it... Hope that helps... [EMAIL PROTECTED] [EMAIL PROTECTED] -- Comment By: Shlomi Hazan (shlomi) Date: 2002-07-18 08:04 Message: Logged In: YES user_id=137544 The error referes to jbossmq-1.0.0Beta. Ver=JBossMQ 0.8 ; OS=Win2K ; JRE=1.4.0_01. -- Comment By: Andreas Schaefer (schaefera) Date: 2002-07-18 02:32 Message: Logged In: YES user_id=70434 Which version, what OS, CVS or download. Andy -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=580449group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss(Branch_3_0) Testsuite Results: 17-July-2002
Number of tests run: 660
Successful tests: 653
Errors:6
Failures: 1
[time of test: 17 July 2002 22:42 GMT]
[java.version: 1.3.1]
[java.vendor: Apple Computer, Inc.]
[java.vm.version: 1.3.1]
[java.vm.name: Java HotSpot(TM) Client VM]
[java.vm.info: mixed mode]
[os.name: Mac OS X]
[os.arch: ppc]
[os.version: 10.1.5]
See http://lubega.com/testarchive/${build.uid} for details of this test.
See http://lubega.com for general test information.
NOTE: If there are any errors shown above - this mail is only highlighting
them - it is NOT indicating that they are being looked at by anyone.
Remember - if a test becomes broken after your changes - fix it or fix the test!
Oh dear - still got some errors!
Thanks for all your effort - we really do love you!
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
