[JBoss-dev] CVS update: newsite/src/docs/common jboss-jbossmx.jsp
User: juhalindfors Date: 02/03/09 01:44:59 Modified:src/docs/common jboss-jbossmx.jsp Log: link to book source Revision ChangesPath 1.5 +2 -0 newsite/src/docs/common/jboss-jbossmx.jsp Index: jboss-jbossmx.jsp === RCS file: /cvsroot/jboss/newsite/src/docs/common/jboss-jbossmx.jsp,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- jboss-jbossmx.jsp 7 Mar 2002 15:56:56 - 1.4 +++ jboss-jbossmx.jsp 9 Mar 2002 09:44:59 - 1.5 @@ -23,6 +23,8 @@ discussed in the emJMX: Managing J2EE with Java Management Extensions/em. brbr a href=http://www.amazon.com/exec/obidos/ASIN/0672322889/104-0417757-3727125;Order a copy to support development./a + brbr + a href=http://www.samspublishing.com/content/images/0672322889/downloads/code.zip;Download book source code./a /td ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: [jetty-discuss] HTTP loadbalancing
Bill Burke wrote:
I'll be your buddy
OK Bud!
I've just checked in a skeleton load balancer into
Jetty/src1.4/org/mortbay/loadbalancer
It has all the nio network plumbing for two way connections with
flow control - but not very good exception handling at the moment.
A trivial round robin policy is used:
public class Policy
{
private Server[] _server;
private int next;
public Policy(Server[] server)
{
_server=server;
}
public void allocate(Connection connection)
throws IOException
{
next=(next+1)%_server.length;
connection.allocate(_server[next]);
}
}
Note that this Policy class does not even have the API to do
anything real can't look for jsessionid and fiddly to get the
InetAddress of the client but it is at least a start.
The nio stuff is really rather cool - I think I may take some
timeout from load balancing to write SocketChannelListener for
Jetty, which should be a big winner for scalability!!!
So Bill or other Buddies, please have a look at the code and we
can talk Policies soon!
I use the org.mortbay.tools.Tenlet (telnet backwards) class
as a sample server - so I can type back at a telnet client.
to run with 1 listener on 8123 and two servers you say:
java org.mortbay.loadbalancer.Balancer :8123 - 127.0.0.1: 127.0.0.1:
remember this is a release-early-release-often piece of code... be gentle :-)
cheers
PS. If another buddy wants to get in on the scene - we have to make the
thing JMX manageable!
cheers
--
Greg Wilkins[EMAIL PROTECTED] GB Phone: +44-(0)7092063462
Mort Bay Consulting Australia and UK.Mbl Phone: +61-(0)4 17786631
http://www.mortbay.com AU Phone: +61-(0)2 98107029
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jmx/src/main/org/jboss/mx/capability DispatcherFactory.java
User: biorn_steedom
Date: 02/03/09 03:04:12
Modified:src/main/org/jboss/mx/capability DispatcherFactory.java
Log:
Fixed Copy/Paste typo
Revision ChangesPath
1.4 +1 -1 jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java
Index: DispatcherFactory.java
===
RCS file:
/cvsroot/jboss/jmx/src/main/org/jboss/mx/capability/DispatcherFactory.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- DispatcherFactory.java8 Mar 2002 00:41:36 - 1.3
+++ DispatcherFactory.java9 Mar 2002 11:04:11 - 1.4
@@ -110,7 +110,7 @@
Descriptor desc = mmbAttribute.getDescriptor();
if (desc != null desc.getFieldValue(setMethod) != null)
{
- setter = mmap.lookupGetter(mmbAttribute);
+ setter = mmap.lookupSetter(mmbAttribute);
if (setter == null)
{
throw new IntrospectionException(no setter method found for
attribute: + attribute.getName());
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] IllegalAccessError from jetty-plugin.sar when bounced.....?
Thanks David, It seems happy now. I'll test it and check it in. Jules David Jencks wrote: I changed MainDeployer to undeploy from the outside in since it deploys from the inside out. I think this will at least make the classloaders get removed only after (outer) packages that might be using the classes have been completely destroyed. Let me know if it helps. david jencks On 2002.03.08 20:30:57 -0500 Jules Gosnell wrote: The problem only happens with the new code. The old service is constructed, JMX configuration calls are made on it. It stores the state of all of these, does nothing with createService(), creates and configures a Jetty instance in startService(), destroys the Jetty instance and cleans up in stopService() and does nothing with destroyService(). The new service constructs a Jetty instance when constructed, delegates all JMX config calls directly to it, thus avoiding holding any state itself, creates various things in createService(), starts Jetty in startService(), stops it in stopService() and destroys it and cleans up in destroyService(). In conclusion, the new service uses create/destroyService() where the old one did not. The JettyService is contained in and configured by the jetty-plugin.sar. The Jetty jar IS undeployed between stopService() and destroyService() (see log below) - is this correct ? 01:24:40,978 INFO [JettyService] Stopped 01:24:40,980 INFO [MainDeployer] not deleting localUrl, it is null or not a copy: njar:file:/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/server/default/tmp/deploy/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/deploy/jetty-plugin.sar/58.jetty-plugin.sar^/org.mortbay.jetty.jmx.jar 01:24:40,980 INFO [MainDeployer] Undeployed njar:file:/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/server/default/tmp/deploy/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/deploy/jetty-plugin.sar/58.jetty-plugin.sar^/org.mortbay.jetty.jmx.jar 01:24:40,984 INFO [MainDeployer] not deleting localUrl, it is null or not a copy: njar:file:/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/server/default/tmp/deploy/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/deploy/jetty-plugin.sar/58.jetty-plugin.sar^/org.mortbay.jetty.jar 01:24:40,985 INFO [MainDeployer] Undeployed njar:file:/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/server/default/tmp/deploy/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/deploy/jetty-plugin.sar/58.jetty-plugin.sar^/org.mortbay.jetty.jar 01:24:40,986 INFO [JettyService] Destroying 01:24:40,998 ERROR [JettyService] could not destroy Jetty java.lang.IllegalAccessError: try to access method org.mortbay.http.HttpServer$ComponentEvent.init(Lorg/mortbay/http/HttpServer;Ljava/lang/Object;Lorg/mortbay/http/HttpServer$1;)V from class org.mortbay.http.HttpServer at org.mortbay.http.HttpServer.destroy(HttpServer.java:1214) Jules David Jencks wrote: On 2002.03.08 19:39:30 -0500 Jules Gosnell wrote: This could not be because the ClassLoader is being asked for a class that it no longer has the jar for - could it. That would be a ClassNotFound I don't know what is the relationship between JettyService and the jetty-plugin.sar? Same as now? It seems odd to me that the MainDeployer is trying to delete a file between stop and destroy steps. david jencks Jules Jules Gosnell wrote: Guys, I've just been refactoring some of the Jetty stuff, and it works fine except for one thing. The second undeploy/deploy (of the plugin) cycle barfs out trying to destroy Jetty with an IllegalAccessError. 23:59:31,861 INFO [MainDeployer] Undeploying file:/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/deploy/jetty-plugin.sar 23:59:31,863 INFO [JettyService] Stopping 23:59:31,867 INFO [Jetty] Stopped org.jboss.jetty.Jetty@7b40fe 23:59:31,867 INFO [JettyService] Stopped 23:59:31,868 INFO [MainDeployer] not deleting localUrl, it is null or not a copy: njar:file:/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/server/default/tmp/deploy/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/deploy/jetty-plugin.sar/58.jetty-plugin.sar^/org.mortbay.jetty.jmx.jar 23:59:31,869 INFO [MainDeployer] Undeployed njar:file:/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/server/default/tmp/deploy/home/jules/cvs/JBoss/3.0/build/output/jboss-3.0.0beta2/deploy/jetty-plugin.sar/58.jetty-plugin.sar^/org.mortbay.jetty.jmx.jar 23:59:31,870 INFO [MainDeployer] not deleting localUrl, it is null or not a copy:
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/rollinglogged PersistenceManager.java
User: chirino
Date: 02/03/09 07:32:34
Modified:src/main/org/jboss/mq/pm/rollinglogged
PersistenceManager.java
Log:
Added some more logic so that you can undeploy a queue or topic. Still needs work
on the recovery side. Queue recovery will only happen the first time the queue is
deployed.
Revision ChangesPath
1.21 +9 -1
jbossmq/src/main/org/jboss/mq/pm/rollinglogged/PersistenceManager.java
Index: PersistenceManager.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/rollinglogged/PersistenceManager.java,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- PersistenceManager.java 27 Feb 2002 09:24:25 - 1.20
+++ PersistenceManager.java 9 Mar 2002 15:32:34 - 1.21
@@ -39,7 +39,7 @@
*
* @author David Maplesden ([EMAIL PROTECTED])
* @author a href=mailto:[EMAIL PROTECTED];David Jencks/a
- * @version$Revision: 1.20 $
+ * @version$Revision: 1.21 $
*/
public class PersistenceManager
extends ServiceMBeanSupport
@@ -826,6 +826,14 @@
this.log = log;
}
}
+
+ /*
+* @see PersistenceManager#closeQueue(JMSDestination, SpyDestination)
+*/
+ public void closeQueue(JMSDestination jmsDest, SpyDestination dest) throws
JMSException
+ {
+ // TODO: Do we need to cleanup anything when a queue get's closed?
+ }
}
/*
vim:tabstop=3:et:shiftwidth=3
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/jdbc PersistenceManager.java
User: chirino
Date: 02/03/09 07:32:34
Modified:src/main/org/jboss/mq/pm/jdbc PersistenceManager.java
Log:
Added some more logic so that you can undeploy a queue or topic. Still needs work
on the recovery side. Queue recovery will only happen the first time the queue is
deployed.
Revision ChangesPath
1.16 +9 -1 jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManager.java
Index: PersistenceManager.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/jdbc/PersistenceManager.java,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- PersistenceManager.java 15 Feb 2002 20:59:52 - 1.15
+++ PersistenceManager.java 9 Mar 2002 15:32:34 - 1.16
@@ -36,7 +36,7 @@
*
* @author: Jayesh Parayali ([EMAIL PROTECTED])
*
- * @version $Revision: 1.15 $
+ * @version $Revision: 1.16 $
*/
public class PersistenceManager extends ServiceMBeanSupport implements
PersistenceManagerMBean, org.jboss.mq.pm.PersistenceManager {
@@ -386,6 +386,14 @@
messageLog.remove(message, txId);
}
}
+ }
+
+ /*
+* @see PersistenceManager#closeQueue(JMSDestination, SpyDestination)
+*/
+ public void closeQueue(JMSDestination jmsDest, SpyDestination dest) throws
JMSException
+ {
+ // TODO: Do we need to cleanup anything when a queue get's closed?
}
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm PersistenceManager.java
User: chirino
Date: 02/03/09 07:32:33
Modified:src/main/org/jboss/mq/pm PersistenceManager.java
Log:
Added some more logic so that you can undeploy a queue or topic. Still needs work
on the recovery side. Queue recovery will only happen the first time the queue is
deployed.
Revision ChangesPath
1.5 +4 -1 jbossmq/src/main/org/jboss/mq/pm/PersistenceManager.java
Index: PersistenceManager.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/PersistenceManager.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- PersistenceManager.java 10 Nov 2001 21:38:03 - 1.4
+++ PersistenceManager.java 9 Mar 2002 15:32:33 - 1.5
@@ -27,7 +27,7 @@
* @author Hiram Chirino ([EMAIL PROTECTED])
* @author Paul Kendall ([EMAIL PROTECTED])
* @createdAugust 16, 2001
- * @version$Revision: 1.4 $
+ * @version$Revision: 1.5 $
*/
public interface PersistenceManager {
@@ -109,6 +109,9 @@
*/
public void remove( MessageReference message, Tx txId )
throws javax.jms.JMSException;
+
+ public void closeQueue(JMSDestination jmsDest, SpyDestination dest)
+ throws javax.jms.JMSException;
/**
* @param server org.jboss.mq.server.JMSServer
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/server BasicQueue.java DestinationManager.java JMSDestination.java JMSQueue.java JMSServer.java JMSTopic.java QueueManager.java TopicManager.java
User: chirino
Date: 02/03/09 07:32:34
Modified:src/main/org/jboss/mq/server BasicQueue.java
DestinationManager.java JMSDestination.java
JMSQueue.java JMSServer.java JMSTopic.java
QueueManager.java TopicManager.java
Log:
Added some more logic so that you can undeploy a queue or topic. Still needs work
on the recovery side. Queue recovery will only happen the first time the queue is
deployed.
Revision ChangesPath
1.15 +7 -1 jbossmq/src/main/org/jboss/mq/server/BasicQueue.java
Index: BasicQueue.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/server/BasicQueue.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- BasicQueue.java 9 Mar 2002 06:09:32 - 1.14
+++ BasicQueue.java 9 Mar 2002 15:32:34 - 1.15
@@ -36,7 +36,7 @@
* @author Norbert Lataille ([EMAIL PROTECTED])
* @author David Maplesden ([EMAIL PROTECTED])
* @createdAugust 16, 2001
- * @version$Revision: 1.14 $
+ * @version$Revision: 1.15 $
*/
//abstract public class BasicQueue implements Runnable {
public class BasicQueue {
@@ -145,6 +145,12 @@
} else {
((ClientConsumer)
sub.clientConsumer).removeRemovedSubscription(sub.subscriptionId);
}
+ }
+
+ public boolean isInUse() {
+ synchronized (receivers) {
+ return receivers.size()0;
+ }
}
public SpyMessage receive(Subscription sub, boolean wait) throws JMSException {
1.2 +9 -3 jbossmq/src/main/org/jboss/mq/server/DestinationManager.java
Index: DestinationManager.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/server/DestinationManager.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DestinationManager.java 6 Mar 2002 17:27:51 - 1.1
+++ DestinationManager.java 9 Mar 2002 15:32:34 - 1.2
@@ -23,7 +23,7 @@
* Super class for destination managers.
*
* @author a href=[EMAIL PROTECTED]Peter Antman/a
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*/
public class DestinationManager extends ServiceMBeanSupport
@@ -83,7 +83,7 @@
}
- protected void stopService() throws Exception
+ public void stopService() throws Exception
{
// unbind from JNDI
if (jndiBound) {
@@ -103,6 +103,12 @@
// Set securityConf at manager
getServer().invoke(securityManager,removeDestination, new
Object[]{spyDest.getName()}, new String[] {java.lang.String});
}
+
+ JMSServer jmsServer = (JMSServer)
+ server.getAttribute(jbossMQService, JMSServer);
+
+ jmsServer.closeDestination(spyDest);
+
log.warn(destination stop not yet fully implemented);
}
@@ -154,7 +160,7 @@
log.info(Bound to JNDI name: + jndiName);
}
-
+
/**
* Gets the JNDI name use by this topic
*
1.8 +5 -1 jbossmq/src/main/org/jboss/mq/server/JMSDestination.java
Index: JMSDestination.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/server/JMSDestination.java,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- JMSDestination.java 2 Feb 2002 03:54:21 - 1.7
+++ JMSDestination.java 9 Mar 2002 15:32:34 - 1.8
@@ -30,7 +30,7 @@
* @author Hiram Chirino ([EMAIL PROTECTED])
* @author David Maplesden ([EMAIL PROTECTED])
* @createdAugust 16, 2001
- * @version$Revision: 1.7 $
+ * @version$Revision: 1.8 $
*/
public abstract class JMSDestination {
@@ -77,6 +77,10 @@
public abstract void restoreMessage( MessageReference message );
public abstract void clientConsumerStopped( ClientConsumer clientConsumer );
+ public abstract boolean isInUse();
+
+ public abstract void close() throws JMSException;
+
/**
* @param req org.jboss.mq.AcknowledgementRequest
1.9 +21 -1 jbossmq/src/main/org/jboss/mq/server/JMSQueue.java
Index: JMSQueue.java
===
RCS file: /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/server/JMSQueue.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- JMSQueue.java 2 Feb 2002 03:54:21 - 1.8
+++ JMSQueue.java 9 Mar 2002 15:32:34 - 1.9
@@ -30,7 +30,7 @@
* @author Hiram Chirino ([EMAIL PROTECTED])
*
[JBoss-dev] CVS update: jbossmq/src/main/org/jboss/mq/pm/file PersistenceManager.java
User: chirino
Date: 02/03/09 07:32:34
Modified:src/main/org/jboss/mq/pm/file PersistenceManager.java
Log:
Added some more logic so that you can undeploy a queue or topic. Still needs work
on the recovery side. Queue recovery will only happen the first time the queue is
deployed.
Revision ChangesPath
1.21 +16 -1 jbossmq/src/main/org/jboss/mq/pm/file/PersistenceManager.java
Index: PersistenceManager.java
===
RCS file:
/cvsroot/jboss/jbossmq/src/main/org/jboss/mq/pm/file/PersistenceManager.java,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- PersistenceManager.java 27 Feb 2002 09:24:25 - 1.20
+++ PersistenceManager.java 9 Mar 2002 15:32:34 - 1.21
@@ -41,7 +41,7 @@
* persistence.
*
* @author Paul Kendall ([EMAIL PROTECTED])
- * @version$Revision: 1.20 $
+ * @version$Revision: 1.21 $
*/
public class PersistenceManager
extends ServiceMBeanSupport
@@ -838,4 +838,19 @@
}
}
}
+ /*
+* @see PersistenceManager#closeQueue(JMSDestination, SpyDestination)
+*/
+ public void closeQueue(JMSDestination jmsDest, SpyDestination dest) throws
JMSException
+ {
+ boolean debug = log.isDebugEnabled();
+ if (debug)
+ log.debug(closing destination: +dest);
+
+ // Cleanup all stuff we loaded/opened
+ String queueName = dest.toString();
+ LogInfo info = (LogInfo)messageLogs.remove(queueName);
+ unrestoredMessages.remove(queueName);
+ }
+
}
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Windows connection refused problem
Hi,
Quite a few people have reported a problem with
connection refused on windows when you hit JBoss with
lots of requests all at the same time.
Its bizarre, I don't see this problem on Linux.
I've tracked the problem to the way ServerSockets are
handled.
Parts of jboss does something like:
public void run()
{
socket = ServerSocket.accept();
listen();
doWork(socket);
}
public void listen()
{
Thread thread = new Thread(this);
thread.start();
}
But if you do the following the connection refused
mostly goes away.
public void run()
{
while(true)
{
socket = serverSocket.accept();
Thread thread = new Thread(new Worker(socket));
thread.start();
}
}
In my testing there is still a problem on windows
right at the very start when the work is intensive.
It looks like the JIT kicks in and the thread
doing the serverSocket.accept() doesn't get chance
to run before the backlog queue fills up.
The problem goes away after the first few requests.
org.jnp.server.Main does exactly what I've written above.
Some thread pooling would be nice :-)
I would like somebody else to verify my analysis.
I don't want to change what's working if the
problem is really elsewhere.
Regards,
Adrian
_
View thread online: http://main.jboss.org/thread.jsp?forum=66thread=10561
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Why is the jetty service now missing?
only the compilation needs the clustering i couldn't compile since i don't have the cluster compile yet so i removed everything because i needed to catch a plane and given what happened in boston i didn't want to fuck with the 'it doesnt build' situation again, so i made sure it compiled marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Jules |Gosnell |Sent: Friday, March 08, 2002 12:00 AM |To: David Jencks |Cc: [EMAIL PROTECTED] |Subject: Re: [JBoss-dev] Why is the jetty service now missing? | | |D |Guys, | |I'll sort this tonight - do not worry, it's trivial to remove the reliance |on clustering. | | |Jules | | | |avid Jencks wrote: | | From one of marcs commit messages: | | User: mnf999 | Date: 02/03/07 11:04:08 | | Modified:jbossbuild.xml | Log: | REMOVED JETTY UNTIL CLUSTER IS FIXED. | | THE BAD NEWS IS JULES WILL BE AT THE LONDON TRAINING, SO SOMEONE FROM | CLUSTER NEEDS TO FIX THAT OR SOMEONE FROM JETTY. SACHA WILL BE AT THE | TRAINING ALSO. | | SO IT IS UP TO BILL/SCOTT/GREGW | | | | On 2002.03.08 00:32:52 -0500 Scott M Stark wrote: | Why is the jetty service now missing from the default configuration? | | bin 1173ls ../server/default/conf/ | auth.conf jbossmq-state.xml server.policy | jboss-service.xml jbossmq-testsuite-service.xml standardjaws.xml | jboss.properties jndi.propertiesstandardjboss.xml | jbossmq-oldstate.xml log4j.xml | standardjbosscmp-jdbc.xml | bin 1174ls ../server/default/deploy/ | counter-service.xmljms-ra.rar | ejb-management.jar jms-service.xml | hsqldb-default-service.xml jmx-ejb-adaptor.jar | jboss-jdbc.rar jmx-ejb-connector-server.sar | jboss-xa.rar jmx-html-adaptor.sar | jbosscx.sarjmx-rmi-adaptor.sar | jbossmq-service.xmlmail-service.xml | jbossmq-state.xml scheduler-service.xml | jbossmq-testsuite-service.xml user-service.xml | | | Scott Stark | Chief Technology Officer | JBoss Group, LLC | | | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | https://lists.sourceforge.net/lists/listinfo/jboss-development | | | | ___ | Jboss-development mailing list | [EMAIL PROTECTED] | https://lists.sourceforge.net/lists/listinfo/jboss-development | | |_ |Do You Yahoo!? |Get your free @yahoo.com address at http://mail.yahoo.com | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results: 9-March-2002
huh? since i didn't do any testing before i left i didn't expect this to report so many succesful tests are we sure that this suite is working properly? marcf |-Original Message- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of |[EMAIL PROTECTED] |Sent: Friday, March 08, 2002 9:26 PM |To: [EMAIL PROTECTED] |Subject: [JBoss-dev] Automated JBoss Testsuite Results: 9-March-2002 | | | | |JBoss daily test results | |SUMMARY | |Number of tests run: 535 | | | |Successful tests: 509 | |Errors:21 | |Failures: 5 | | | | | |[time of test: 9 March 2002 5:25 GMT] |[java.version: 1.3.1_02] |[java.vendor: Sun Microsystems Inc.] |[java.vm.version: 1.3.1_02-b02] |[java.vm.name: Java HotSpot(TM) Server VM] |[java.vm.info: mixed mode] |[os.name: Linux] |[os.arch: i386] |[os.version: 2.4.9-31] | |See http://lubega.com for full details | |NOTE: If there are any errors shown above - this mail is only highlighting |them - it is NOT indicating that they are being looked at by anyone. |Remember - if a test becomes broken after your changes - fix it or |fix the test! | | | | | |DETAILS OF ERRORS | |[details not shown -as this makes the mail too big to reach the sf |mailing list] | | | | |PS BEFORE you commit, run the test suite! | |Its really is easy, just use the ant target 'run-basic-testsuite' from the |build directory. | | |To just run the unit tests (they are quite quick): | |In the testsuite directory, |./build.sh tests-unit | | |You can run a single test case using: |./build.sh -Dtest=[XXXTestCase] one-test | |The XXXTestCase is the classname of the junit class to run. So, to run the |EJBSpecUnitTestCase use: |./build.sh -Dtest=EJBSpecUnitTestCase one-test | | |To run all tests within a package, use |./build.sh -Dtest=[package] test | |The package is name of the directory under the org/jboss/test |directory that |contains the tests to run. So, to run the unit tests in the |org.jboss.test.security package use: |./build.sh -Dtest=security test | | | |Thanks for all your effort - we really do love you! | | | |___ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development | ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-527856 ] class loading problem during ear deploy
Bugs item #527856, was opened at 2002-03-09 18:50 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527856group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Raffaele Spazzoli (raffaelespazzol) Assigned to: Nobody/Anonymous (nobody) Summary: class loading problem during ear deploy Initial Comment: when I deploy an application that uses log4j.jar I receive the following error: [ERROR,Default] log4j:ERROR A org.jboss.logging.log4j.ConsoleAppender object is not assignable to a org.apache.log4j.Appender variable. [ERROR,Default] log4j:ERROR Could not instantiate appender named Console. the log4j.jar is bundled in the ear file under the directory /lib and the jars that uses it refer to it by the ClassPath entry in the Manifest file. Furthermore the log4j.jar is bundled under the WEB-INF/lib directory in the war file. I've strong suspect that the error is due to the presence of the log4j file in the war archive. I know that I don't need to include the log4j file when executing in the jboss environment but we are trying to make general ear file, and anyway jboss should try to be as coherent to the specification as possible. The specification says that every ear should be able to use his own classes in is own version indipendently from what happen for other application hosted in the same container. If this can be useful to resolve the problem I include the same version of log4j as the one that came with jboss and I use catalina embedded in jboss -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527856group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Automated JBoss Testsuite Results: 9-March-2002
Hi, --- marc fleury [EMAIL PROTECTED] wrote: are we sure that this suite is working properly? Looks good to me - the cvs update bit patched some files - so the latest code should be there. Everything looks fairly ok... Chris = Need somewhere to Live in London? - Then go to http://freeflats.com __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] MBeanProxy
Hi Geeks After having some hot dicussions I came to the this conclusion: - after some tests I looks like MBeanProxy works as fast as direct JMX calls - the interfaces can be created by using XDoclet therefore you just have to add the Standard MBean interface on and then use it with the proxy Therefore MBeanProxy are a valid and maybe better solution than to use JMX direct calls except you want to use get/setAttributes() methods. See ya x Andreas Schaefer Senior Consultant JBoss Group, LLC x ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-527876 ] Deployment order still wrong
Bugs item #527876, was opened at 2002-03-09 20:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527876group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Adrian Brock (ejort) Assigned to: Nobody/Anonymous (nobody) Summary: Deployment order still wrong Initial Comment: The deployment order is still broken for ears. I'm reporting it as a bug so others can monitor for the fix. To reproduce. 1) add an ear with a war inside to deploy/ 2) remove jetty-plugin.sar 3) rebuild The rebuilt Jetty is loaded after the ear, the war never gets deployed. Similar problems for other dependencies. Database and messaging. Regards, Adrian -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527876group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-527328 ] unexpected error in proxy compiler
Bugs item #527328, was opened at 2002-03-08 02:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527328group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Thomas Hamann (thomash76) Assigned to: Nobody/Anonymous (nobody) Summary: unexpected error in proxy compiler Initial Comment: win2000pro, jdk1.3.1_01, jboss3.0.0-beta2 (200203050840) Hi, this morning i checked out the current version of JBoss from CVS - the result is, my application which deployed successfully until yesterday, does not deploy. All i get is an exception: 10:32:41,585 ERROR [Proxies] unexpected error java.lang.VerifyError: (class: jatek/server/JaTeKGroupBean$Proxy, method: ejbSelectGroupMember signature: (JJ)Ljatek/ser ver/GroupMember;) Register pair 2/3 contains wrong type at java.lang.Class.getField0(Native Method) at java.lang.Class.getField(Class.java:826) at org.jboss.proxy.compiler.Runtime.makeProxyType(Runtime.java:71) at org.jboss.proxy.compiler.ProxyCompiler.init(ProxyCompiler.java:63) at org.jboss.proxy.compiler.Proxies$Impl.makeProxyConstructor(Proxies.java:716) at org.jboss.proxy.compiler.Proxies$Impl.newTarget(Proxies.java:589) at org.jboss.proxy.compiler.Proxies.newTarget(Proxies.java:62) at org.jboss.proxy.compiler.Proxy.newProxyInstance(Proxy.java:37) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateBeanClassInstanceCommand.init(JDBCCreateBeanClassI nstanceCommand.j ava:50) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createCreateBeanClassInstanceCommand(JDB CCommandFactory.jav a:97) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java:300) at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.java:134) at org.jboss.ejb.EntityContainer.create(EntityContainer.java:329) at org.jboss.ejb.Container.invoke(Container.java:723) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1003) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:720) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:248) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy3.create(Unknown Source) at org.jboss.ejb.EjbModule.createService(EjbModule.java:297) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:134) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:720) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:248) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy3.create(Unknown Source) at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:397) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:585) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:454) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy2.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:295) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:4 66) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:356) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeployme ntScanner.java:190) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymen tScanner.java:179) 10:32:42,569 ERROR [EntityContainer] Exception in service lifecyle
[JBoss-dev] [ jboss-Bugs-527328 ] unexpected error in proxy compiler
Bugs item #527328, was opened at 2002-03-08 02:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527328group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Thomas Hamann (thomash76) Assigned to: Nobody/Anonymous (nobody) Summary: unexpected error in proxy compiler Initial Comment: win2000pro, jdk1.3.1_01, jboss3.0.0-beta2 (200203050840) Hi, this morning i checked out the current version of JBoss from CVS - the result is, my application which deployed successfully until yesterday, does not deploy. All i get is an exception: 10:32:41,585 ERROR [Proxies] unexpected error java.lang.VerifyError: (class: jatek/server/JaTeKGroupBean$Proxy, method: ejbSelectGroupMember signature: (JJ)Ljatek/ser ver/GroupMember;) Register pair 2/3 contains wrong type at java.lang.Class.getField0(Native Method) at java.lang.Class.getField(Class.java:826) at org.jboss.proxy.compiler.Runtime.makeProxyType(Runtime.java:71) at org.jboss.proxy.compiler.ProxyCompiler.init(ProxyCompiler.java:63) at org.jboss.proxy.compiler.Proxies$Impl.makeProxyConstructor(Proxies.java:716) at org.jboss.proxy.compiler.Proxies$Impl.newTarget(Proxies.java:589) at org.jboss.proxy.compiler.Proxies.newTarget(Proxies.java:62) at org.jboss.proxy.compiler.Proxy.newProxyInstance(Proxy.java:37) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateBeanClassInstanceCommand.init(JDBCCreateBeanClassI nstanceCommand.j ava:50) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createCreateBeanClassInstanceCommand(JDB CCommandFactory.jav a:97) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java:300) at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.java:134) at org.jboss.ejb.EntityContainer.create(EntityContainer.java:329) at org.jboss.ejb.Container.invoke(Container.java:723) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1003) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:720) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:248) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy3.create(Unknown Source) at org.jboss.ejb.EjbModule.createService(EjbModule.java:297) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:134) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:720) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:248) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy3.create(Unknown Source) at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:397) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:585) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:454) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy2.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:295) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:4 66) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:356) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeployme ntScanner.java:190) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymen tScanner.java:179) 10:32:42,569 ERROR [EntityContainer] Exception in service lifecyle
[JBoss-dev] [ jboss-Bugs-527328 ] unexpected error in proxy compiler
Bugs item #527328, was opened at 2002-03-08 02:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527328group_id=22866 Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Thomas Hamann (thomash76) Assigned to: Nobody/Anonymous (nobody) Summary: unexpected error in proxy compiler Initial Comment: win2000pro, jdk1.3.1_01, jboss3.0.0-beta2 (200203050840) Hi, this morning i checked out the current version of JBoss from CVS - the result is, my application which deployed successfully until yesterday, does not deploy. All i get is an exception: 10:32:41,585 ERROR [Proxies] unexpected error java.lang.VerifyError: (class: jatek/server/JaTeKGroupBean$Proxy, method: ejbSelectGroupMember signature: (JJ)Ljatek/ser ver/GroupMember;) Register pair 2/3 contains wrong type at java.lang.Class.getField0(Native Method) at java.lang.Class.getField(Class.java:826) at org.jboss.proxy.compiler.Runtime.makeProxyType(Runtime.java:71) at org.jboss.proxy.compiler.ProxyCompiler.init(ProxyCompiler.java:63) at org.jboss.proxy.compiler.Proxies$Impl.makeProxyConstructor(Proxies.java:716) at org.jboss.proxy.compiler.Proxies$Impl.newTarget(Proxies.java:589) at org.jboss.proxy.compiler.Proxies.newTarget(Proxies.java:62) at org.jboss.proxy.compiler.Proxy.newProxyInstance(Proxy.java:37) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateBeanClassInstanceCommand.init(JDBCCreateBeanClassI nstanceCommand.j ava:50) at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createCreateBeanClassInstanceCommand(JDB CCommandFactory.jav a:97) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java:300) at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.java:134) at org.jboss.ejb.EntityContainer.create(EntityContainer.java:329) at org.jboss.ejb.Container.invoke(Container.java:723) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1003) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:720) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:248) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy3.create(Unknown Source) at org.jboss.ejb.EjbModule.createService(EjbModule.java:297) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:134) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:720) at $Proxy0.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:248) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy3.create(Unknown Source) at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:397) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:585) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:454) at java.lang.reflect.Method.invoke(Native Method) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:73) at $Proxy2.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:295) at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:4 66) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:356) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeployme ntScanner.java:190) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymen tScanner.java:179) 10:32:42,569 ERROR [EntityContainer] Exception in service lifecyle
Re: [JBoss-dev] [ jboss-Bugs-527328 ] unexpected error in proxy compiler
I tried to deploy your jar. As far as I can see your ejb-ql is missing an AND: ejb-ql![CDATA[SELECT OBJECT(owner) FROM AccountHolder owner WHERE owner.clientId = ?1 owner.createDate = ?2]]/ejb-ql just before the owner.createDate. The exception says: org.jboss.deployment.DeploymentException: Could not deploy file:/I:/jboss/jboss-3.0.0beta2/serve r/pmsystem/deploy/atmApplication2.jar; - nested throwable is: org.jboss.deployment.DeploymentExc eption: Error compiling ejbql; - nested throwable is: org.jboss.ejb.plugins.cmp.ejbql.ParseExcep tion: Encountered owner.createDate at line 1, column 79. Was expecting one of: EOF AND ... OR ... + ... - ... * ... / ... which is correct. HTH. Georg _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=10464 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [ jboss-Bugs-527328 ] unexpected error in proxy compiler
I forgot to mention: it seems this has nothing to do with the bug. The bug (527328) may be related to the new BCEL-based proxy compiler. Best regards Georg _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=10464 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] [ jboss-Bugs-527328 ] unexpected error in proxy compiler
EJB-QL error identified and corrected. Thanks for that. :) You and I must be using different build versions, as I did not get far enough to receive the error message that you received. Upon redeploy I still have the same issue with the bug. So I think my original concern pertains to the bug, and the EJB-QL statement error is not related to the bug. With the correction to the EJB-QL statement the bug is still reproducable on my computer. I also agree with your assessment on the changes to the proxy compiler. I did not encounter the issue until after the proxy compiler changes were made. And I don't have the foggiest idea about how that proxy compiler is supposed to work so I'm not touching it. :) _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=10464 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 10-March-2002
JBoss daily test results SUMMARY Number of tests run: 528 Successful tests: 353 Errors:154 Failures: 21 [time of test: 10 March 2002 0:32 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-527856 ] class loading problem during ear deploy
Bugs item #527856, was opened at 2002-03-09 18:50 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527856group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Closed Resolution: Postponed Priority: 5 Submitted By: Raffaele Spazzoli (raffaelespazzol) Assigned to: Nobody/Anonymous (nobody) Summary: class loading problem during ear deploy Initial Comment: when I deploy an application that uses log4j.jar I receive the following error: [ERROR,Default] log4j:ERROR A org.jboss.logging.log4j.ConsoleAppender object is not assignable to a org.apache.log4j.Appender variable. [ERROR,Default] log4j:ERROR Could not instantiate appender named Console. the log4j.jar is bundled in the ear file under the directory /lib and the jars that uses it refer to it by the ClassPath entry in the Manifest file. Furthermore the log4j.jar is bundled under the WEB-INF/lib directory in the war file. I've strong suspect that the error is due to the presence of the log4j file in the war archive. I know that I don't need to include the log4j file when executing in the jboss environment but we are trying to make general ear file, and anyway jboss should try to be as coherent to the specification as possible. The specification says that every ear should be able to use his own classes in is own version indipendently from what happen for other application hosted in the same container. If this can be useful to resolve the problem I include the same version of log4j as the one that came with jboss and I use catalina embedded in jboss -- Comment By: Adrian Brock (ejort) Date: 2002-03-10 00:38 Message: Logged In: YES user_id=9459 This has nothing to do with spec compliance. lo4j is a library. Not an application. JBoss currently uses log4j 1.1 which does not support seperate contexts for logging. The server and applications must share the logging environment. When log4j 1.2 reaches stable, we will implement the new RepositorySelector processing that allows the server and applications to have seperate logging contexts. This problem will then go away. If you want to monitor for this, please repost this as a feature request. Regards, Adrian -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527856group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Resourc adapter problems: ManagedConnectionFactoryProperties andManagedConnection.cleanup
Hi all, I have recently implemented a resource adapter for an XML database product, and deployed it to JBoss appserver (2.4.4). The thign I cannot seem to get to work is the ManagedConnectionFactoryProperties in the jcml code. I use the following: attribute name=ManagedConnectionFactoryProperties UserName=Administrator Password=secret DatabaseName=MyDatabase PropertiesURL=d:/xhive/bin/xhive.properties.default LogLevel=4 /attribute Are these supposed to overrule their config-property counterparts in ra.xml? Then this does not happen (the values in ra.xml are always chosen. The second problem is ManagedConnection cleanup. In section 5.8.3 of the connection spec it says that: The application server can also initiate cleanup of a ManagedConnection instance when the container terminates the application component instance that has the corresponding connec-tion handle. The application server should call ManagedConnection.cleanup to initiate the connection cleanup. After the cleanup, the application server puts the ManagedConnection in-stance into the pool to serve future allocation requests. This suggests that cleanup is called after I call remove on a bean that has a connection handle to my XML database through the resource adapter. However, when I log events on ManagedConnection, cleanup is never invoked. Also, whenever I remove a bean with still open connection handles, the next time I create such a bean, a new physical connection is always opened. The first question was posted one one of the forums before, but no reactions were posted. Thanks in advance, --Mark Polman-- ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 10-March-2002
JBoss daily test results SUMMARY Number of tests run: 528 Successful tests: 353 Errors:154 Failures: 21 [time of test: 10 March 2002 1:14 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20020124 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Resourc adapter problems: ManagedConnectionFactoryProperties and ManagedConnection.cleanup
There are at least 3 problems here: 1. You appear to be using config appropriate for jboss 3 in jboss 2.4. The corresponding attribute in 2.4.x is Properties. 2. AFAIK non-string properties are not handled [well] at the moment, so the 4 is apt to run into problems when you use the correct attribute name. 3. Currently jboss has a limitation that you MUST get a connection within a method call to your ejb and AFTER the transaction starts and you MUST close it before the transaction ends and before the method returns. I think perhaps you not doing one of these is causing the lack of cleanup calls on your managed connections. I'm currently working on a reimplementation of the ConnectionManager for jboss 3 that will remove this limitation. Then I'll fix (2), also for jboss 3. david jencks On 2002.03.10 05:01:52 -0500 Polman wrote: Hi all, I have recently implemented a resource adapter for an XML database product, and deployed it to JBoss appserver (2.4.4). The thign I cannot seem to get to work is the ManagedConnectionFactoryProperties in the jcml code. I use the following: attribute name=ManagedConnectionFactoryProperties UserName=Administrator Password=secret DatabaseName=MyDatabase PropertiesURL=d:/xhive/bin/xhive.properties.default LogLevel=4 /attribute Are these supposed to overrule their config-property counterparts in ra.xml? Then this does not happen (the values in ra.xml are always chosen. The second problem is ManagedConnection cleanup. In section 5.8.3 of the connection spec it says that: The application server can also initiate cleanup of a ManagedConnection instance when the container terminates the application component instance that has the corresponding connec-tion handle. The application server should call ManagedConnection.cleanup to initiate the connection cleanup. After the cleanup, the application server puts the ManagedConnection in-stance into the pool to serve future allocation requests. This suggests that cleanup is called after I call remove on a bean that has a connection handle to my XML database through the resource adapter. However, when I log events on ManagedConnection, cleanup is never invoked. Also, whenever I remove a bean with still open connection handles, the next time I create such a bean, a new physical connection is always opened. The first question was posted one one of the forums before, but no reactions were posted. Thanks in advance, --Mark Polman-- ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss-management - Imported sources
User: user57 Date: 02/03/09 17:50:28 Log: JBoss/Management module Status: Vendor Tag: jboss Release Tags: start N jboss-management/build.bat N jboss-management/build.sh N jboss-management/build.xml No conflicts created by this import ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: CVSROOT modules
User: user57 Date: 02/03/09 17:54:33 Modified:.modules Log: o hooked up JBoss/Management to jboss-all Revision ChangesPath 1.104 +2 -1 CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.103 retrieving revision 1.104 diff -u -r1.103 -r1.104 --- modules 10 Mar 2002 01:54:02 - 1.103 +++ modules 10 Mar 2002 01:54:33 - 1.104 @@ -108,7 +108,8 @@ _jboss_jetty \ _jboss_catalina \ _jboss_jboss.net \ -_jboss_iiop +_jboss_iiop \ +_jboss_management ## ## The JBoss website. This is the module used to generate/update ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: CVSROOT modules
User: user57 Date: 02/03/09 17:54:03 Modified:.modules Log: o Added module for JBoss/Management Revision ChangesPath 1.103 +1 -0 CVSROOT/modules Index: modules === RCS file: /cvsroot/jboss/CVSROOT/modules,v retrieving revision 1.102 retrieving revision 1.103 diff -u -r1.102 -r1.103 --- modules 2 Mar 2002 00:12:06 - 1.102 +++ modules 10 Mar 2002 01:54:02 - 1.103 @@ -60,6 +60,7 @@ _jboss_connector-d connectorjbosscx _jboss_j2ee -d j2ee jboss-j2ee _jboss_messaging-d messagingjbossmq +_jboss_management -d management jboss-management ## ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: build/jboss build.xml
User: user57
Date: 02/03/09 17:57:50
Modified:jbossbuild.xml
Log:
o added management module config (not hooked up to standard group yet)
o added example hook
Revision ChangesPath
1.106 +66 -1 build/jboss/build.xml
Index: build.xml
===
RCS file: /cvsroot/jboss/build/jboss/build.xml,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -r1.105 -r1.106
--- build.xml 9 Mar 2002 02:48:02 - 1.105
+++ build.xml 10 Mar 2002 01:57:49 - 1.106
@@ -12,7 +12,7 @@
!----
!-- == --
-!-- $Id: build.xml,v 1.105 2002/03/09 02:48:02 user57 Exp $ --
+!-- $Id: build.xml,v 1.106 2002/03/10 01:57:49 user57 Exp $ --
project default=main name=JBoss/Build
@@ -196,6 +196,7 @@
module name=jboss.net/
module name=catalina/
module name=iiop/
+ module name=management/
!-- Module groups --
@@ -218,6 +219,7 @@
admin,
jetty,
varia/
+!-- add management when src files are added --
!-- cluster, was removed add when proxy is fixed --
/group
@@ -1272,6 +1274,69 @@
mkdir dir=${install.api}/${_module.name}/
copy todir=${install.api}/${_module.name} filtering=no
fileset dir=${_module.output}/api
+ include name=**/*/
+ /fileset
+/copy
+ /target
+
+ !-- == --
+ !-- Management --
+ !-- == --
+
+ target name=_module-management-most
+property name=_module.name value=management override=true/
+property name=_module.output override=true
+ value=${project.root}/${_module.name}/output/
+
+!-- Copy the generated libraries --
+!-- FIXME
+mkdir dir=${install.lib}/
+copy todir=${install.lib} filtering=no
+ fileset dir=${_module.output}/lib
+ include name=jboss-management.jar/
+ /fileset
+/copy
+--
+
+!-- Copy the generated client libraries --
+!-- FIXME
+mkdir dir=${install.client}/
+copy todir=${install.client} filtering=no
+ fileset dir=${_module.output}/lib
+ include name=jboss-management-client.jar/
+ /fileset
+/copy
+--
+
+!-- Copy thirdparty code --
+!-- FIXME
+copy todir=${install.lib} filtering=no
+ fileset dir=${sun.jaxp.lib}
+include name=jaxp.jar/
+include name=crimson.jar/
+include name=xalan.jar/
+ /fileset
+ fileset dir=${sun.jmx.lib}
+include name=jmxri.jar/
+include name=jmxtools.jar/
+ /fileset
+/copy
+--
+ /target
+
+ target name=_module-management-all depends=_module-management-most
+!-- Copy the generated javadocs --
+mkdir dir=${install.api}/${_module.name}/
+copy todir=${install.api}/${_module.name} filtering=no
+ fileset dir=${_module.output}/api
+ include name=**/*/
+ /fileset
+/copy
+
+!-- Copy the generated todo docs --
+mkdir dir=${install.todo}/${_module.name}/
+copy todir=${install.todo}/${_module.name} filtering=no
+ fileset dir=${_module.output}/todo
include name=**/*/
/fileset
/copy
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 10-March-2002
JBoss daily test results SUMMARY Number of tests run: 528 Successful tests: 353 Errors:154 Failures: 21 [time of test: 10 March 2002 1:54 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1_02a-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-527979 ] No way invoke a CMP's method from client
Bugs item #527979, was opened at 2002-03-10 02:22 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527979group_id=22866 Category: JBossCMP Group: None Status: Open Resolution: None Priority: 5 Submitted By: bill (billprogra) Assigned to: Nobody/Anonymous (nobody) Summary: No way invoke a CMP's method from client Initial Comment: I current try the beta2 version in CVS, I deployed the jar file everything is file, tables created in database, corresponding SQL statements have been generated. When I triger the client programme, the Exception was found as below: java.lang.NullPointerException at org.jboss.proxy.ClientContainer.invoke (ClientContainer.java:96) at $Proxy0.create(Unknown Source) at mysqltest.Client.main(Client.java:42) If you want more detail please reference: http://main.jboss.org/thread.jsp?forum=47thread=10491 Thank you. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527979group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Deploying Dirs to Jetty ...
Christoph, From a cursory inspection of the Axis code, it should work as it is (ie by creating and populating a directory on the fly). The underlying Jetty instance certainly supports deployment of directories, as well as deployment of wars etc. So long as the AbstractWebContainer method performDeploy is passed the directory as the second argument (as it would seem to be), Jetty should be able to deploy it. BTW: The unpackWars flag is usually set to true because if the war contains JSPs then they work best when extracted (this flag would have no effect if it is a directory to be deployed). Is your question motivated by having tried a deployment and it didn't work? If so, a trace would be helpful. Jan is it (or should it) still be possible to deploy already extracted web-applications with Jetty? In version 1.53 of org.jboss.jetty.Jetty, there is a property called unpackWars (default set to true?) which seems to force Jetty to JarExtract every deployment it gets hold of ... Jboss.net currently relies on the fact that we can create web-inf deployment-descriptors (especially jboss-web.xml) from runtime configuration data (e.g., security configurations of the AxisService) and feed it into the WebContainer ... I have unfortunately no idea how to do that in an alternative, e.g., prepacked fashion as David proposed. Any help would be Appreciated. CGJ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jboss/src/etc/conf/default standardjboss.xml
User: d_jencks Date: 02/03/09 18:38:49 Modified:src/etc/conf/default standardjboss.xml Log: added client interceptors- hope these are all correct Revision ChangesPath 1.34 +259 -1jboss/src/etc/conf/default/standardjboss.xml Index: standardjboss.xml === RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/standardjboss.xml,v retrieving revision 1.33 retrieving revision 1.34 diff -u -r1.33 -r1.34 --- standardjboss.xml 15 Jan 2002 23:30:34 - 1.33 +++ standardjboss.xml 10 Mar 2002 02:38:48 - 1.34 @@ -7,7 +7,7 @@ !-- -- !-- = -- -!-- $Id: standardjboss.xml,v 1.33 2002/01/15 23:30:34 dsundstrom Exp $ -- +!-- $Id: standardjboss.xml,v 1.34 2002/03/10 02:38:48 d_jencks Exp $ -- jboss enforce-ejb-restrictionsfalse/enforce-ejb-restrictions @@ -27,6 +27,26 @@ interceptororg.jboss.ejb.plugins.EntitySynchronizationInterceptor/interceptor interceptororg.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor/interceptor /container-interceptors + client-interceptors + home + interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /home + bean + interceptororg.jboss.proxy.ejb.EntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /bean + list-entity + interceptororg.jboss.proxy.ejb.ListEntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /list-entity + /client-interceptors instance-poolorg.jboss.ejb.plugins.EntityInstancePool/instance-pool instance-cacheorg.jboss.ejb.plugins.EntityInstanceCache/instance-cache persistence-managerorg.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager/persistence-manager @@ -73,6 +93,26 @@ interceptororg.jboss.ejb.plugins.EntityInstanceInterceptor/interceptor interceptororg.jboss.ejb.plugins.EntitySynchronizationInterceptor/interceptor /container-interceptors + client-interceptors + home + interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /home + bean + interceptororg.jboss.proxy.ejb.EntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /bean + list-entity + interceptororg.jboss.proxy.ejb.ListEntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /list-entity + /client-interceptors instance-poolorg.jboss.ejb.plugins.EntityInstancePool/instance-pool instance-cacheorg.jboss.ejb.plugins.EntityInstanceCache/instance-cache persistence-managerorg.jboss.ejb.plugins.jaws.JAWSPersistenceManager/persistence-manager @@ -120,6 +160,26 @@ interceptororg.jboss.ejb.plugins.EntitySynchronizationInterceptor/interceptor interceptororg.jboss.ejb.plugins.cmp.jdbc.JDBCRelationInterceptor/interceptor /container-interceptors + client-interceptors + home + interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /home + bean + interceptororg.jboss.proxy.ejb.EntityInterceptor/interceptor +
Re: [JBoss-dev] Deploying Dirs to Jetty ...
Christoph, I've had a closer look at the Jetty code propmpted by your question, and I've found a bug in the deployment which will throw an exception if extractWars is true it is a directory that is being deployed. Fix is coming. Is your question motivated by having tried a deployment and it didn't work? If so, a trace would be helpful. Guess that won't be necessary :-) Jan ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/bmp/META-INF jboss.xml
User: d_jencks Date: 02/03/09 18:41:18 Modified:src/resources/bmp/META-INF jboss.xml Log: added client interceptors Revision ChangesPath 1.5 +21 -1 jbosstest/src/resources/bmp/META-INF/jboss.xml Index: jboss.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/bmp/META-INF/jboss.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- jboss.xml 3 Aug 2001 20:27:09 - 1.4 +++ jboss.xml 10 Mar 2002 02:41:18 - 1.5 @@ -5,7 +5,7 @@ container-configuration container-nameMy BMP EntityBean/container-name call-loggingfalse/call-logging - container-invokerorg.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker/container-invoker + container-invokerorg.jboss.proxy.ejb.ProxyFactory/container-invoker container-interceptors interceptororg.jboss.ejb.plugins.LogInterceptor/interceptor interceptororg.jboss.ejb.plugins.SecurityInterceptor/interceptor @@ -15,6 +15,26 @@ interceptororg.jboss.ejb.plugins.EntityInstanceInterceptor/interceptor interceptororg.jboss.ejb.plugins.EntitySynchronizationInterceptor/interceptor /container-interceptors + client-interceptors + home + interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /home + bean + interceptororg.jboss.proxy.ejb.EntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /bean + list-entity + interceptororg.jboss.proxy.ejb.ListEntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /list-entity + /client-interceptors instance-poolorg.jboss.ejb.plugins.EntityInstancePool/instance-pool instance-cacheorg.jboss.ejb.plugins.EntityInstanceCache/instance-cache persistence-managerorg.jboss.ejb.plugins.BMPPersistenceManager/persistence-manager ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-527979 ] No way invoke a CMP's method from client
Bugs item #527979, was opened at 2002-03-10 02:22 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527979group_id=22866 Category: JBossCMP Group: None Status: Closed Resolution: Fixed Priority: 5 Submitted By: bill (billprogra) Assigned to: David Jencks (d_jencks) Summary: No way invoke a CMP's method from client Initial Comment: I current try the beta2 version in CVS, I deployed the jar file everything is file, tables created in database, corresponding SQL statements have been generated. When I triger the client programme, the Exception was found as below: java.lang.NullPointerException at org.jboss.proxy.ClientContainer.invoke (ClientContainer.java:96) at $Proxy0.create(Unknown Source) at mysqltest.Client.main(Client.java:42) If you want more detail please reference: http://main.jboss.org/thread.jsp?forum=47thread=10491 Thank you. -- Comment By: David Jencks (d_jencks) Date: 2002-03-10 02:55 Message: Logged In: YES user_id=60525 Try again, I just fixed this, I think Bill forgot to check in the new client interceptor configurations yesterday. You need to update standardjboss.xml: I'm working on updating the necessary jboss.xml from the testsuite. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=527979group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 10-March-2002
JBoss daily test results SUMMARY Number of tests run: 528 Successful tests: 352 Errors:154 Failures: 22 [time of test: 10 March 2002 2:54 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-02a-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/web/META-INF jboss.xml
User: d_jencks Date: 02/03/09 19:08:20 Modified:src/resources/web/META-INF jboss.xml Log: added client interceptor config Revision ChangesPath 1.5 +14 -0 jbosstest/src/resources/web/META-INF/jboss.xml Index: jboss.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/web/META-INF/jboss.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- jboss.xml 21 Feb 2002 07:02:34 - 1.4 +++ jboss.xml 10 Mar 2002 03:08:20 - 1.5 @@ -38,6 +38,20 @@ interceptor transaction=Beanorg.jboss.ejb.plugins.TxInterceptorBMT/interceptor interceptor transaction=Bean metricsEnabled=trueorg.jboss.ejb.plugins.MetricsInterceptor/interceptor /container-interceptors + client-interceptors + home + interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /home + bean + interceptororg.jboss.proxy.ejb.StatelessSessionInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /bean + /client-interceptors instance-poolorg.jboss.ejb.plugins.StatelessSessionInstancePool/instance-pool instance-cache/instance-cache persistence-manager/persistence-manager ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/security-spec/META-INF jboss.xml
User: d_jencks Date: 02/03/09 19:08:20 Modified:src/resources/security-spec/META-INF jboss.xml Log: added client interceptor config Revision ChangesPath 1.4 +14 -0 jbosstest/src/resources/security-spec/META-INF/jboss.xml Index: jboss.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/security-spec/META-INF/jboss.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- jboss.xml 3 Mar 2002 07:41:28 - 1.3 +++ jboss.xml 10 Mar 2002 03:08:20 - 1.4 @@ -39,6 +39,20 @@ interceptor transaction=Beanorg.jboss.ejb.plugins.TxInterceptorBMT/interceptor interceptor transaction=Bean metricsEnabled=trueorg.jboss.ejb.plugins.MetricsInterceptor/interceptor /container-interceptors + client-interceptors + home + interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /home + bean + interceptororg.jboss.proxy.ejb.StatelessSessionInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /bean + /client-interceptors instance-poolorg.jboss.ejb.plugins.StatelessSessionInstancePool/instance-pool instance-cache/instance-cache persistence-manager/persistence-manager ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: jbosstest/src/resources/lock/META-INF jboss.xml
User: d_jencks Date: 02/03/09 19:08:20 Modified:src/resources/lock/META-INF jboss.xml Log: added client interceptor config Revision ChangesPath 1.5 +210 -9jbosstest/src/resources/lock/META-INF/jboss.xml Index: jboss.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/lock/META-INF/jboss.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- jboss.xml 9 Aug 2001 21:11:48 - 1.4 +++ jboss.xml 10 Mar 2002 03:08:20 - 1.5 @@ -17,6 +17,26 @@ interceptororg.jboss.ejb.plugins.EntityInstanceInterceptor/interceptor interceptororg.jboss.ejb.plugins.EntitySynchronizationInterceptor/interceptor /container-interceptors + client-interceptors + home + interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /home + bean + interceptororg.jboss.proxy.ejb.EntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /bean + list-entity + interceptororg.jboss.proxy.ejb.ListEntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /list-entity + /client-interceptors instance-poolorg.jboss.ejb.plugins.EntityInstancePool/instance-pool instance-cacheorg.jboss.ejb.plugins.EntityInstanceCache/instance-cache persistence-managerorg.jboss.ejb.plugins.jaws.JAWSPersistenceManager/persistence-manager @@ -49,7 +69,7 @@ container-configuration container-nameEntityBean_B/container-name call-loggingfalse/call-logging - container-invokerorg.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker/container-invoker + container-invokerorg.jboss.proxy.ejb.ProxyFactory/container-invoker container-interceptors interceptororg.jboss.ejb.plugins.LogInterceptor/interceptor interceptororg.jboss.ejb.plugins.SecurityInterceptor/interceptor @@ -59,6 +79,26 @@ interceptororg.jboss.ejb.plugins.EntityInstanceInterceptor/interceptor interceptororg.jboss.ejb.plugins.EntitySynchronizationInterceptor/interceptor /container-interceptors + client-interceptors + home + interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /home + bean + interceptororg.jboss.proxy.ejb.EntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /bean + list-entity + interceptororg.jboss.proxy.ejb.ListEntityInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /list-entity + /client-interceptors instance-poolorg.jboss.ejb.plugins.EntityInstancePool/instance-pool instance-cacheorg.jboss.ejb.plugins.EntityInstanceCache/instance-cache persistence-managerorg.jboss.ejb.plugins.jaws.JAWSPersistenceManager/persistence-manager @@ -91,7 +131,7 @@ container-configuration container-nameEntityBean_C/container-name call-loggingfalse/call-logging - container-invokerorg.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker/container-invoker + container-invokerorg.jboss.proxy.ejb.ProxyFactory/container-invoker container-interceptors interceptororg.jboss.ejb.plugins.LogInterceptor/interceptor interceptororg.jboss.ejb.plugins.SecurityInterceptor/interceptor @@ -101,6 +141,26 @@ interceptororg.jboss.ejb.plugins.EntityInstanceInterceptor/interceptor interceptororg.jboss.ejb.plugins.EntitySynchronizationInterceptor/interceptor /container-interceptors +
[JBoss-dev] CVS update: jbosstest/src/resources/security/META-INF jboss.xml
User: d_jencks Date: 02/03/09 19:08:20 Modified:src/resources/security/META-INF jboss.xml Log: added client interceptor config Revision ChangesPath 1.4 +14 -0 jbosstest/src/resources/security/META-INF/jboss.xml Index: jboss.xml === RCS file: /cvsroot/jboss/jbosstest/src/resources/security/META-INF/jboss.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- jboss.xml 9 Jul 2001 20:20:48 - 1.3 +++ jboss.xml 10 Mar 2002 03:08:20 - 1.4 @@ -30,6 +30,20 @@ interceptor transaction=Beanorg.jboss.ejb.plugins.TxInterceptorBMT/interceptor interceptor transaction=Bean metricsEnabled=trueorg.jboss.ejb.plugins.MetricsInterceptor/interceptor /container-interceptors + client-interceptors + home + interceptororg.jboss.proxy.ejb.HomeInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /home + bean + interceptororg.jboss.proxy.ejb.StatelessSessionInterceptor/interceptor + interceptororg.jboss.proxy.SecurityInterceptor/interceptor + interceptororg.jboss.proxy.TransactionInterceptor/interceptor + interceptororg.jboss.invocation.InvokerInterceptor/interceptor + /bean + /client-interceptors instance-poolorg.jboss.ejb.plugins.StatelessSessionInstancePool/instance-pool instance-cache/instance-cache persistence-manager/persistence-manager ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 10-March-2002
JBoss daily test results SUMMARY Number of tests run: 528 Successful tests: 353 Errors:154 Failures: 21 [time of test: 10 March 2002 3:48 GMT] [java.version: 1.3.1] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1-b24] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results: 10-March-2002
JBoss daily test results SUMMARY Number of tests run: 528 Successful tests: 352 Errors:154 Failures: 22 [time of test: 10 March 2002 4:41 GMT] [java.version: 1.3.1_02] [java.vendor: Sun Microsystems Inc.] [java.vm.version: 1.3.1_02-b02] [java.vm.name: Java HotSpot(TM) Server VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-31] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. Remember - if a test becomes broken after your changes - fix it or fix the test! DETAILS OF ERRORS [details not shown -as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite! Its really is easy, just use the ant target 'run-basic-testsuite' from the build directory. To just run the unit tests (they are quite quick): In the testsuite directory, ./build.sh tests-unit You can run a single test case using: ./build.sh -Dtest=[XXXTestCase] one-test The XXXTestCase is the classname of the junit class to run. So, to run the EJBSpecUnitTestCase use: ./build.sh -Dtest=EJBSpecUnitTestCase one-test To run all tests within a package, use ./build.sh -Dtest=[package] test The package is name of the directory under the org/jboss/test directory that contains the tests to run. So, to run the unit tests in the org.jboss.test.security package use: ./build.sh -Dtest=security test Thanks for all your effort - we really do love you! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: Loading classes from manifest
Thanks, I misunderstood the meaning of the Classpath in the manifest. -Cameron _ View thread online: http://main.jboss.org/thread.jsp?forum=66thread=5184 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Non blocking listener. was: HTTP loadbalancing
OK, I have added a java.nio listener to Jetty: org.mortbay.http.SocketChannelListener It has had very little testing, but appears to be working OK on my machine. If anybody has a big iron and something that can generate lot's of connections, it would be interesting to see what it does for performance. It should reduce the thread count significantly! This is java 1.4 only, so I can't move it to the JBoss repository until the build.sh knows how to handle optional 1.4 stuff. cheers Dan Christopherson wrote: This is maybe a bit offtopic, and a bit long, but this is one of those serindipitous occasions where a conversation strikes on something somebody else is already working on... Greg Wilkins wrote: + Use java.nio as: * if you care about performance you should be using jdk1.4 anyway * if you want one machine to handle more connections than the sum of all your servers, then java.net.ServerSocket aint going to do the job! * I want to play with nio before I write the NioListener for Jetty! -- Greg Wilkins[EMAIL PROTECTED] GB Phone: +44-(0)7092063462 Mort Bay Consulting Australia and UK.Mbl Phone: +61-(0)4 17786631 http://www.mortbay.com AU Phone: +61-(0)2 98107029 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Non blocking listener. was: HTTP loadbalancing
This is java 1.4 only, so I can't move it to the JBoss repository until the build.sh knows how to handle optional 1.4 stuff. I will try to have something working for this soon... perhaps early next week. --jason ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: [jetty-discuss] HTTP loadbalancing
I have now added client InetAddress stickyness, which is probably going to be good enough for 90% of cases. But for those that want session stickyness, I have now allow delayed server allocation and pass the queued data into the Policy. This will allow a search for jsessionId up until the queue is full (at which time you had better allocated or you will just block). Only thing lacking is a monitor of the response channel so you can pick up session cookie sets. I'm now going to stop on the balancing policy and concentrate on the network stuff. Still no decent exception handling. There is also a funny in the nio (at least on Linux), where I close the Channel, the socket, the inputstream, the outputstream, etc. and the client still does not see the closed connection until it tries to write another packet! Note good for HTTP/1.0! This only happens sometimes - and never in a test harness!?!?!?!?! cheers -- Greg Wilkins[EMAIL PROTECTED] GB Phone: +44-(0)7092063462 Mort Bay Consulting Australia and UK.Mbl Phone: +61-(0)4 17786631 http://www.mortbay.com AU Phone: +61-(0)2 98107029 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
