Re: [JBoss-user] Re: CMP Debug SQL Statements (JAWS)

2001-07-29 Thread Nicolai P Guba

Try this instead.  Note where the debug tag is now.

jaws
  datasourceAdsDB/datasource
  type-mappingOracle8/type-mapping
  debugtrue/debug
  default-entity
create-tabletrue/create-table
remove-tablefalse/remove-table
read-onlyfalse/read-only
select-for-updatefalse/select-for-update
  /default-entity
--
  Nicolai P Gubahttp://www.gnu.org http://www.frontwire.com
mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
GSM: +44 (0)7909 960 751   DDI: +44 (0)20 7368 9708

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



[JBoss-user] MBean NameAlreadyBoundException

2001-07-29 Thread Frederick N. Brier

The second time a server comes up the console is showing 
NameAlreadyBoundException(s) when an MBean name in its JNDI bind() 
call.  Now unbind() is called within the stopService() method, but my log 
message never shows that the stopService() method is ever called.   The 
MBean extends org.jboss.util.ServiceMBeanSupport.  Now I could catch the 
NameAlreadyBoundException and try to rebind() it, but that seems like a 
hack or a preventative measure.  What do I need to do to get the 
stopService method to be called?

Lastly, is there an easy way to clear all the names out of the JBoss JNDI 
namespace, such as editing a flat text file,  or deleting a binary file 
sitting in a JBoss directory?


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] MBean NameAlreadyBoundException

2001-07-29 Thread David Jencks

I'm highly confused by trying to guess what you might be doing.  What
configuration are you running? What do you mean by the second time a
server comes up?  Are you running any non-jboss mbean servers or jndis? 
My impression was that jboss jndi was 100% non persistent, when you stop
your jboss instance everything goes away, and this is what I observe.

Have you written your own mbean? How do you deploy it?

What exactly is your configuration, what you are doing, and the result you
don't like?

david jencks

On 2001.07.29 11:07:17 -0400 Frederick N. Brier wrote:
 The second time a server comes up the console is showing 
 NameAlreadyBoundException(s) when an MBean name in its JNDI bind() 
 call.  Now unbind() is called within the stopService() method, but my log
 
 message never shows that the stopService() method is ever called.   The 
 MBean extends org.jboss.util.ServiceMBeanSupport.  Now I could catch the 
 NameAlreadyBoundException and try to rebind() it, but that seems like a 
 hack or a preventative measure.  What do I need to do to get the 
 stopService method to be called?
 
 Lastly, is there an easy way to clear all the names out of the JBoss JNDI
 
 namespace, such as editing a flat text file,  or deleting a binary file 
 sitting in a JBoss directory?
 
 
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user
 
 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] Calling CORBA objects from JBoss

2001-07-29 Thread gerardo macari
 
 Dave Ortman [EMAIL PROTECTED] wrote: 
Hi,I recently posted an inquiry regarding the utilization of CORBA objects fromwithin EJB's deployed in JBoss. Basically, I was unable to have a session beanmake a call to a CORBA object. Since then, we have deployed the same bean toWebLogic, and it worked fine.So, the issue is not EJB specific. I looked at the FAQ, and saw that JBossdoes not support RMI/IIOP. However, I didn't think this would prevent my sessionbeans from making CORBA calls.Is there a limitation of JBoss which would make calling CORBA objects impossible?Thanks,-Dave___JBoss-user mailing list[EMAIL PROTECTED]http://lists.sourceforge.net/lists/listinfo/jboss-user


Hi Dave,

I need to do the same thing (call a Corba Object). I think since JBOSS does not support RMI-IIOP, it does not have the ability
to change the JRMP to an IIOP call, so the receiving ORB who is expecting only calls via IIOP ignores it (if it gets there at all).
PS: Don't quote me on this, but I think thats what happens (WebLogic states it DOES support RMI-IIOP as you said)

GerardoGerardo MacariDo You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messengerhttp://phonecard.yahoo.com/

RE: [JBoss-user] MBean NameAlreadyBoundException

2001-07-29 Thread Jim Brownfield

This is probably not relavent, but I thought I'd throw it in.

I had a similar problem, and it turned out to be that somehow my MBean ended
up being put into jboss-auto.jcml twice without me knowing it.  What was
happening was two of my MBeans were trying to start at the same time, and
the second instance was getting the NameAlreadyBoundExceptionss.  I just
deleted the jboss-auto.jcml.  I was never able to reproduce the
circumstances causing the double entries, but I've seen it at least twice.

Probably not your problem, but FYI...

Jim

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Frederick N.
 Brier
 Sent: Sunday, July 29, 2001 8:07 AM
 To: [EMAIL PROTECTED]
 Subject: [JBoss-user] MBean NameAlreadyBoundException


 The second time a server comes up the console is showing
 NameAlreadyBoundException(s) when an MBean name in its JNDI bind()
 call.  Now unbind() is called within the stopService() method, but my log
 message never shows that the stopService() method is ever called.   The
 MBean extends org.jboss.util.ServiceMBeanSupport.  Now I could catch the
 NameAlreadyBoundException and try to rebind() it, but that seems like a
 hack or a preventative measure.  What do I need to do to get the
 stopService method to be called?

 Lastly, is there an easy way to clear all the names out of the JBoss JNDI
 namespace, such as editing a flat text file,  or deleting a binary file
 sitting in a JBoss directory?


 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] MBean NameAlreadyBoundException

2001-07-29 Thread David Jencks

Yes, if you are running a jboss version that reads jboss-auto.jcml, delete
it (jboss-auto) frequently.

This could perhaps cause apparent persistence of jndi bindings also.

david jencks

On 2001.07.29 14:15:13 -0400 Jim Brownfield wrote:
 This is probably not relavent, but I thought I'd throw it in.
 
 I had a similar problem, and it turned out to be that somehow my MBean
 ended
 up being put into jboss-auto.jcml twice without me knowing it.  What was
 happening was two of my MBeans were trying to start at the same time, and
 the second instance was getting the NameAlreadyBoundExceptionss.  I
 just
 deleted the jboss-auto.jcml.  I was never able to reproduce the
 circumstances causing the double entries, but I've seen it at least
 twice.
 
 Probably not your problem, but FYI...
 
 Jim
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Frederick
 N.
  Brier
  Sent: Sunday, July 29, 2001 8:07 AM
  To: [EMAIL PROTECTED]
  Subject: [JBoss-user] MBean NameAlreadyBoundException
 
 
  The second time a server comes up the console is showing
  NameAlreadyBoundException(s) when an MBean name in its JNDI bind()
  call.  Now unbind() is called within the stopService() method, but my
 log
  message never shows that the stopService() method is ever called.   The
  MBean extends org.jboss.util.ServiceMBeanSupport.  Now I could catch
 the
  NameAlreadyBoundException and try to rebind() it, but that seems like a
  hack or a preventative measure.  What do I need to do to get the
  stopService method to be called?
 
  Lastly, is there an easy way to clear all the names out of the JBoss
 JNDI
  namespace, such as editing a flat text file,  or deleting a binary file
  sitting in a JBoss directory?
 
 
  ___
  JBoss-user mailing list
  [EMAIL PROTECTED]
  http://lists.sourceforge.net/lists/listinfo/jboss-user
 
 
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user
 
 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] Stateful Session Bean declaration

2001-07-29 Thread Toby Hede

from ejb-jar.xml:

enterprise-beans
  session
 descriptionEJBDoclet tags:/description
 ejb-nameubik/Account/ejb-name
 homeubik.account.interfaces.IAccountHome/home
 remoteubik.account.interfaces.IAccount/remote
 ejb-classubik.account.ejb.Account/ejb-class
 session-typeStateful/session-type
 transaction-typeContainer/transaction-type
  /session
/enterprise-beans


from jboss.xml:
   enterprise-beans
  session
 ejb-nameubik/Account/ejb-name
 jndi-nameubik/Account/jndi-name
   container-configurationStandard Stateful
SessionBean/container-configuration
  /session
   /enterprise-beans


where 'Standard Stateful SessionBean' is defined (i rip this straight from
the standardjboss.xml file in the INSTALL_PATH/jboss/conf directory).


If this is still not working, can you provide the code for how you re-invoke
the session bean? Are you using the ejbHandle to store the Session
reference?


/t
toby hede





- Original Message -
From: Anthony IVETAC [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, July 28, 2001 1:41 AM
Subject: [JBoss-user] Stateful Session Bean declaration


 I'm stuck.

 I can't figure out how to correctly declare a statfeul session bean in the
 ejb-jar.xml file!!!

 The bean works, except it's attributes aren't being stored in between
method
 invocations.

 Does anyone have a snippet of EJB-JAR.xml for a stateful session bean,
please?

 BTW - where are stateful session beans passivated to, the default
datasource?


 Thanks very much!


 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user



___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] MBean NameAlreadyBoundException

2001-07-29 Thread Frederick N. Brier

Jim, David, thank you.  I think you are both correct about the 
jboss-auto.jcml file.  Delete it and no duplicate messages.  I guess I 
should probably put the rebind in there in case the server gets restarted 
and the jboss-auto.jcml file has still references.

My configuration is JBoss 2.2.1 with Tomcat 3.2.1 in a single Sun 1.3.1 JVM 
running on Redhat Linux 7.0.  Only one JVM runs at any given time.  My 
reference was to Ctrl-C'ing the server, and then restarting it a second 
time.  Although I haven't gotten to the point where I am integrating JSPs 
and Servlets, I do have Apache set up as the httpd server with mod_jserv.

I've written 3 MBean(s) so far.  Ant builds their code in a jar and I then 
copy it into jboss/lib/ext (haven't tried to make ant do that yet), and 
make the appropriate entries in jboss.jcml.  Two of the MBean(s) are single 
instance and the last has multiple instances and entries in the jboss.jcml 
file.  I haven't fully tested them yet.  All the instances load without 
error, and appear to do what they are supposed to in startService().  Is 
this what you were asking?  Am I doing anything wrong?

I'm just learning all this EJB/JMX/JNDI/Castor(XML and JDO) and figuring 
out how all the pieces play with each other.  I've created 4 entity beans 
that are supported by the MBean(s).  Those also need to be tested.  I'd 
like to see my stopService log.debug() message (other debug messages are 
being displayed).

So far so good.  Thank you again.

Frederick N. Brier

At 12:53 PM 7/29/2001, you wrote:
I'm highly confused by trying to guess what you might be doing.  What
configuration are you running? What do you mean by the second time a
server comes up?  Are you running any non-jboss mbean servers or jndis?
My impression was that jboss jndi was 100% non persistent, when you stop
your jboss instance everything goes away, and this is what I observe.

Have you written your own mbean? How do you deploy it?

What exactly is your configuration, what you are doing, and the result you
don't like?

david jencks

On 2001.07.29 11:07:17 -0400 Frederick N. Brier wrote:
  The second time a server comes up the console is showing
  NameAlreadyBoundException(s) when an MBean name in its JNDI bind()
  call.  Now unbind() is called within the stopService() method, but my log
 
  message never shows that the stopService() method is ever called.   The
  MBean extends org.jboss.util.ServiceMBeanSupport.  Now I could catch the
  NameAlreadyBoundException and try to rebind() it, but that seems like a
  hack or a preventative measure.  What do I need to do to get the
  stopService method to be called?
 
  Lastly, is there an easy way to clear all the names out of the JBoss JNDI
 
  namespace, such as editing a flat text file,  or deleting a binary file
  sitting in a JBoss directory?
 
 
  ___
  JBoss-user mailing list
  [EMAIL PROTECTED]
  http://lists.sourceforge.net/lists/listinfo/jboss-user
 
 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] MBean NameAlreadyBoundException

2001-07-29 Thread David Jencks

Hi,

Glad it worked.

If you want to see an example of a junit test for mbean functionality, see
jbosstest/src/main/org/jboss/test/jmx/test/ConnectionFactoryTest.java.

There is something odd going on if your stopService method isn't logging
properly.  I'd try throwing an exception or something to make sure it isn't
being called, and find out why.  When I have problems like that it usually
turns out I made a typo or capitalization mistake.

Out of curiousity, what is the relationship between the ejbs and the
mbeans?

Thanks
david jencks

On 2001.07.29 19:34:26 -0400 Frederick N. Brier wrote:
 Jim, David, thank you.  I think you are both correct about the 
 jboss-auto.jcml file.  Delete it and no duplicate messages.  I guess I 
 should probably put the rebind in there in case the server gets restarted
 
 and the jboss-auto.jcml file has still references.
 
 My configuration is JBoss 2.2.1 with Tomcat 3.2.1 in a single Sun 1.3.1
 JVM 
 running on Redhat Linux 7.0.  Only one JVM runs at any given time.  My 
 reference was to Ctrl-C'ing the server, and then restarting it a second 
 time.  Although I haven't gotten to the point where I am integrating
 JSPs 
 and Servlets, I do have Apache set up as the httpd server with mod_jserv.
 
 I've written 3 MBean(s) so far.  Ant builds their code in a jar and I
 then 
 copy it into jboss/lib/ext (haven't tried to make ant do that yet), and 
 make the appropriate entries in jboss.jcml.  Two of the MBean(s) are
 single 
 instance and the last has multiple instances and entries in the
 jboss.jcml 
 file.  I haven't fully tested them yet.  All the instances load without 
 error, and appear to do what they are supposed to in startService().  Is 
 this what you were asking?  Am I doing anything wrong?
 
 I'm just learning all this EJB/JMX/JNDI/Castor(XML and JDO) and figuring 
 out how all the pieces play with each other.  I've created 4 entity beans
 
 that are supported by the MBean(s).  Those also need to be tested.  I'd 
 like to see my stopService log.debug() message (other debug messages are 
 being displayed).
 
 So far so good.  Thank you again.
 
 Frederick N. Brier
 
 At 12:53 PM 7/29/2001, you wrote:
 I'm highly confused by trying to guess what you might be doing.  What
 configuration are you running? What do you mean by the second time a
 server comes up?  Are you running any non-jboss mbean servers or jndis?
 My impression was that jboss jndi was 100% non persistent, when you stop
 your jboss instance everything goes away, and this is what I observe.
 
 Have you written your own mbean? How do you deploy it?
 
 What exactly is your configuration, what you are doing, and the result
 you
 don't like?
 
 david jencks
 
 On 2001.07.29 11:07:17 -0400 Frederick N. Brier wrote:
   The second time a server comes up the console is showing
   NameAlreadyBoundException(s) when an MBean name in its JNDI bind()
   call.  Now unbind() is called within the stopService() method, but my
 log
  
   message never shows that the stopService() method is ever called.  
 The
   MBean extends org.jboss.util.ServiceMBeanSupport.  Now I could catch
 the
   NameAlreadyBoundException and try to rebind() it, but that seems like
 a
   hack or a preventative measure.  What do I need to do to get the
   stopService method to be called?
  
   Lastly, is there an easy way to clear all the names out of the JBoss
 JNDI
  
   namespace, such as editing a flat text file,  or deleting a binary
 file
   sitting in a JBoss directory?
  
  
   ___
   JBoss-user mailing list
   [EMAIL PROTECTED]
   http://lists.sourceforge.net/lists/listinfo/jboss-user
  
  
 
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user
 
 
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user
 
 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user