On Wednesday, October 1, 2003, at 11:36 PM, Milen Dyankov wrote:
Matthew Hixson wrote:
Sorry, I should have said JBossQL rather than EJB-QL. If you're not
using xdoclet you can specify a JBossQL query in jbosscmp-jdbc.xml
like so:
findAll
hi,
some weeks ago I asked about JBoss clustering. Now we starting implemnet
our new projekt. We use stateless session beans and entity beans (Commit
Option B). This are beans which aren't synchronized in an cluster. At the
front we have Apache Webserver with mod_jl load balancer. All requests
I added the following code
protected void handleInstantiateExceptions(Throwable t, String
className) throws ReflectionException, MBeanException {
log.error("Error instantiating MBean className=" + className, t);
to "jmx/src/main/org/jboss/mx/server/MBeanServerImpl.java"
The following
This is the trace that the last call to
createTopicConnection(SpyConnectionFactory.java:78) produces when the
system runs ok.
2003-10-02 12:56:58,796 TRACE
[org.jboss.mq.security.ServerSecurityInterceptor] Autenticating user
null/null
2003-10-02 12:56:58,796 TRACE
[org.jboss.security.plugins.JaasS
Title: Surprise with SSL after migrating from 3.0.x to 3.2.1
Hi all,
Well, I guess that the Subject sums it up. SSL configuration changed! For me, the worst part is that Jboss did not warn/complain about having the
jboss:service=invoker, type=jrmp,socketType=SSL
jboss:service=invoker, type
This is just a syntax error print out. All adding an error handler will do is
remove the bitching about using a default error handler to print the syntax error.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
-Original Message-
From:
Hi Jon,
Has the db pool been started?
I assume it has since you can lookup the data source in jndi.
Question for Alex:
Shouldn't this be in startService()?
You can't guarantee other dependent services are ready in
createService().
at
org.jboss.system.ServiceMBeanSupport.create(ServiceMB
On Thu, 2003-10-02 at 11:46, Panagiotis Korros wrote:
> 2003-10-02 13:00:26,125 DEBUG
> [org.jboss.security.plugins.JaasSecurityManager.jbossmq] Login failure
> javax.security.auth.login.LoginException: No LoginModules configured for
> jbossmq
> at
> javax.security.auth.login.LoginContext.ini
On Thu, 2003-10-02 at 11:58, Ricardo Coutinho wrote:
> Hi all,
>
> Well, I guess that the Subject sums it up. SSL configuration changed!
> For me, the worst part is that Jboss did not warn/complain about
> having the
>
> jboss:service=invoker,
> type=jrmp,socketType=SSL
> jboss:service=invoker,
If you have a testcase, please, email me.
Thanks,
alex
Rod Macpherson wrote:
We do see inserts and updates in the DB using SQL*Plus for example. We
also see inserts and updates if we fetch an entity bean to view the new
or updated record. The problem behavior is that JDBC database queries
(usin
Hi all,
I'm trying to write a MBean. I'm trying to use XDoclet to generate the
deployment descriptor and the interface.
Unfortunatly I cannot find an example. I was hoping somebody has a example
file which I can use to create my own MBean.
Thanks a lot.
Harm de Laat
Informatiefabriek
The Nethe
Hello list,
I'm having trouble restarting JBoss (I'm using JBoss 3.2.1) after
running some messaging tests that fail, the PersistenceManager throws an
exception which gets thrown in the resolveAllUncomittedTXs method in
org.jboss.mq.pm.jdbc2.PersistenceManager, as you can see in the stack
tra
Perhaps, so. It is instantiation of PersistenceManagerFactoryImpl. I'll
look at it. Thanks.
Adrian Brock wrote:
Hi Jon,
Has the db pool been started?
I assume it has since you can lookup the data source in jndi.
Question for Alex:
Shouldn't this be in startService()?
You can't guarantee other
> Has the db pool been started?
I don't know, how do I find out?
Cheers,
Jon.
On Thu, Oct 02, 2003 at 12:12:41PM +0100, Adrian Brock wrote:
> Hi Jon,
>
> Has the db pool been started?
> I assume it has since you can lookup the data source in jndi.
>
> Question for Alex:
>
> Shouldn't this
There is a fundamental problem with the hsql mbean.
When it starts, it creates a new thread to start the db.
JBoss continues on to other services.
If the thread takes too long to bind the sockets,
you get "Connection refused".
Somebody hacked jdbc2 so you can do retries
(default 5 times waiting 1.
On Thu, 2003-10-02 at 13:42, J.Mann wrote:
> > Has the db pool been started?
>
> I don't know, how do I find out?
>
Look at the logs, you should see a message saying
something like "[ManagedConnectionPool] started
for the db. Is this before or after the error?
Regards,
Adrian
--
x
> Yes, are there any messages in the log just before the above message
about the jbossmq security policy configuration?
No
This is the exact trace for the last succesfull logins to the queue
(Just as you told me I enabled tracing for org.jboss.security
org.jboss.mq.security org.jboss.mq.sm).
20
> Unfortunatly I cannot find an example.
Have you searched? :p
>I was hoping somebody has a example
>file which I can use to create my own MBean.
Something like this:
/**
* This MBean has a scheduled method that polls incoming(xml) instructions
files;
* it also can receive a direct instruc
Hello Adrian and thanks for the reply,
I'm using the PersistenceManager MBean configured out of the box to use
HypersonicSQL by default, would defining a different datasource using,
say, MySQL (let newDS be its name) and changing the PersistenceManager
configuration to use that one solve the pr
With an external db, you won't see the same problem.
The db is either started or it isn't.
There are examples configurations coming with jboss-3.2.2
in docs/examples/jms for other dbs
(I welcome contributions for other dbs not included).
The sql properties should work with 3.2.x and 3.0.7+
Don't
I investigated this more and found that it was a bug in XDoclet that
generated implementations of getData() in entity beans with overly
optimistic lazy evaluations. JBoss works just fine, but I had to change
XDoclet's template files. I guess this problem is fixed in later XDoclet
versions, but we s
Yes, this was the issue. My app requires two database connections,
but I had only copied the -ds.xml for one.
Thanks!
Jon Mann.
On Thu, Oct 02, 2003 at 01:57:43PM +0100, Adrian Brock wrote:
> On Thu, 2003-10-02 at 13:42, J.Mann wrote:
> > > Has the db pool been started?
> >
> > I don't know,
Hello again,
I've finally managed to make the PersistenceManager to work with MySQL,
using the mysql-jdbc2.xml from this link which I've found searching the
mailing list:
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/etc/server/examples/deploy/
There is an error in the mysql-jdbc2-ds.
Currently I have had issues where JBoss would not start because of a
lack of disk space for log files. Also, while running and disk space
runs out, no logs can be created.
How can I be alerted when either of these conditions are met? Was
thinking of creating an MBean that checks every hour. The
Hi,
I tried looking through the archives but found nothing substantial.I want to
precompile jsps on the server before deploying them to improve performance.I
saw 1 mthod using the web.xml but that would mean putting all my zillions of
jsp's under it- a nightmare scenario for maintenance.Is there a
On Thu, 2003-10-02 at 16:00, Stefan Puiu wrote:
> Hello again,
>
> I've finally managed to make the PersistenceManager to work with MySQL,
> using the mysql-jdbc2.xml from this link which I've found searching the
> mailing list:
> http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/etc/serve
> I saw 1 mthod using the web.xml but that would
> mean putting all my zillions of jsp's under it- a nightmare scenario
> for maintenance.
You could use XDoclet to generate your web.xml, but you're right, it's a
mess.
See
http://www.coredevelopers.net/technology/jetty/jetty-jboss-faq.jsp#JSP_Prec
Hi everybody,
I got a problem while JBoss was deploying the traditional HelloEJB
sample. The most interesting part of the JBoss's log says:
12:20:23,302 WARN [verifier] EJB spec violation:
Bean : Hello
Section: 22.2
Warning: The bean provider must specify
You can configure log4j to send ERROR level logging
to an e-mail address using the appender. Not tried it myself.
You'll probably have to change jboss-service.xml so that the
mail service is deployed before the log4j service.
Regards,
Adrian
On Thu, 2003-10-02 at 16:18, Michael Klem wrote:
> Cur
Post the output from
jar -tf HelloWorld.jar
Regards,
Adrian
On Thu, 2003-10-02 at 17:06, Santi Caballe Llobet wrote:
> Hi everybody,
>
> I got a problem while JBoss was deploying the traditional HelloEJB
> sample. The most interesting part of the JBoss's log says:
>
> ===
Yes you can add an MBean that do that for you (even backuping old log to
another partition for instance)
For the startup condition, you can simply do this check before running JBoss
(that is hack the run.sh script for instance). But I can't imagine that a
disk space problem would prevent you to ac
Hi Adrian,
First of all thank you for answering. The HelloWorld.jar's content
is:
=
C:\jboss\server\default\deploy>jar -tf HelloWorld.jar
META-INF/
META-INF/MANIFEST.MF
examples/
examples/Hello.class
examples/HelloBean.class
examples/HelloHome.class
examples
I think the Ant jspc target can generate a web XML fragment
that Ant can then substitute into your web.xml automatically.
Haven't tried this myself ... yet - just read about it.
JD
-Original Message-
From: Balakrishnan, Vijay [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 02, 2003 8:29
Tried this in 3.2.2RC2. Works like a charm, nothing special needs to be
done.
Joachim
- Original Message -
From: "Adrian Brock" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 02, 2003 6:09 PM
Subject: Re: [JBoss-user] Lack of disk space question
> You can configure
On Thu, 2003-10-02 at 05:35, Bruce Slawson wrote:
> Adrian,
>
> Looks like I'm not crazy after all. I was able to recreate the problem
> running your code. It looks like it has nothing to do with
> stopping/starting the JMS container invoker. This is what I did to
> recreate it.
>
> I built
Yes, as is the case for the type 3 jdbc driver that has a bug, or the jsse
library that has a bug, etc.
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
[EMAIL PROTECTED] wrote:
The spec prohibits the use of files / native libraries for a r
Do you have an older version of the bcel.jar deployed? 3.2.2RC4 updated the
bcel.jar we ship to the 5.1 2003-04-25 release. Just running with this version
without recomping was showing binary compatibility problems between the previous
and current bcel.jars.
--
Scott Stark
Its seems to be occuring after the authentication cache is timing out. Is this
the 3.2.2RC4 release available from SF or a cvs snapshot?
Can you describe the runtime env a bit more in terms of how many
senders/receivers there are and how many msgs are being exchanged?
--
On Fri, 2003-10-03 at 00:27, Scott M Stark wrote:
> Do you have an older version of the bcel.jar deployed? 3.2.2RC4 updated the
> bcel.jar we ship to the 5.1 2003-04-25 release. Just running with this version
> without recomping was showing binary compatibility problems between the previous
> and c
Took awhile to get it to fail with TRACE logging but it finally did. I
used essentially the same test conditions that you mentioned. Without
trace logging I could get it to fail quickly. It seems like the delays
provided by the additional logging helped somewhat. In previous tests I
noticed
Hi Bruce,
I found the problem, it is fixed in CVS.
It should be availble from pserver in 24 hours time
or the nightly snapshot if I haven't missed the snapshot time.
The fix is in org.jboss.mq.server.BasicQueue.
It was a race condition. Nothing to do with transactions.
Thanks for testing this, I
On Thu, 2 Oct 2003 21:08, [EMAIL PROTECTED] wrote:
> This is just a syntax error print out. All adding an error handler will do
> is remove the bitching about using a default error handler to print the
> syntax error.
I realise that. Customers tend to complain if they see something in a log that
I have seen the problem to appear in jboss versions 3.2 and above. Now I
am using the 3.2.2RC4 release available at sourceforge.
In my runtime environment there is a message driven bean receiving the
messages configured to use the default message driven container.
There are 4-5 senders that each s
43 matches
Mail list logo
