Howdy all
Im running JBoss 3.0.2.
I seem to have an issue with doing JMS connections and sends from
internal EJBs back onto local Queues. It works correctly but seems to
be accumulating a large number of running threads of the "OIL Worker"
and OILClientILService. In turn I get a large number o
M -0800, Sundaram Ramasamy wrote:
> > Today I visited jboss.org web site, it looks different (with php . I don't know
>much about php.
> >
> > Is there any advantage in PHP compare to JSP?
> >
> > Thanks
> >
> > -SR
> >
--
Brian Towle
On Wed, 2002-10-23 at 17:59, David Jencks wrote:
> On 2002.10.23 18:15:32 -0400 Brian Towles wrote:
> > OK i found it looks like the MessageCache only needs a reference to
> > the CacheStore name and when its running its startService (in this case
> > at least) it do
Cache.
So the config of the MessageCache Mbean only has to have an attribute
pointing to the PMs name and not a depend in this case.
kinda funky
thx all
-=Brian
On Wed, 2002-10-23 at 16:32, Brian Towles wrote:
> The basic issue is the JDBC2 PersistenceManager then.
>
> They way it is
would need a MessageCache as well.
So the question changes to how do you use the CacheStore in the jdbc2
PersistenceManager and the jdbc2 PersistenceManager?
Thanks
-=Brian
On Wed, 2002-10-23 at 15:30, David Jencks wrote:
> On 2002.10.23 16:22:12 -0400 Brian Towles wrote:
> >
Howdy all
Using JBoss 3.0.2
Im trying to setup a jdbc2 persistence for MQ where both the
MessageCache uses the PersistenceManager for storage of the cache.
There is an example config file in the source code under
messaging/src/etc/server/examples/deploy but on implementation there
message cach
wrote:
> What do you mean by "It doesn't work"? and "It fails"?
>
> > -Message d'origine-
> > De : [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]De la part de Brian
> > Towles
> > Envoyé : samedi, 28 septembre 2002 18:44
&g
Howdy all
I having an issue using ExternalContext to point to a a HAJNDI instance
on a separate cluster of jboss machines.
I have JBoss to JBoss communication working fine with tyrex on an
instance to instance basis. And I have ExternalContext working fine
when I point it to the normal JNDI p
Nevermind
Something not right at layer 2 on the switches. Setup layer 3 for it
and it works fine
Time to smack Cisco around some
-=Brian
On Sun, 2002-09-22 at 11:01, Brian Towles wrote:
> Howdy all
>
> I seem to be having an issue getting two jboss instances to cluster.
>
Howdy all
I seem to be having an issue getting two jboss instances to cluster.
I have the pay docs and have found my way around the missing stuff =)
Clustering is coming up on each instance and both instances think they
are the only one in the group.
I have used the javagroups test program
:
> Brian Towles,
> How do you have this working? What are you doing differently than everyone
> else that allows your session bean to call another bean on another server?
>
> I get a Caused by: java.io.NotSerializableException:
> tyrex.tm.impl.TransactionImpl
>
> Also see
Do you have a sample of this type of MBean
or actually more importantly a sample of how to access the MBean from
and EJB?
Thanks
-=Brian
On Thu, 2002-09-12 at 08:13, Herve Tchepannou wrote:
> In my application, I also have some application properties store in a
> property file.
> I prefer c
Howdy all
I am getting this same error now as well.
I can swear I actually had this working at some point but it is not
working even after a clean instance of jboss is used and a small test is
run.
According to the Tyrex Docs for 1.0 TransactionImpl is not Serializable.
Using 3.0.1 built from
an,
>
> I am interested in the patches. Could you send them?
>
> - Matt
>
> -----Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Brian Towles
> Sent: Friday, August 30, 2002 2:56 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBo
Howdy all
Im looking to implement a MDB that has a selector based on how long a
message has been in the queue ( (NOW - JMSTimestamp) > 2000 ) or
something like that..
I know the selector syntax is limited but is there any keyword for
something like the current timestamp (ie NOW)?
Thanks
-=B
I have done an Axis Beta3 Integration but have not had time to change
all the test case stuff in jboss.net yet so i have not submitted it back
yet.
If there is interest in the patches i will make them available. It has
been working for me just fine.
-=Brian
On Fri, 2002-08-30 at 12:54, Da
Nevermind I forgot about Tyrex
Knew I was doing something stupid.
-=Brian
On Tue, 2002-08-27 at 00:00, Brian Towles wrote:
> Howdy all
>
> I have been trying to implement some cross server EJB calling between
> two Jboss instances (3.0.1) and hit some MarshalExceptions caus
Howdy all
I have been trying to implement some cross server EJB calling between
two Jboss instances (3.0.1) and hit some MarshalExceptions caused by
Not Serializable TransactionImpl, TxCapsule and
TimeoutFactory$TimeoutImpl so far.
I thought at first it was just missing a Serializable interf
Howdy
I know the currently Jboss3 uses a modified Axis beta1 for the jboss.net
stuff.
Has anyone successfully used Axis beta3 at all for inbound calls to hit
EJB functions? And if you have how?
Have to used gSoap generated clients hitting my services and Axis beta3
is the best for interactio
erence between the ear the works and this one? The latest
> manifest loading fixes are available in the 3.0 branch so you can try that
> or the 3.0.1 release due out Monday.
>
> - Original Message -----
> From: "Brian Towles" <[EMAIL PROTECTED]>
> To: <[EMAIL
Howdy all
I am having an issue deploying an ear file and having the Manifest
Class-Path followed.
the ear consists of and ejb file and supporting files..
junction.ear
junction-ejb.jar
junction-server.jar
junction-client.jar
junction-common.jar
The Manifest class
Howdy All
Im trying to deploy an MDB to a JBoss 3.0 instance and am getting the
following Security issue. I think I have everything wide open on the
Queue and the exception seems to indicate that its something with the
creation of the DLQ.
Ive tried various roles in the method permissions for t
22 matches
Mail list logo