[JBoss-user] Logging with Jboss 3.0
Is there a best practice for having my application output to the jboss logs? I haven't been able to find an docs or archived list threads on printing to the jboss logs in 3.0. -ryan -- Humans are the unfortunate result of a local maximum in the fitness landscape. www.ryanmarsh.com --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] SAR file with DB, EAR and MBean
Hi, Does anybody have an example of how to arrange the contents and describe the dependencies in a SAR file? The SAR needs to contain a db connection, an ear file and an mbean, and these parts should be deployed in the following order: db, ear, mbean. So far I have been deploying the 3 parts independently and configured the mbean to deploy after the ear by using the depends-list element in the mbeans service xml file. If i package a SAR like: META-INF/jboss-service.xml myapp.ear myapp-mbean.jar I cant figure out what the contens of the jboss-service.xml should be. Should it contain the contents of both the db-service.xml and the mbean-service.xml or can META-INF contain several service xml files? If anybody has hints or an example of this i would be greatfull... Thanks in advance.. ^Torsten --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging with Jboss 3.0
Hello Ryan, JBoss uses log4j for logging. All you need is to have a Category variable in your class and configure logging if neccessary in log4j.xml. alex Thursday, July 25, 2002, 9:47:33 AM, you wrote: RM Is there a best practice for having my application output to the jboss RM logs? I haven't been able to find an docs or archived list threads on RM printing to the jboss logs in 3.0. RM -ryan -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] HELP : JBoss 3.0.x isn't logging ANY RuntimeExceptions!!
Hi,
JBoss 3.0.x isn't logging ANY runtime exceptions that are happening. This
is VERY bad, and makes debugging almost impossible. I get absolutely
nothing on the console, or the server.log when any RuntimeException
happens (the transaction blows up, the client dies, but NOTHING on the
server).
For example, take this basic Stateless SessionBean
-- SLSB -
public String nullString;
/**
* @ejb:interface-method
*/
public String blowUp()
{
// null pointer exception
return nullString.toString();
}
--- CLIENT --
public static void main(String[] args) throws Exception
{
sessionBean = SessionBeanEJBUtil.getHome().create();
sessionBean.blowUp();
}
-
As I said, there is NOTHING on the server, and the client gets the
following :-
I am running 3.0.1RC1 from CVS (two nights ago), but this problem has been
around for ages. It is costing us heaps in wasted developer time.
My debug Threshold is set to INFO for the CONSOLE. Basically I am using
exactly the log4j.xml that comes with JBoss.
HELP!
Exception in thread main java.rmi.ServerException: RemoteException
occurred in server thread; nested exception is:
java.rmi.ServerException: null; CausedByException is:
null; nested exception is:
javax.ejb.EJBException: null
Embedded Exception
null
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at
org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:128)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:108)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:73)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76)
at
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:111)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
at $Proxy1.blowUp(Unknown Source)
at
au.com.ucw.cop.test.ExportBatchTest.main(ExportBatchTest.java:14)
Caused by: java.rmi.ServerException: null; CausedByException is:
null; nested exception is:
javax.ejb.EJBException: null
Embedded Exception
null
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:119)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:176)
at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61)
at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:129)
at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:183)
at
org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:313)
at org.jboss.ejb.Container.invoke(Container.java:705)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:370)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
Caused by: javax.ejb.EJBException: null
Embedded Exception
null
at
org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:675)
at
org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)
at
RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANY RuntimeExceptions!!
Jboss uses log4j. If you want to change what jboss logs, edit the
log4j.xml file. For more info I think there is stuff in the Quick Start
Guide:
http://prdownloads.sourceforge.net/jboss/JBoss.3.0QuickStart.Draft3.pdf?
download
-James
-Original Message-
From: Craig O'Shannessy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 1:48 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANY
RuntimeExceptions!!
Hi,
JBoss 3.0.x isn't logging ANY runtime exceptions that are happening.
This
is VERY bad, and makes debugging almost impossible. I get absolutely
nothing on the console, or the server.log when any RuntimeException
happens (the transaction blows up, the client dies, but NOTHING on the
server).
For example, take this basic Stateless SessionBean
-- SLSB -
public String nullString;
/**
* @ejb:interface-method
*/
public String blowUp()
{
// null pointer exception
return nullString.toString();
}
--- CLIENT --
public static void main(String[] args) throws Exception
{
sessionBean = SessionBeanEJBUtil.getHome().create();
sessionBean.blowUp();
}
-
As I said, there is NOTHING on the server, and the client gets the
following :-
I am running 3.0.1RC1 from CVS (two nights ago), but this problem has
been
around for ages. It is costing us heaps in wasted developer time.
My debug Threshold is set to INFO for the CONSOLE. Basically I am using
exactly the log4j.xml that comes with JBoss.
HELP!
Exception in thread main java.rmi.ServerException: RemoteException
occurred in server thread; nested exception is:
java.rmi.ServerException: null; CausedByException is:
null; nested exception is:
javax.ejb.EJBException: null
Embedded Exception
null
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.ja
va:701)
at java.lang.Thread.run(Thread.java:536)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRem
oteCall.java:247)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223
)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at
org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvoker
Proxy.java:128)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:1
08)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.jav
a:73)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76)
at
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionI
nterceptor.java:111)
at
org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
at $Proxy1.blowUp(Unknown Source)
at
au.com.ucw.cop.test.ExportBatchTest.main(ExportBatchTest.java:14)
Caused by: java.rmi.ServerException: null; CausedByException is:
null; nested exception is:
javax.ejb.EJBException: null
Embedded Exception
null
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce
ptor.java:119)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor
CMT.java:176)
at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61)
at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.jav
a:129)
at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:183)
at
org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer
.java:313)
at org.jboss.ejb.Container.invoke(Container.java:705)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:370
)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANYRuntimeExceptions!!
I am using the default logging that comes with JBoss and it is not
logging RuntimeExceptions! I have changed the logging to DEBUG and I
still didn't get any. I don't think this problem is mine.
Are you saying that you don't think JBoss should log transaction crashes
by default? (I don't mean to sound rude, but did you actually read my
email?)
Craig
On Thu, 2002-07-25 at 17:46, James Ward wrote:
Jboss uses log4j. If you want to change what jboss logs, edit the
log4j.xml file. For more info I think there is stuff in the Quick Start
Guide:
http://prdownloads.sourceforge.net/jboss/JBoss.3.0QuickStart.Draft3.pdf?
download
-James
-Original Message-
From: Craig O'Shannessy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 1:48 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANY
RuntimeExceptions!!
Hi,
JBoss 3.0.x isn't logging ANY runtime exceptions that are happening.
This
is VERY bad, and makes debugging almost impossible. I get absolutely
nothing on the console, or the server.log when any RuntimeException
happens (the transaction blows up, the client dies, but NOTHING on the
server).
For example, take this basic Stateless SessionBean
-- SLSB -
public String nullString;
/**
* @ejb:interface-method
*/
public String blowUp()
{
// null pointer exception
return nullString.toString();
}
--- CLIENT --
public static void main(String[] args) throws Exception
{
sessionBean = SessionBeanEJBUtil.getHome().create();
sessionBean.blowUp();
}
-
As I said, there is NOTHING on the server, and the client gets the
following :-
I am running 3.0.1RC1 from CVS (two nights ago), but this problem has
been
around for ages. It is costing us heaps in wasted developer time.
My debug Threshold is set to INFO for the CONSOLE. Basically I am using
exactly the log4j.xml that comes with JBoss.
HELP!
Exception in thread main java.rmi.ServerException: RemoteException
occurred in server thread; nested exception is:
java.rmi.ServerException: null; CausedByException is:
null; nested exception is:
javax.ejb.EJBException: null
Embedded Exception
null
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.ja
va:701)
at java.lang.Thread.run(Thread.java:536)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRem
oteCall.java:247)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223
)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at
org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvoker
Proxy.java:128)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:1
08)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.jav
a:73)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76)
at
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionI
nterceptor.java:111)
at
org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
at $Proxy1.blowUp(Unknown Source)
at
au.com.ucw.cop.test.ExportBatchTest.main(ExportBatchTest.java:14)
Caused by: java.rmi.ServerException: null; CausedByException is:
null; nested exception is:
javax.ejb.EJBException: null
Embedded Exception
null
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce
ptor.java:119)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor
CMT.java:176)
at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61)
at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.jav
a:129)
at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:183)
at
org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer
.java:313)
at org.jboss.ejb.Container.invoke(Container.java:705)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at
org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:370
)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at
RE: [JBoss-user] RE: MS SQL XA driver (was: You are not getting the semantics you expect warning)
Burns, Jamie wrote: It seems clear that JBoss is finding com.microsoft.jdbcx.sqlserver.SQLServerDataSource. If it couldnt find it l would expect a ClassNotFoundException. It also seems clear that it should be able to be cast it to javax.sql.XADataSource since the super class implements this. I agree. The only thing I can think of that would cause this problem is if two different classloaders were being used, such that XADataSource (the target of the cast) was loaded by one classloader, and SQLServerDataSource was loaded by another classloader (along with another copy of XADAtaSource). My understanding is that if the same class is loaded by two different classloaders, so that you have versions C1 and C2 of the same class, you can't cast a C1 to a C2. However, I don't know much about how the classloading works in JBoss. It may depend on where you put the MSSQL JAR file. (I had mine in JBOSS_HOME\server\default\lib.) Why do you say that it should implement XAResource when its being cast as an XADataSource? Sorry, I meant XADataSource. You might try filing this as a bug in the the SourceForge bug tracker for JBoss, giving a clear, minimal test case. Ben --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Jetty] WARNING: HttpException(400, Bad Request, Missing Content)
Hello guys, sometimes I meet the following warning: WARN [Jetty] WARNING: POST /some-url/ HTTP/1.1 HttpException(400, Bad Request, Missing Content) Other times this same page is processed without it. All updates are done correctly in both cases. What does this warning mean? TIA -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] If http session is replicated.. no need for session affinity?
I agree. Plus you get better performance: with sticky sessions, you only serialize once per session modification, otherwise, you pay the price twice. Modifications will occur soon thanks to Jules' code. Cheers, Sacha -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Lucas McGregor Envoyé : jeudi, 25 juillet 2002 01:23 À : '[EMAIL PROTECTED]' Objet : RE: [JBoss-user] If http session is replicated.. no need for session affinity? That depends, how fast does replication happen? Are all writes in synch, or do they take time to propagate? If they take time, then a user might leave server A with a state, and then hit server B which has an older session state. What about concurrency? What is a user makes two quick actions, like changing a setting in a user profile. One request to change language to English hits server A and a request to change it back to Spanish hits server B. Which one becomes the final setting? Will multiple servers have non-coherent sessions? Session failover is really built for failover. A failure has happened, and the system is trying to deal with it. It isn't really session load balancing, and using it as such might cause you to run into a bunch of hard to detect, hard to replicate, hard to diagnose, and hard to fix bugs. I would stick to sticky session at the loadbalancer level. Just my $0.02. Lucas McGregor -Original Message- From: Joao Clemente [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 3:50 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] If http session is replicated.. no need for session affinity? Hi. As I was looking for a good load balancing solution for JBoss, it just came to my mind this question: If httpSession is replicated, all machines have all session instances in memory... So, there is no need to use a sticky-session load balancing algorithm, right? Furthermore, as we do not need to check the session, we don't need a layer-7 LB, so we can use a simpler/faster layer-4 LB without a problem! Or maybe there is something I am not seeing and it's still better to redirect the client to the same machine? -- /-- João Pedro Clemente jpcl @ rnl.ist.utl.pt - | There are no hard things. You're just misprepared | Powered by a i686 cpu running Linux 2.4.16 (LFS 3.1) - 47 min uptime \--- --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JBoss's catalina
Hi, Can anyone tell me something about Catalina webserver that comes with Jboss. Is it as good as a seperate Tom Cat server OR it has some minimal features only? Regards, Preeti --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANYRuntimeExceptions!!
Craig,
I may be completely wrong here, but my understanding of JBoss is this:
By default JBoss logs it's own stuff. If you have an application that
you want logging on, you must implement logging within it. I recommend
logging with log4j since it integrates well with JBoss (And is really
neat). You can also just do System.out.printlns. In other words, JBoss
doesn't log for your App. You must implement logging on your own. I
could be way off, but in my apps I have always implemented my own
logging.
-James
-Original Message-
From: Craig O'Shannessy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 2:56 AM
To: jboss-user
Subject: RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging
ANYRuntimeExceptions!!
I am using the default logging that comes with JBoss and it is not
logging RuntimeExceptions! I have changed the logging to DEBUG and I
still didn't get any. I don't think this problem is mine.
Are you saying that you don't think JBoss should log transaction crashes
by default? (I don't mean to sound rude, but did you actually read my
email?)
Craig
On Thu, 2002-07-25 at 17:46, James Ward wrote:
Jboss uses log4j. If you want to change what jboss logs, edit the
log4j.xml file. For more info I think there is stuff in the Quick
Start
Guide:
http://prdownloads.sourceforge.net/jboss/JBoss.3.0QuickStart.Draft3.pdf?
download
-James
-Original Message-
From: Craig O'Shannessy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 1:48 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANY
RuntimeExceptions!!
Hi,
JBoss 3.0.x isn't logging ANY runtime exceptions that are happening.
This
is VERY bad, and makes debugging almost impossible. I get absolutely
nothing on the console, or the server.log when any RuntimeException
happens (the transaction blows up, the client dies, but NOTHING on the
server).
For example, take this basic Stateless SessionBean
-- SLSB -
public String nullString;
/**
* @ejb:interface-method
*/
public String blowUp()
{
// null pointer exception
return nullString.toString();
}
--- CLIENT --
public static void main(String[] args) throws Exception
{
sessionBean = SessionBeanEJBUtil.getHome().create();
sessionBean.blowUp();
}
-
As I said, there is NOTHING on the server, and the client gets the
following :-
I am running 3.0.1RC1 from CVS (two nights ago), but this problem has
been
around for ages. It is costing us heaps in wasted developer time.
My debug Threshold is set to INFO for the CONSOLE. Basically I am
using
exactly the log4j.xml that comes with JBoss.
HELP!
Exception in thread main java.rmi.ServerException: RemoteException
occurred in server thread; nested exception is:
java.rmi.ServerException: null; CausedByException is:
null; nested exception is:
javax.ejb.EJBException: null
Embedded Exception
null
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.ja
va:701)
at java.lang.Thread.run(Thread.java:536)
at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRem
oteCall.java:247)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223
)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at
org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown
Source)
at
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvoker
Proxy.java:128)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:1
08)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.jav
a:73)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76)
at
org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionI
nterceptor.java:111)
at
org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
at $Proxy1.blowUp(Unknown Source)
at
au.com.ucw.cop.test.ExportBatchTest.main(ExportBatchTest.java:14)
Caused by: java.rmi.ServerException: null; CausedByException is:
null; nested exception is:
javax.ejb.EJBException: null
Embedded Exception
null
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce
ptor.java:119)
at
RE: [JBoss-user] Running several jboss instances on the same machine
Hello, I'm portuguese. Will write in english so that everyone understands. I now have the answer to my problem. I poked the configuration files and mailing lists. When I start up two JBoss instances, the log gives me no conflicts. I'm attaching a little file with the changes that I have made to the configuration. Regards Daniel Santos -Original Message- From: Emerson Cargnin - SICREDI Serviços [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 5:37 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Running several jboss instances on the same machine vc é brasileiro??? we use this approache, but uses a different virtual ip for each developer... Daniel Santos wrote: Hello, all I need to run several Jboss server instances on a machine with one IP address. I have different configurations for each developer. I don't know how to assign a different port to each conf. Can anyone help me ? (I'm using jetty) By the way, when I run the jboss startup script and supply it the name of the configuration I uses default. I'm using jboss 3.0.0 Many thanks Daniel Santos --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user -- Emerson Cargnin - MSA SICREDI - Tel : 3358-4860 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user To prevent conflicts between services of different instances of JBoss 3.0.0 running on the same machine, the following changes should be made to the configuration files of each developer's configuration. Follows a list of files and the changes that have to be made : deploy/jetty-plugin.sar -- First uncompress the sar file using unzip. In section : mbean : jboss.web:service=Jetty change the port numbers of : attribute name : org.mortbay.http.SocketListener attribute name : org.mortbay.http.SunJsseListener Now compress the changed contents and put the new file were it was. deploy/jmx-html-adaptor.sar -- First uncompress the sar file using unzip. In section : mbean : com.sun.jdmk.comm.HtmlAdaptorServer change the port numbers of : attribute name : Port Now compress the changed contents and put the new file were it was. conf/jboss-service.xml -- In section : mbean : org.jboss.web.WebService change the port numbers of : attribute name : Port In section : mbean : org.jboss.naming.NamingService change the port numbers of : attribute name : Port In section : mbean : org.jboss.invocation.jrmp.server.JRMPInvoker change the port numbers of : attribute name : RMIObjectPort deploy/jbossmq-service.xml -- In section : mbean : org.jboss.mq.il.uil.UILServerILService change the port numbers of : attribute name : ServerBindPort In section : mbean : org.jboss.mq.il.oil.OILServerILService change the port numbers of : attribute name : ServerBindPort deploy/hsqldb-service.xml -- change the port numbers of : config-property name=ConnectionURL - 10007 In section : mbean : org.jboss.jdbc.HypersonicDatabase change the port numbers of : attribute name : Port - 10007
Re: [JBoss-user] JBoss's catalina
It is the full tomcat 4.01 or 4.03 depending on which implementation of JBOSS 3.x you have. Best Regards, Anthony Geoghegan. J2EE Developer CPS Ireland Ltd. - Original Message - From: Preeti Sood [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 25, 2002 11:08 AM Subject: [JBoss-user] JBoss's catalina Hi, Can anyone tell me something about Catalina webserver that comes with Jboss. Is it as good as a seperate Tom Cat server OR it has some minimal features only? Regards, Preeti --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] stateless session beans cannot call statefulsession beans!!?
Hi David,
I have a non-transactional SQL datasource (legacy). I am trying to
update it as transactionally as possible. Using afterComplete() in a
SFSB that implements SessionSynch. works pretty damn well (it is
guaranteed that ALL the other datasources have committed).
Anyhow, I got a fairly neat solution to the problem from a guy on
EJBinterest (Doug Bateman). He suggested I pass the SFSB in to the
SLSB, so someone else can handle the remove (a SFSB).
e.g. SFSB1 creates and caches SFSB2, and when it calls SLSB1, it passed
the local ref to SFSB2 in as an arg, this allows SFSB1 to do an
ejbRemove on SFSB2 when it's own remove() gets called.
Thanks for the input.
Craig
On Sun, 2002-07-21 at 01:09, David Jencks wrote:
I don't understand what you are trying to do. Why not update the
datasource when the data changes?
If you are trying to write a cache that flushes at the end of the tx,
notified by a synch, I don't think session beans are necessarily an
appropriate solution. JDO has this problem also, and I don't think there
is a good solution. It's mentioned in appendix C of the jca spec in an
un-implementable way.
I think the way to do it is to write a jca adapter that exposes some
transactional interface and knows about the tx manager. When its tx
interface (LocalTransaction or XAResource) is informed of a new tx, it can
register a synch with the tx manager so it can flush on beforeCommit().
Currently the JDO spec sidesteps this solution by requiring you to close
your jdo persistence managers (connection handles) inside the tx, which is
the trigger for the flush operation.
david jencks
On 2002.07.16 21:42:46 -0400 Craig O'Shannessy wrote:
On Wed, 2002-07-17 at 00:43, Maris Orbidans wrote:
Start a new transaction with someMethod(accountNumber1,amount) method.
I think then the SFSB will be removable because it will not be
participating in any transaction.
This is true, but doesn't actually help what I am trying to do. I need
to update a non-transactional datasource, and the best way to do this
seems to be to use SessionSynchronization, (which can ONLY be used on
SFSB's). The update needs to be part of the outer transaction. This
seems to preclude the use of ANY SLSB's anywhere between the original
client call and the SFSB doing the SessionSynchronization. This seems
like a nasty, dangerous and undocumented restriction.
This means, for example, that the Container may delegate the
requests from the same client within the same transaction to
different
instances, and that the Container may interleave requests
from multiple
transactions to the same instance
I am not sure that it means that instances of SLSB are reentrant.
(spec. 7-11-8)
Maris
-Original Message-
From: Craig O'Shannessy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 16, 2002 12:15 PM
To: jboss-user
Subject: [JBoss-user] stateless session beans cannot call
stateful session beans!!?
Hi,
I wonder if someone could clear up a problem for me. It seems that a
Stateless session bean cannot really use a Stateful session bean for
two reasons.
1. The stateless bean cannot call remove on the stateful,
therefore can't
clean it up (see code below)
2. If the stateless bean holds onto a reference to a stateful
bean to get
around creating one on each call and avoid problem 1.,
another problem
occurs. The Stateless bean can be shared between
concurrent transactions
(see quote from spec below), therefore the stateful beans
transactional
scope is indeterminate (cause nasty blocking or even overlapping
transactions?)
One reason you might want to use a Stateful bean from a
Stateless is to
do SessionSyncronization on a non transactional datasouce for
example.
- Code example for problem 1.
--
/**
* For readability, this example uses xdoclet code, if you
don't use it,
* you might want to check it out!
*/
class StatelessBean extends SessionBean
{
/**
* @ejb:interface-method
*/
public void transferMoney(long account1,long
account2,double amount)
{
StatefulEJBLocal stateful =
StatefulEJBUtil.getLocalhome().create();
stateful.someMethod(accountNumber1,amount);
// stateful.remove(); -- Can't do this, RemoveException
// (7.5.7 p79 ejb2 spec)
}
}
--
Quote from Section 7.8, p87 of ejb2 spec
Because all instances of a stateless session bean are equivalent, the
container can choose to delegate a client-invoked method to
any available
Re: [JBoss-user] [Jetty] WARNING: HttpException(400, Bad Request,Missing Content)
I'm forwarding you to jetty-discuss: Jules Alex Loubyansky wrote: Hello guys, sometimes I meet the following warning: WARN [Jetty] WARNING: POST /some-url/ HTTP/1.1 HttpException(400, Bad Request, Missing Content) Other times this same page is processed without it. All updates are done correctly in both cases. What does this warning mean? TIA --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Message consumer closing due to error in listening thread
Hi I have a process which puts a message on a queue and then subscribes to a topic awaiting an answer. When it gets the answer, it tries to close the topic, which it does successfully, but I quickly get: 2002-07-25 08:11:11,031 WARN [org.jboss.mq.SpyMessageConsumer] Message consumer closing due to error in listening thread. javax.jms.IllegalStateException: Session is closed. at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:536) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:493) at java.lang.Thread.run(Thread.java:536) 2002-07-25 08:11:11,031 DEBUG [org.jboss.mq.SpyMessageConsumer] Message consumer closing. When I close the topic, I do a topicSession.close() topicConnection.close() What am I doing wrong, if anything? Eric Kaplan Armanta, Inc. 55 Madison Ave. Morristown, NJ 07960 Phone: (973) 326-9600 attachment: winmail.dat
[JBoss-user] Other interesting jms errors
Hi In addition to the error I just reported, we came across a couple of others which we have yet to reproduce but other people may have encountered. If no one has seen this, hopefully it points to a bug that can be fixed. Regards In the first one, we just bring up the application, subscribe to a topic, and get the following right after the first receipt of a jms publish on the topic, after which the subscription is invalid: 2002-07-24 17:46:47,859 WARN [MessageListenerThread - pool] Message consumer closing due to error in listening thread. org.jboss.mq.SpyJMSException: Cannot acknowlege a message at org.jboss.mq.Connection.send(Connection.java:790) at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:537) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:493) at java.lang.Thread.run(Thread.java:536) linked exception is: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.ja va:2591) at java.io.ObjectInputStream.readByte(ObjectInputStream.java:837) at org.jboss.mq.il.oil.OILServerIL.waitAnswer(OILServerIL.java:521) at org.jboss.mq.il.oil.OILServerIL.acknowledge(OILServerIL.java:180) at org.jboss.mq.Connection.send(Connection.java:786) at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:537) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:493) at java.lang.Thread.run(Thread.java:536) 2002-07-24 17:46:47,859 WARN [MessageListenerThread - pool] Message consumer closing due to error in listening thread. org.jboss.mq.SpyJMSException: Cannot acknowlege a message at org.jboss.mq.Connection.send(Connection.java:790) at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:537) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:493) at java.lang.Thread.run(Thread.java:536) linked exception is: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.ja va:2591) at java.io.ObjectInputStream.readByte(ObjectInputStream.java:837) at org.jboss.mq.il.oil.OILServerIL.waitAnswer(OILServerIL.java:521) at org.jboss.mq.il.oil.OILServerIL.acknowledge(OILServerIL.java:180) at org.jboss.mq.Connection.send(Connection.java:786) at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:537) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:493) at java.lang.Thread.run(Thread.java:536) 2002-07-24 17:46:47,875 WARN [MessageListenerThread - pool] Message consumer closing due to error in listening thread. org.jboss.mq.SpyJMSException: Cannot acknowlege a message at org.jboss.mq.Connection.send(Connection.java:790) at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:537) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:493) at java.lang.Thread.run(Thread.java:536) linked exception is: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.ja va:2591) at java.io.ObjectInputStream.readByte(ObjectInputStream.java:837) at org.jboss.mq.il.oil.OILServerIL.waitAnswer(OILServerIL.java:521) at org.jboss.mq.il.oil.OILServerIL.acknowledge(OILServerIL.java:180) at org.jboss.mq.Connection.send(Connection.java:786) at org.jboss.mq.SpyMessage.doAcknowledge(SpyMessage.java:537) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:493) at java.lang.Thread.run(Thread.java:536) 2002-07-24 17:46:47,875 WARN [Connection Monitor Thread] Connection failure: org.jboss.mq.SpyJMSException: Connection Failed at org.jboss.mq.Connection.asynchFailure(Connection.java:603) at org.jboss.mq.Connection$PingTask.run(Connection.java:1187) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:36 4) at java.lang.Thread.run(Thread.java:536) linked exception is: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.ja va:2591) at java.io.ObjectInputStream.readByte(ObjectInputStream.java:837) at org.jboss.mq.il.oil.OILServerIL.waitAnswer(OILServerIL.java:521) at org.jboss.mq.il.oil.OILServerIL.ping(OILServerIL.java:395) at org.jboss.mq.Connection.pingServer(Connection.java:1021) at org.jboss.mq.Connection$PingTask.run(Connection.java:1183) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:36 4) at java.lang.Thread.run(Thread.java:536) 2002-07-24 17:47:09,421 WARN [Connection Monitor Thread] Connection failure: org.jboss.mq.SpyJMSException: Connection Failed at org.jboss.mq.Connection.asynchFailure(Connection.java:603) at org.jboss.mq.Connection$PingTask.run(Connection.java:1187) at
[JBoss-user] best primary key generator method
Hi, Someone has asked me this question so I thought I'd pass it on. Currently for primary key generation we're using a pattern described in the EJB Design Patterns book. http://www.theserverside.com/books/EJBDesignPatterns/index.jsp In brief - the entity bean in question will query a stateless session bean for the next PK. - The stateless session bean has a block of numbers available and returns the next number in the block. - If the session bean's block has been used up, it will create a new block by requesting the latest PK from a sequence table in the database (via an entity bean), and incrementing this value. It seems to work very well so far. The interaction with the DB is kept to a minimum due to the caching of PKs using the stateless session bean and it is not possible to duplicate keys in a clustered environment because each stateless session bean holds a unique block (taken from the database). My question is this. How does this compare to using JBoss's own PK generator class? Might the JBoss solution offer a more efficient option? AND... how might this compare to, say, Weblogic's autoprimarykey option. Any information greatly received. Thanks, Tim ___ emuse technologies Hanover Quay Dublin 2 Ireland Tel: 353-1-671-7317 Fax: 353-1-671-7319 website: http://www.emusetechnologies.com/ email: mailto:[EMAIL PROTECTED] ___ This message has been scanned for viruses using GroupShield 4.5 for Exchange Server 5.5 CONFIDENTIALITY NOTICE - The information contained in this email message is intended only for confidential use of the named recipient. If the reader is not the intended recipient or the person responsible for delivering it to the recipient, you are hereby notified that you have received this communication in error and that any review, dissemination or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately. --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANYRuntimeExceptions!!
James - I'm a relative newbie to EJB, but have used log4j in the past. What I'm not sure of is how is the log4j first configured for my EJBs? In a normal java application I would include the PropertyConfigurator.configure(myConfigFile) statement in the main(String[] args) block at the start of my application. This however, goes out the window with stateless session beans and Entity beans. I'm not sure as to how JBoss will maintain one instance of my Logger class. Will my classes (even just plain old java classes that are called by a servlet etc) somehow use the same instance of the logger class that JBoss is using - and therefore I can use the log4J settings that come with JBoss, of do I need to include a separate configuration file and if so when would I initialise it? Any help or words of wisdom would be appreciated. Regards Alan. winmail.dat
RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANYRuntimeExceptions!!
Title: RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANYRuntimeExceptions!! There are 2 ways to use log4j for your EJBs in JBoss. The simplest is to modify JBoss' configuration file, log4j.xml and include your own settings. The other, a little more complicated, is to create a servlet that reads your log4j configuration file and initializes the environment. There are more detailsabout it in this message from the Log4Jmailing list: http://www.mail-archive.com/log4j-user@jakarta.apache.org/msg03297.html Sincerely, Paul -Message d'origine-De: Alan Yost [mailto:[EMAIL PROTECTED]]De la part de Alan YostEnvoyé: jeudi 25 juillet 2002 15:16À: [EMAIL PROTECTED]Objet: RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANYRuntimeExceptions!! James - I'm a relative newbie to EJB, but have used log4j in the past. What I'm not sure of is how is the log4j first configured for my EJBs? In a normal java application I would include thePropertyConfigurator.configure(myConfigFile) statement in themain(String[] args) block at the start of my application. This however, goes out the window with stateless session beans and Entity beans. I'mnot sureas to how JBoss will maintain one instance of myLogger class. Will my classes (even just plain old java classes that are called by a servlet etc) somehow use the same instance of the logger class that JBoss is using - and therefore I can use the log4J settings that come with JBoss, of do I need to include a separate configuration file and if so when would I initialise it? Any help or words of wisdom would be appreciated. Regards Alan. attachment: winmail.dat
[JBoss-user] Fwd: RE: using log4J with JBoss and Cactus
Greetings, Paul Ekeland, a JBoss, Cactus as well as log4j user recently posted the following to the log4j-user@ mailing list. As I understand it, he claims that one has to use org.jboss.logging.appender.FileAppender instead of org.apache.log4j.FileAppender under JBoss. Is this true? If so why is this? Many thanks in advance, ps: Here is his post: Reply-To: Log4J Users List [EMAIL PROTECTED] Delivered-To: mailing list [EMAIL PROTECTED] From: Paul Ekeland [EMAIL PROTECTED] To: Log4J Users List [EMAIL PROTECTED] Subject: RE: using log4J with JBoss and Cactus Date: Thu, 25 Jul 2002 16:12:40 +0200 Hello Ceki, Thanks for answering. So far, I have solved one of the problem: now my appenders do produce files. In the log4j.xml of JBoss, my error was to make them derive from the org.apache.log4j.FileAppender. The correct way is to make them derive from JBoss' class.: appender name=cactus class=org.jboss.logging.appender.FileAppender [snip] -- Ceki For complete log4j documentation please refer to http://qos.ch/log4jBook.html --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] If http session is replicated.. no need for sessionaffinity?
If we know that your cluster is using session affinity, there are a large number of optimisations that we can make, which will result in a faster service for you. I will be checking in an updated implementation of distributable sessions for Jetty shortly, which I shall then spend some time optimising in this way. Ok. But that is a feature to come? There is no optimization at this time? I mean, there is no advantage at this time? You would be well advised to use session affinity if you can. If you don't you are simply making a lot more work for your cluster. Well, I am trying to understand WHY I am doing more work for my cluster this way. Can you explain that? Lets supose the replication occurs without problems, the requests are spaced in time no there are no problems in incoerent states. Is there a penalty (memory usage, performace, or whatever) for not directing the requests to the same instance? Why? --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] EJB Notification errors - looking for examples
Hello again. Well after scratching my head for a long long time, it appears to me like the MainDeployer is contains arguments or return methods that aren't serializable and thus causing the Notificaiton object to throw a RemoteException (really a wrapped MarshelException). In my previous emails I include the stack trace etc. I'd be happy to talk with someone and explain the problem further, but at this point I'm filing it as a bug. Also in response to my previous emails, and in comments in the MainDeployer, I was referred to look at the farm deployment. Problem is I can't find that source anywhere. Can some direct me in the right location where I can see the farm deployer in action. Has anyone been able to recieve notifications from the MainDeployer (it is broadcasting them)? Another question: currently the notifications are sent with the RMINotficationListener, but there is a switch statement that checks to see if it should use this, JMSNotificationListener, or others. Where does this option get set? How can I configure notifications to use a JMS queue? Mike [EMAIL PROTECTED] wrote: Send JBoss-user mailing list submissions to [EMAIL PROTECTED] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/jboss-user or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of JBoss-user digest... Today's Topics: 1. Re: stateless session beans cannot call stateful session beans!!? (Craig O'Shannessy) 2. Re: JBoss's catalina (Anthony Geoghegan) 3. Re: [Jetty] WARNING: HttpException(400, Bad Request, Missing Content) (Jules Gosnell) 4. Message consumer closing due to error in listening thread (Eric Kaplan) 5. Other interesting jms errors (Eric Kaplan) --__--__-- Message: 1 Subject: Re: [JBoss-user] stateless session beans cannot call stateful session beans!!? From: Craig O'Shannessy [EMAIL PROTECTED] To: jboss-user [EMAIL PROTECTED] Date: 25 Jul 2002 20:19:28 +1000 Reply-To: [EMAIL PROTECTED] Hi David, I have a non-transactional SQL datasource (legacy). I am trying to update it as transactionally as possible. Using afterComplete() in a SFSB that implements SessionSynch. works pretty damn well (it is guaranteed that ALL the other datasources have committed). Anyhow, I got a fairly neat solution to the problem from a guy on EJBinterest (Doug Bateman). He suggested I pass the SFSB in to the SLSB, so someone else can handle the remove (a SFSB). e.g. SFSB1 creates and caches SFSB2, and when it calls SLSB1, it passed the local ref to SFSB2 in as an arg, this allows SFSB1 to do an ejbRemove on SFSB2 when it's own remove() gets called. Thanks for the input. Craig On Sun, 2002-07-21 at 01:09, David Jencks wrote: I don't understand what you are trying to do. Why not update the datasource when the data changes? If you are trying to write a cache that flushes at the end of the tx, notified by a synch, I don't think session beans are necessarily an appropriate solution. JDO has this problem also, and I don't think there is a good solution. It's mentioned in appendix C of the jca spec in an un-implementable way. I think the way to do it is to write a jca adapter that exposes some transactional interface and knows about the tx manager. When its tx interface (LocalTransaction or XAResource) is informed of a new tx, it can register a synch with the tx manager so it can flush on beforeCommit(). Currently the JDO spec sidesteps this solution by requiring you to close your jdo persistence managers (connection handles) inside the tx, which is the trigger for the flush operation. david jencks On 2002.07.16 21:42:46 -0400 Craig O'Shannessy wrote: On Wed, 2002-07-17 at 00:43, Maris Orbidans wrote: Start a new transaction with someMethod(accountNumber1,amount) method. I think then the SFSB will be removable because it will not be participating in any transaction. This is true, but doesn't actually help what I am trying to do. I need to update a non-transactional datasource, and the best way to do this seems to be to use SessionSynchronization, (which can ONLY be used on SFSB's). The update needs to be part of the outer transaction. This seems to preclude the use of ANY SLSB's anywhere between the original client call and the SFSB doing the SessionSynchronization. This seems like a nasty, dangerous and undocumented restriction. This means, for example, that the Container may delegate the requests from the same client within the same transaction to different instances, and that the Container may interleave requests from multiple transactions to the same instance I am not sure that it means that instances of SLSB are reentrant. (spec. 7-11-8)
RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANYRuntimeExceptions!!
Title: RE: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANYRuntimeExceptions!!
Alan,
Here is a little snippet from how I am
doing this:
import org.apache.log4j.Category;
public class CategoryDAO {
private static String
CLASSNAME = CategoryDAO.class.getName();
private Category cat =
(Category)Category.getInstance(CLASSNAME);
// blah blah
Hope that helps.
-James
-Original Message-
From: Alan Yost
[mailto:[EMAIL PROTECTED]] On Behalf Of Alan Yost
Sent: Thursday, July
25, 2002 7:16 AM
To:
[EMAIL PROTECTED]
Subject: RE: [JBoss-user] HELP :
JBoss 3.0.x isn't logging ANYRuntimeExceptions!!
James - I'm a relative newbie to EJB, but have used
log4j in the past. What I'm not sure of is how is the log4j first
configured for my EJBs?
In a normal java application I would include
thePropertyConfigurator.configure(myConfigFile) statement in themain(String[] args) block at the
start of my application. This however, goes out the window with stateless
session beans and Entity beans.
I'mnot sureas to how JBoss will maintain
one instance of myLogger class. Will my classes (even just plain
old java classes that are called by a servlet etc) somehow use the same
instance of the logger class that JBoss is using - and therefore I can use the
log4J settings that come with JBoss, of do I need to include a separate configuration
file and if so when would I initialise it?
Any help or words of wisdom would be appreciated.
Regards
Alan.
[JBoss-user] What does this error message mean?
This line appeared right before JBoss started puking error messages: 2002-07-24 09:30:21,154 DEBUG [org.jboss.mq.il.oil.OILClientILService]Closing receiver connections on port: 2464 But why would receiver connections be suddenly closed? What is port 2462? I can't seam to find it in any of my config files? Here's some more background on what I'm doing: I let jboss sit for about 20 hours and when i came back it was constantlydumping the following to the console: 2002-07-24 11:00:05,060 WARN [org.jboss.mq.Connection] Connection failure: org.jboss.mq.SpyJMSException: Connection Failedat org.jboss.mq.Connection.asynchFailure(Connection.java:603)at org.jboss.mq.Connection$PingTask.run(Connection.java:1187)atEDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)at java.lang.Thread.run(Thread.java:536)linked exception is:java.io.IOException: ping timeout.at org.jboss.mq.Connection$PingTask.run(Connection.java:1179)atEDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)at java.lang.Thread.run(Thread.java:536) I believe that JBossMQ died, because when I attempt to send a message to atopic i get the following error: 2002-07-24 10:59:25,591 ERROR [STDERR] org.jboss.mq.SpyJMSException: Cannotsend a message to the JMS server I have a very vanilla install of JBoss3.0.1rc1 (plus tomcat). To thejbossmq-destinations-service.xml, I have only added: mbean code="org.jboss.mq.server.jmx.Topic"name="jboss.mq.destination:service=Topic,name=HitTopic" depends optional-attribute-name="DestinationManager" jboss.mq:service=DestinationManager /depends/mbean Does anyone have any clue why this happened? Here's an except from my Server.log: 2002-07-24 09:20:31,326 DEBUG[org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemovernotifying pools, interval: 452002-07-24 09:28:01,326 DEBUG[org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemovernotifying pools, interval: 452002-07-24 09:30:21,154 DEBUG [org.jboss.mq.il.oil.OILClientILService]Closing receiver connections on port: 24642002-07-24 09:30:21,170 WARN [org.jboss.mq.il.oil.OILServerILService]Connection failure (1).java.net.SocketException: Connection reset by peer: JVM_recv in socket inputstream readat java.net.SocketInputStream.socketRead0(Native Method)at java.net.SocketInputStream.read(SocketInputStream.java:116)at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)at java.io.BufferedInputStream.read(BufferedInputStream.java:201)atjava.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2118)atjava.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2301)atjava.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:2368)atjava.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:2440)atjava.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream.java:2589)at java.io.ObjectInputStream.readByte(ObjectInputStream.java:837)atorg.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:190)at java.lang.Thread.run(Thread.java:536)2002-07-24 09:31:07,466 WARN [org.jboss.mq.Connection] Connection failure: org.jboss.mq.SpyJMSException: Connection Failedat org.jboss.mq.Connection.asynchFailure(Connection.java:603)at org.jboss.mq.Connection$PingTask.run(Connection.java:1187)atEDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)at java.lang.Thread.run(Thread.java:536)linked exception is:java.net.SocketException: Connection reset by peer: socket write errorat java.net.SocketOutputStream.socketWrite0(Native Method)atjava.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)at java.net.SocketOutputStream.write(SocketOutputStream.java:126)atjava.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:69)at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:127)atjava.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream.java:1583)at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:639)at org.jboss.mq.il.oil.OILServerIL.waitAnswer(OILServerIL.java:520)at org.jboss.mq.il.oil.OILServerIL.ping(OILServerIL.java:395)at org.jboss.mq.Connection.pingServer(Connection.java:1021)at org.jboss.mq.Connection$PingTask.run(Connection.java:1183)atEDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)at java.lang.Thread.run(Thread.java:536)2002-07-24 09:32:07,466 WARN [org.jboss.mq.Connection] Connection failure: org.jboss.mq.SpyJMSException: Connection Failedat org.jboss.mq.Connection.asynchFailure(Connection.java:603)at org.jboss.mq.Connection$PingTask.run(Connection.java:1187)atEDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)at java.lang.Thread.run(Thread.java:536)linked exception is:java.io.IOException: ping timeout.at
Re: [JBoss-user] HELP : JBoss 3.0.x isn't logging ANYRuntimeExceptions!!
JBoss is heirarchial. Jboss initializes it, and therefore your logging messages would utilize there root category appenders. This is configured in the jboss root dir/server/instance/conf/log4j.xml file, where instance is (out of the box) either all, default, or minimal. If your running out of the box then its default. The question is whether or not this is a good approach is up to you. This is the best approach I can think of. - Include log4j.jar with your EAR and declare the dependency in the EJB's Manifest file. (this is so you can deploy on other servers, for example an app server that doesn't already have log4j on the classpath) - Include log4j.properties in your classpath of your ejb's. (if you don't want to use the system configuration) - Include the following as a field in your EJB's private Logger log = Logger.getLogger(this.getClass()); - if you have log4j.properties on your classpath this will use that when instantiated log4j by default, however if it is already instantiated you will use that configuration. I usually modify log4j.xml and create a seperate RollingFileAppender, for my specific catalogs. Hope this helps. Mike I'm not sure as to how JBoss will maintain one instance of my Logger class. Will my classes (even just plain old java classes that are called by a servlet etc) somehow use the same instance of the logger class that JBoss is using - and therefore I can use the log4J settings that come with JBoss, of do I need to include a separate configuration file and if so when would I initialise it? Any help or words of wisdom would be appreciated. Regards Alan. -- Mike/ --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] CMR...
S. Chausson Are you using Remote Interface when you are calling myElement.setPerson(myPerson). The CMRs' only work with local interfaces, either pass a local reference ormap your remote to local with in themyElement.setPerson. I hope this helps. -Asif Rafiq Ahmed - Original Message - From: Sebastien CHAUSSON To: [EMAIL PROTECTED] Sent: Wednesday, July 24, 2002 4:17 AM Subject: [JBoss-user] CMR... Hi, I'm trying to populate the jboss default DB (Hypersonic) using CMRbut it doesn't work (I use JBoss 3.0): I have 2 entity bean (Person and Element) which have a relationship 'one-to-many' unidirectionnal. When I deploy my component in jboss, it automatically create 2 tables in the DB : Element (with a relation column) and Person = OK When I create a Person entity, jboss just add it in the Person table = OK When I create an Element entity,jboss just add it in the Element table (leaving relation column at 'null').= OK (I didn't chose to pass a 'Person' directly in the ejbCreate() method of the Element entity bean, but just to have setPerson() and getPerson()methods) But when I call myElement.setPerson(myPerson), I get this error message : [java] java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:[java] java.rmi.ServerException: null; CausedByException is:[java] $Proxy82; nested exception is:[java] javax.ejb.EJBException: null; CausedByException is:[java] $Proxy82[java] java.rmi.ServerException: null; CausedByException is:[java] $Proxy82; nested exception is:[java] javax.ejb.EJBException: null; CausedByException is:[java] $Proxy82[java] javax.ejb.EJBException: null; CausedByException is:[java] $Proxy82[java] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:245)[java] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:220)[java] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:122)[java] at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)[java] at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:128)[java] at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:108)[java] at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:73)[java] at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76)[java] at org.jboss.proxy.ejb.EntityInterceptor.invoke(EntityInterceptor.java:116)[java] at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)[java] at $Proxy8.setPerson(Unknown Source)[java] at DataPopulate.createElements(DataPopulate.java:397) [java] at DataPopulate.main(DataPopulate.java:45)[java] java.lang.ClassCastException: $Proxy82[java] no stack trace available[java] Could anyone explain to me whats wrong? Thanks for any advice. S. Chausson
RE: [JBoss-user] If http session is replicated.. no need for sessionaffinity?
I agree. Plus you get better performance: with sticky sessions, you only serialize once per session modification, otherwise, you pay the price twice. Sorry, but I don't see what you mean. You're saying that replica servers do NOT need to deserealize the sessions they get, unless they need to use them? Otherwise, I see no logic in your statement of serialize 1 time vs serialize 2 times. What I think is that: 1 - Cluster nodes A,B,C 2 - Session1 is created in A - A serializes Session1 and sends to group by multicast - B and C get the message, and unserialize session1. They now have session1 replica in memory 3a)- Session1 is changed in A (sticky session load balancing) - A serializes Session1 and sends to group by multicast - B and C get the message, and unserialize session1. They now have session1 replica in memory 3b)- Session1 is changed in B (LB without sticky session) - B serializes Session1 and sends to group by multicast - A and C get the message, and unserialize session1. They now have session1 replica in memory I see no performance difference in using either a dunmb LB or a sticky session LB. So, if there is, the cenario I just described is wrong. Please describe me why! Thank you Joao Clemente --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] What does this error message mean?
Does this happen every time you leave jboss sit for 20 hours, or is this the only time this has happened? Are the server and client on the same machine? If not are the system clocks sync'd? -Seth --On Thursday, July 25, 2002 1:47 PM -0500 Luttrell, Peter [EMAIL PROTECTED] wrote: This line appeared right before JBoss started puking error messages: 2002-07-24 09:30:21,154 DEBUG [org.jboss.mq.il.oil.OILClientILService] Closing receiver connections on port: 2464 But why would receiver connections be suddenly closed? What is port 2462? I can't seam to find it in any of my config files? Here's some more background on what I'm doing: I let jboss sit for about 20 hours and when i came back it was constantly dumping the following to the console: 2002-07-24 11:00:05,060 WARN [org.jboss.mq.Connection] Connection failure: org.jboss.mq.SpyJMSException: Connection Failed at org.jboss.mq.Connection.asynchFailure(Connection.java:603) at org.jboss.mq.Connection$PingTask.run(Connection.java:1187) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java :36 4) at java.lang.Thread.run(Thread.java:536) linked exception is: java.io.IOException: ping timeout. at org.jboss.mq.Connection$PingTask.run(Connection.java:1179) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java :36 4) at java.lang.Thread.run(Thread.java:536) I believe that JBossMQ died, because when I attempt to send a message to a topic i get the following error: 2002-07-24 10:59:25,591 ERROR [STDERR] org.jboss.mq.SpyJMSException: Cannot send a message to the JMS server I have a very vanilla install of JBoss3.0.1rc1 (plus tomcat). To the jbossmq-destinations-service.xml, I have only added: mbean code=org.jboss.mq.server.jmx.Topic name=jboss.mq.destination:service=Topic,name=HitTopic depends optional-attribute-name=DestinationManager jboss.mq:service=DestinationManager /depends /mbean Does anyone have any clue why this happened? Here's an except from my Server.log: 2002-07-24 09:20:31,326 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 45 2002-07-24 09:28:01,326 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 45 2002-07-24 09:30:21,154 DEBUG [org.jboss.mq.il.oil.OILClientILService] Closing receiver connections on port: 2464 2002-07-24 09:30:21,170 WARN [org.jboss.mq.il.oil.OILServerILService] Connection failure (1). java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:116) at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) at java.io.BufferedInputStream.read(BufferedInputStream.java:201) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:211 8) at java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInpu tSt ream.java:2301) at java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.j ava :2368) at java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.jav a:2 440) at java.io.ObjectInputStream$BlockDataInputStream.readByte(ObjectInputStream .ja va:2589) at java.io.ObjectInputStream.readByte(ObjectInputStream.java:837) at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java :19 0) at java.lang.Thread.run(Thread.java:536) 2002-07-24 09:31:07,466 WARN [org.jboss.mq.Connection] Connection failure: org.jboss.mq.SpyJMSException: Connection Failed at org.jboss.mq.Connection.asynchFailure(Connection.java:603) at org.jboss.mq.Connection$PingTask.run(Connection.java:1187) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java :36 4) at java.lang.Thread.run(Thread.java:536) linked exception is: java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:126) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:69) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:127) at java.io.ObjectOutputStream$BlockDataOutputStream.flush(ObjectOutputStream .ja va:1583) at java.io.ObjectOutputStream.flush(ObjectOutputStream.java:639) at org.jboss.mq.il.oil.OILServerIL.waitAnswer(OILServerIL.java:520) at org.jboss.mq.il.oil.OILServerIL.ping(OILServerIL.java:395) at org.jboss.mq.Connection.pingServer(Connection.java:1021) at org.jboss.mq.Connection$PingTask.run(Connection.java:1183) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java :36 4) at java.lang.Thread.run(Thread.java:536) 2002-07-24 09:32:07,466 WARN
RE: [JBoss-user] Fwd: RE: using log4J with JBoss and Cactus
Scott, Ceki, group,
The only difference between the org.apache.log4j.FileAppender and
org.jboss.logging.appender.FileAppender is that ours will create
missing directories in the File attribute path.
This is an enhancement that I and others on the log4j list have suggested.
Perhaps, as it is already in the public domain,
org.jboss.logging.appender.FileAppender or a suitable modification of it
might be submitted to the log4j project for inclusion in the standard
distribution? Just a thought...
- Matt Munz
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Scott M
Stark
Sent: Thursday, July 25, 2002 2:24 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Fwd: RE: using log4J with JBoss and Cactus
This is not true. I am able to send a given category to a seperate log
using the org.apache.log4j.FileAppender. The only difference between
the org.apache.log4j.FileAppender and
org.jboss.logging.appender.FileAppender
is that ours will create missing directories in the File attribute path. If
the File he was using corresponds to a path that does not exist then our
appender would behave differently.
log4j:configuration xmlns:log4j=http://jakarta.apache.org/log4j/;
debug=false
...
appender name=TEST class=org.apache.log4j.FileAppender
param name=File value=${jboss.server.home.dir}/log/tests.log/
param name=Append value=false/
layout class=org.apache.log4j.PatternLayout
param name=ConversionPattern value=%d %-5p [%c] %m%n/
/layout
/appender
category name=org.jboss.deployment additivity=false
priority value=DEBUG/
appender-ref ref=TEST/
/category
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Ceki Gülcü [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 25, 2002 8:04 AM
Subject: [JBoss-user] Fwd: RE: using log4J with JBoss and Cactus
Greetings,
Paul Ekeland, a JBoss, Cactus as well as log4j user recently posted
the following to the log4j-user@ mailing list. As I understand it, he
claims
that one has to use org.jboss.logging.appender.FileAppender instead of
org.apache.log4j.FileAppender under JBoss. Is this true? If so why is
this? Many thanks in advance,
---
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
---
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] MDB Deployment Security Exception
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 the MDB but honestly I dont think I should even need that by default. As I understand it the DLQHander gets created on the MDB deployment. Is this an issue in configuration (DLQ does not seem to have an explicit deployment section) Any help would be appreciated Thanks -=Brian Exception im getting 11:59:27,988 INFO [EjbModule] Deploying DomainEventListner 11:59:28,498 WARN [JMSContainerInvoker] JMS provider failure detected: javax.jms.JMSSecurityException: User: null is NOT authenticated at org.jboss.mq.security.SecurityManager.authenticate(SecurityManager.java:181) at org.jboss.mq.security.ServerSecurityInterceptor.authenticate(ServerSecurityInterceptor.java:40) at org.jboss.mq.server.TracingInterceptor.authenticate(TracingInterceptor.java:575) at org.jboss.mq.server.JMSServerInvoker.authenticate(JMSServerInvoker.java:288) at org.jboss.mq.il.jvm.JVMServerIL.authenticate(JVMServerIL.java:302) at org.jboss.mq.Connection.authenticate(Connection.java:759) at org.jboss.mq.Connection.init(Connection.java:233) at org.jboss.mq.Connection.init(Connection.java:264) at org.jboss.mq.SpyConnection.init(SpyConnection.java:59) at org.jboss.mq.SpyConnectionFactory.createQueueConnection(SpyConnectionFactory.java:96) at org.jboss.ejb.plugins.jms.DLQHandler.create(DLQHandler.java:131) ( rest of big huge honking exception goes here ) My Beans ejb-jar.xml is defined as message-driven description![CDATA[Message processor for the domainRegistration requests.]]/description ejb-nameDomainEventListner/ejb-name ejb-classcom.flytechnology.server.ejb.listeners.domain.DomainEventListner/ejb-class transaction-typeContainer/transaction-type acknowledge-modeAuto-acknowledge/acknowledge-mode message-driven-destination destination-typejavax.jms.Queue/destination-type subscription-durabilityNonDurable/subscription-durability /message-driven-destination /message-driven ---and i have even added a permissions role to ejb-jar.xml method-permission descriptiondescription not supported yet by ejbdoclet/description role-namesubscriber/role-name method descriptiondescription not supported yet by ejbdoclet/description ejb-nameDomainEventListner/ejb-name method-name*/method-name /method /method-permission --- my jboss.xml entry looks like message-driven ejb-nameDomainEventListner/ejb-name destination-jndi-name queue/DomainEventQueue /destination-jndi-name /message-driven ---The Queue is defined in the jbossmq-destinations.xml file as mbean code=org.jboss.mq.server.jmx.Queue name=jboss.mq.destination:service=Queue,name=DomainEventQueue depends optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends depends optional-attribute-name=SecurityManagerjboss.mq:service=SecurityManager/depends attribute name=SecurityConf security role name=guest read=true write=true/ role name=publisher read=true write=true create=false/ role name=subscriber read=true write=true create=false/ role name=noacc read=true write=true create=false/ /security /attribute /mbean - The jbossmq-state.xml is default that comes with the distribution --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] RE: [Xdoclet-user] CMR and value objects
Be very careful about autogenerating valueobject/dataobject. Let me summarize a pattern I came up with: - use one vo for one entity bean in ejb 1.1. xdoclet can generate everything for you. - in ejb2, 1-vo-1-ejb is not that useful, use local interfaces and start a UserTransaction in your base Action class in web tier. - Now if you are going to transfer some data for display/etc to a remote client (say a swing client) or you want to display some data in a web page and you don't want to do sophisticated traverses in ejbs or pass a huge graph of vo instances around then create a XyzListingRow class which is a simple flat class which only contains whatever the caller needs in the display. The attributes of this listing class are grabbed from a graph of entity objects. It's a one listing class - n ejbs mapping. Sure you should code it yourself and code generation doesn't help here, though it's possible but at least xdoclet doesn't provide it yet. An alternative approach is going to the db directly and filling the listing class without loading ejbs. It's useful for sophisticated queries. I tend to use this strategy for search operations that return tens of listing objects, but in some cases it's even useful for single object editing scenarios too. So even if valueobject//dataobject/ subtasks are provided by xdoclet but they are only for a one to one mapping of vo-ejbs. Don't let xdoclet dictate the architecture! Use code generation wisely :-) Ara. -Original Message- From: [EMAIL PROTECTED] [mailto:xdoclet-user- [EMAIL PROTECTED]] On Behalf Of Emerson Cargnin - SICREDI Serviços Sent: Thursday, July 25, 2002 12:31 AM To: David Ward Cc: Roland; [EMAIL PROTECTED]; jboss- [EMAIL PROTECTED] Subject: Re: [Xdoclet-user] CMR and value objects I think the worst problem when defining the approaches to vo's is what how deep you go in the relations. I mean, if i need just the main data of an entity or if I need the description of related entities in the same request, you have to find the trade-off to get the middle point of how many data will be sent for a request. We are creating a bank system that will run through satellite lines, about a 1 second delay between central (JBoss) and bank offices (700 with jboss/tomcat). That said, we had to create a way to avoid transmiting data that would not be used, and not having to make a lot of remote call to get all data to populate the view (struts too). We made a framework that works over a xml defining the data necessary for each remote call, so that in the server the framework navigates through the bean and generates an object of GenericVO class (basically a HashMap), then the client creates a concrete vo collection using this GenericVO. The business delegate will be used passing it a screen name and it specific parameters. example of the view xml : screenConfiguration screen name=SCR001 command name=getPraca fields field name=oid source=Oid/ field name=uf source=Municipio.Uf.Oid/ field name=municipio source=Municipio.Oid/ field name=endereco source=Endereco/ field name=cepInicial source=CepInicial/ field name=cepFinal source=CepFinal/ field name=situacao source=Situacao/ /fields /command /screen /screenConfiguration in this example the method getPraca will bring some PracaEJB fields, and some related fields, as Municipio.Uf.Oid that gets the MunicipioEJB relation from PracEJB, UFEJB relation from MunicipioEJB and at last Oid field from UFEJB. What you all think about this approach??? any sugestion, want more details of the solution ?? obs: sorry sending for jboss-user list, but i thought this subject coul'd be wanted there too. David Ward wrote: I suggest using xdoclet from cvs, then use @value-object tags in your ejb on the persistent fields and relationship fields you want included. Then, in your build.xml, use the valueobject/ and entitycmp/ tags. The valueobject tag will generate valueobjects for you that also handle aggregations/compositions of other valueobjects, with helpful add,remove,update methods. Then, the entitycmp tag will create an abstract subclass of your ejb that has similar helpful methods to persist your valueobject data (including traversing relationships). Just make sure to make abstract methods with @ejb:interface-method on them in your ejb so you can make use of them from your session facade. Hope this helps, David -- Roland wrote: Hello, Is there a best practice/pattern for creating value objects for entities with CMR fields/relationships?? I am migrating to CMP 2.0 and am having trouble deciding how to use value objects. That is, previously when I used our own relationship framework, we would have simple accessors for relationships. Now with CMP 2.0 we have local objects (and collections of local objects) as
Re: [jetty-discuss] Re: [JBoss-user] [Jetty] WARNING: HttpException(400,Bad Request, Missing Content)
The simple answer is that Jetty was expecting more bytes to be in the body of the POST than it actually got from the client using a persistent connection. To look much further than this you should enable more verbose Jetty logging and you should be able to inspect the full request to see if there is a problem with the content-length in the request header or whether the client has simply closed the connection unexpectedly. Brett On Thu, 25 Jul 2002, Jules Gosnell wrote: I'm forwarding you to jetty-discuss: Jules Alex Loubyansky wrote: Hello guys, sometimes I meet the following warning: WARN [Jetty] WARNING: POST /some-url/ HTTP/1.1 HttpException(400, Bad Request, Missing Content) Other times this same page is processed without it. All updates are done correctly in both cases. What does this warning mean? TIA --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging with Jboss 3.0
Ahh, thanks! On Thu, 2002-07-25 at 02:10, Alex Loubyansky wrote: Hello Ryan, JBoss uses log4j for logging. All you need is to have a Category variable in your class and configure logging if neccessary in log4j.xml. alex Thursday, July 25, 2002, 9:47:33 AM, you wrote: RM Is there a best practice for having my application output to the jboss RM logs? I haven't been able to find an docs or archived list threads on RM printing to the jboss logs in 3.0. RM -ryan -- Best regards, Alex Loubyansky -- Humans are the unfortunate result of a local maximum in the fitness landscape. www.ryanmarsh.com --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jboss 3 with ORACLE 8.0.5+
Hi I haven't specifically configured with Oracle but did this with MySQL and MS-SQL servers. The procedure is just the same! You just have to modify the oracle-service.xml that comes with JBoss 3 (JBOSS DIR\docs\examples\jca ) and deploy this file in you deployment directory (JBOSS DIR\server\default\deploy if you use the default config). Make sure you got the Oracle JDBC drivers in JBOSS DIR\server\default\lib directory. Mak - Original Message - From: Saroj Kumar [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 24, 2002 10:05 AM Subject: [JBoss-user] Jboss 3 with ORACLE 8.0.5+ Hi All, I want to know all the steps required to configure ORACLE 8+/8i/9i to work with JBOSS3. It would be better if someone could explain the pre-requisites and necessary groundwork to be done to make it work. TIA, Saroj --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Sybase Errors with JBossCMP
Hi -
I am trying to deploy a very simple CMP bean which I created for an existing
table in our Sybase AS Enterprise 12 database. An exception is thrown every
time JBoss tries to check a connection in to the connection pool. This
exception happens when the bean is deployed and again when it is called.
Has anyone seen this error before/know how to deal with it? Thanks.
Robert
Here are the relevant details from the jboss log file:
2002-07-25 17:05:38,707 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.validityBean] Initializing
CMP plugin for validityBean
2002-07-25 17:05:38,757 DEBUG
[org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.validityBean] Loading
standardjbosscmp-jdbc.xml :
file:/C:/jboss-3.0.0/server/default/conf/standardjbosscmp-jdbc.xml
2002-07-25 17:05:38,977 DEBUG
[org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool:
registering pool with interval 90 old interval: 9223372036854775807
2002-07-25 17:05:38,977 DEBUG
[org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool:
about to notify thread: old next: 1027642388977, new next: 1027642388977
2002-07-25 17:05:38,977 DEBUG
[org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using
properties: {user=rmartin, password=firstq}
2002-07-25 17:05:38,977 DEBUG
[org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory]
Checking driver for URL: jdbc:sybase:Tds:fqbackup:4100/fqdata
2002-07-25 17:05:38,987 DEBUG
[org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Driver
not yet registered for url: jdbc:sybase:Tds:dbserver:4100/data
2002-07-25 17:05:39,077 DEBUG
[org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Driver
not yet registered for url: jdbc:sybase:Tds:dbserver:4100/data
2002-07-25 17:05:39,207 DEBUG
[org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Driver
already registered for url: jdbc:sybase:Tds:dbserver:4100/data
2002-07-25 17:05:40,019 INFO
[org.jboss.resource.connectionmanager.JBossManagedConnectionPool]
ResourceException returning ManagedConnection to pool:
javax.resource.ResourceException: Could not cleanup:
com.sybase.jdbc2.jdbc.SybSQLException: SET CHAINED command not allowed
within multi-statement transaction.
at
org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.cleanup(LocalMa
nagedConnection.java:198)
at
org.jboss.resource.connectionmanager.InternalManagedConnectionPool.returnCon
nection(InternalManagedConnectionPool.java:137)
at
org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.ret
urnConnection(JBossManagedConnectionPool.java:324)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2.returnManagedCon
nection(BaseConnectionManager2.java:494)
at
org.jboss.resource.connectionmanager.LocalTxConnectionManager$LocalConnectio
nEventListener.connectionClosed(LocalTxConnectionManager.java:388)
at
org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.closeHandle(Loc
alManagedConnection.java:338)
at
org.jboss.resource.adapter.jdbc.local.LocalConnection.close(LocalConnection.
java:97)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCUtil.safeClose(JDBCUtil.java:58)
at
org.jboss.ejb.plugins.cmp.jdbc.SQLUtil.fixTableName(SQLUtil.java:69)
at
org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCEntityBridge.init(JDBCEntityBrid
ge.java:103)
at
org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java
:332)
at
org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.jav
a:155)
at org.jboss.ejb.EntityContainer.create(EntityContainer.java:337)
at org.jboss.ejb.Container.invoke(Container.java:789)
at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav
a:894)
at $Proxy6.create(Unknown Source)
at
org.jboss.system.ServiceController.create(ServiceController.java:272)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
cher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy19.create(Unknown Source)
at org.jboss.ejb.EjbModule.createService(EjbModule.java:392)
at
org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:134)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
cher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.jav
a:894)
at $Proxy6.create(Unknown Source)
at
