[JBoss-dev] CVS update: manual/src/xdocs/howto howtotimer.2.xml
User: schaefera Date: 02/01/21 01:50:10 Modified:src/xdocs/howto howtotimer.2.xml Log: Added Adam Heath path to the Scheduler Docu. Revision ChangesPath 3.3 +10 -9 manual/src/xdocs/howto/howtotimer.2.xml Index: howtotimer.2.xml === RCS file: /cvsroot/jboss/manual/src/xdocs/howto/howtotimer.2.xml,v retrieving revision 3.2 retrieving revision 3.3 diff -u -r3.2 -r3.3 --- howtotimer.2.xml 2002/01/20 14:10:42 3.2 +++ howtotimer.2.xml 2002/01/21 09:50:10 3.3 @@ -460,11 +460,11 @@ - When you want to use a Schedulalbe instance then you have to create a class with - implement the Schedulable interface. Then whenever an appropriate Time Notification - comes in, its perform method will be called. It contains two - parameters. The first is the time when the notification is sent and the second is the - number of remaining occurrencies (where -1 means no limit). + One way to use the Scheduler service is to provide a class that implements the + Schedulable interface. When the Scheduler receives a Notification from the Timer + it will call the Schedulable's perform() method. This method + takes 2 paramaters: the first is the time that the notification was sent; the second + is the number of the remain occurences(where -1 means no limit). The example coming with the Scheduler what a Schedulable class should look like is @@ -512,10 +512,11 @@ - When you want to use another MBean to be called by the Scheduler you must make - sure that the MBean is available to the JMX Agent of the JBoss server. It must be - loaded when the first call is made from the Scheduler otherwise the call wil not - be made but the number of repetitions will be decreased (if not endless). + The other way is to tell the Scheduler which method on which MBean schould be + called by the Scheduler service when it receives a Notification from the Timer. + The MBean must be loaded, created and started when the Scheduler calls the + MBean for the first time. If not available the Scheduler will count this call + (decrease the remaining repetitions if not endless) but the call is not performed. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] CVS update: manual/src/xdocs/howto howtotimer.2.xml
Hi Adam Thanx for your help. At least you were reading my docu. I think it is great when you review the docu and help to improve the documentation. Andy > On Sun, 20 Jan 2002, Andreas Schaefer wrote: > > > + > > + > > + > > + When you want to use a Schedulalbe instance then you have to create a class with > > + implement the Schedulable interface. Then whenever an appropriate Time Notification > > + comes in, its perform method will be called. It contains two > > + parameters. The first is the time when the notification is sent and the second is the > > + number of remaining occurrencies (where -1 means no limit). > > + > > There is a typo above, Schedulalbe -> Schedulable. Also, the first paragraph > is oddly worded. Below might be more appropriate. > > > When you want to use the Schedule service, then you have to create a class > that implements the Schedulable interface. Then whenever an appropriate > Timer Notification comes in, its perform method will > be called. This method takes 2 paramaters: the first is the time that the > notification was sent; the second is the number of remain occurences(where > -1 means no limit). > > > (note: this is not directed at just you, Andreas). > > There are other similiar issues with English wording in other parts of the > free documentation as well. Would it be helpful if I were to supply patches > to make the docs more correct? > > I can't give a timeframe on how often I would do such rewording. We(work) > haven't yet switched to 3.0 yet. We were discussing doing so, however, > because I've now started writing MBeans for everyone else, and 3.0 supports > hot-deploy of those. > > I'm also willing to send my patches thru proxies. By proxies I mean whowever > maintains the subsection of the code that is being documented, and that I am > modifying/fixing/patching. > > ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] More Scheduler Stuff
> -Message d'origine- > De: Andreas Schaefer [mailto:[EMAIL PROTECTED]] > I will add now the feature to the Scheduler to > call a MBean instead of a Schedulable class. > This would need two new attributes: > - setSchedulableMBean: JMX MBean name > - setSchedulableMBeanMethod: method name and what attributes > are to pass >which can be: >- 'Notification' the notification from the Timer >- 'Date' date of the call >- 'Repetitions' number of the remaining repetitions >- 'SchedulerName' MBean name of the Scheduler called >- any Datatype like 'java.lang.String' where a NULL will > be passed to (which will not work with basic data types) > > Any other suggestions or remarks ? this seems really cool. The Scheduler is an important tool in an enterprise app... crontab often does the job, but running inside jboss is an advantage One need I had was to call some of my own application EJB from the scheduler. (this would make the application less dependent on jboss, since an external crontab may call an EJB method itself) with your proposed architecture, one would only need to design a MBean that respect the schdulable mbean contract, and then should call a wellknown EJB. here is a discussion about HOW in my opinion an EJB should be called (what's your opinion on that?) : short version: I propose to support 2 kind of MBean to invoke an EJB periodicaly : 1- an MBean that calls a stateless session bean method. - the most simple would be to declare a home/remote interface globally, that the MBean could call, and the business session bean could implement. moreover thing could be easily ported to a n -there should exists a parameters in the MBean indicating wether to "queue", "ignore" or "invoke concurently" notifications calls that ovelap. 2- an MBean that send a JMS message to a message bean. - message content is not very important, so they will be either empty, constant text (a CDATA ?) or just contain the java.util.Date.toString of the notification date. - session factory and topic/destination will be found in JNDI - if someone want to change the content, either should he derive that MBean, or use a session bean that does the job... long version (arguments...): the most simple would be to call a stateless EJB. whether to reuse the same session bean or to create one each time is a performance and reliability (what if an EJB is undeployed meanwhile) issue. another issue is how to behave if one call takes much time, and if one call overlap another (overlap, queue, ignore)... calling a stateful EJB could seems useful if one want to parametrize the call... but deploying a new stateless session bean with diffrent env-entry does the same and is simpler. (so I think this is not usefull). calling an entity bean could be done for two distinc reasons - to parametrize the notification, with the same opinion as stateful session (ei: not very usefull) - to implement a kind of singleton and control concurent call to the notification method... one could implement this control in the stateless session bean, but as this is a common need, it would be practical to ease that. however my opinion is that the best place to do that is in the notification Mbean, or in the scheduler, that should be configurable to forbide reentry... calling a message bean through JMS could be a nice feature, because message bean invokation are naturally queued, and supports long operations. parameters is not really a problem since there are no essential parameters to be transmited... the mbean could refers to JNDI-stored JMS destinations and factory... for most application sending an empty message to a dedicated message bean, or sending a constant text message to a polyvalent message bean would do the job... sending the date could be useful in some rare cases, where the initial date of notification is important, because calls may be queued for a long time... but anyway if one want to generate complex JMS message one won't avoid writing code, either derivating the MBean, or writing a stateles session bean that send the JMS... for session bean the question could be also wether to depend on a static remote/home interface of to support dynamic calls... if we wan our application to be easily portable to a classic crontab of java thread system, the best would be to avoid dynamic invocation which is not perfect on some J2EE system... does it seems reasonable to you ? ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Re: The penny drops - JBoss Repository Selector
Hi Ceki, > >http://www.mail-archive.com/jboss-development@lists.sourceforge.net/msg10808.html > Thanks for the pointer. I was going to make these changes, but you've already provided the code :-) I think I said before, there are still some places that use Category directly. I'm changing these to use our Logger. NOTE for jboss-dev: I am aware of the bootstrap logger which didn't exist when Ceki provided this patch. Thanks again for help Ceki. Regards, Adrian _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] How to get specific build ?
JBoss Dev, I'm not sure where to post this message - but I'm sure someone in this group would know. I'd like to get a build of jboss-all for a specific date and time - in particular - a build with a good testsuite result - like the one on Saturday ( 1 error, 1 failure ) However - I'm a little unsure of how the builds are committed to the CVS repository and how those commits relate to the automatic testsuite runs. I did work out how to send a "date" parameter to the CVS server but it seems that the date I asked for didn't have a close match and I was given a version that was 12 hours older than that. A lot can happen in 12 hours :) Would someone explain to me how I would go about chasing a build ( or src tree or whatever is appropriate ) that corresponds to a particular testsuite ? Jason UitholData TechnologistDatacodeX Pty Ltd[EMAIL PROTECTED]http://www.datacodex.com
RE: [JBoss-dev] sun's j2ee-cas-com-bridge
On the J2EE CAS Bridge forum there are several messages which state that Sun is providing the source of the bridge to J2EE licensees. The Sun version of the bridge will never be released as 1.0. Despite some lobbying on my part, they refuse to open source the bridge as well. Anyway, this looks like another case where JBoss will be discriminated against because it is open source and thus not a J2EE licensee. -Original Message- From: Alexey Yudichev [mailto:[EMAIL PROTECTED]] Sent: Monday, January 21, 2002 1:30 AM To: [EMAIL PROTECTED] Subject: [JBoss-dev] sun's j2ee-cas-com-bridge As you know, sun released "Java 2 Platform, Enterprise Edition Client Access Services (J2EETM CAS) COM Bridge 1.0 Early Access" (http://developer.java.sun.com/developer/earlyAccess/j2eecas/download-com-br idge.html). They only support 4 or 5 leading EJB servers. They provide EJB server connectivity with some kind of win32 connector. They wrote such connectors for 5 servers mentioned above. Can anybody write such a connector for jboss? It will extend jBoss usage area to Windows COM clients. For now we have only 3rd-party jintegra (http://www.intrinsyc.com/products/bridging/jintegra.asp) bridge which costs a lot. Best wishes, Alexei Yudichev mailto:[EMAIL PROTECTED] ___ 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] org/jboss/web/catalina ajp13connector support
Title: org/jboss/web/catalina ajp13connector
support
I was wondering if there were a particular reason why
EmbeddedCatalinaServiceSX was written to support http and warp
connectors, but not Ajp13. I added an initAjpConnector method
which takes the default Embedded engine and then substitutes 'Ajp'
for 'Warp' for the connector-specific code, and this seems to work
(ie real .html files are displayed by Apache, fake ones are rejected
by Apache, real jsp files are displayed by Catalina, and fake ones
are rejected by Catalina). Was this support left out because
the tomcat folks call their ajp connector support beta and recommend
using warp? I'd use warp, but it doesn't seem to dig into war
files for web.xml, and jboss will only look in war files for web.xml
- I'd rather not have to support both. Also, Warp doesn't seem
to automatically deliver static content to Apache and dynamic content
to catalina, although that is a promised feature, and I can't direct
it to specifically serve all *.jsp files.
Should I be afraid of using Ajp?
Aaron
/* JBoss, the OpenSource EJB server
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
package org.jboss.web.catalina;
import java.io.InputStream;
import java.io.IOException;
import java.io.File;
import java.io.PrintWriter;
import java.net.UnknownHostException;
import java.net.URL;
import java.net.URLClassLoader;
import java.net.MalformedURLException;
import java.net.InetAddress;
import java.security.ProtectionDomain;
import java.util.HashMap;
import java.util.Iterator;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.servlet.ServletContext;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.xml.sax.EntityResolver;
import org.xml.sax.InputSource;
import org.jboss.deployment.DeploymentException;
import org.jboss.security.SecurityDomain;
import org.jboss.web.AbstractWebContainer;
import org.jboss.web.AbstractWebContainer.WebDescriptorParser;
import org.jboss.web.WebApplication;
import org.jboss.web.catalina.security.JBossSecurityMgrRealm;
import org.jboss.web.catalina.security.SSLServerSocketFactory;
import org.apache.log4j.Category;
import org.apache.log4j.Priority;
import org.apache.catalina.Connector;
import org.apache.catalina.Container;
import org.apache.catalina.Context;
import org.apache.catalina.Deployer;
import org.apache.catalina.Engine;
import org.apache.catalina.Host;
import org.apache.catalina.Lifecycle;
import org.apache.catalina.LifecycleEvent;
import org.apache.catalina.LifecycleException;
import org.apache.catalina.LifecycleListener;
import org.apache.catalina.Logger;
import org.apache.catalina.Realm;
import org.apache.catalina.Valve;
import org.apache.catalina.authenticator.AuthenticatorBase;
import org.apache.catalina.connector.http.HttpConnector;
import org.apache.catalina.connector.warp.WarpConnector;
import org.apache.catalina.connector.warp.WarpHost;
import org.apache.catalina.connector.warp.WarpEngine;
import org.apache.catalina.core.StandardContext;
import org.apache.catalina.loader.WebappClassLoader;
import org.apache.catalina.startup.Embedded;
import org.apache.ajp.tomcat4.*;
import org.apache.ajp.*;
/** An implementation of the AbstractWebContainer for the Jakarta
Tomcat
4.0 servlet container. This uses the Embedded as the integration
class. It
does not parse the catalina server.xml.
@see org.jboss.web.AbstractWebContainer
@see org.apache.catalina.startup.Embedded
@author [EMAIL PROTECTED]
@version $Revision: 1.2 $
*/
public class EmbeddedCatalinaServiceSX extends AbstractWebContainer
implements EmbeddedCatalinaServiceSXMBean
{
// Constants
-
public static final String NAME =
"EmbeddedCatalinaSX";
/** The embedded instance used to configure catalina
*/
private Embedded catalina;
/** The catalina host container */
private Host catalinaHost;
/** The catalina debug level */
private int debugLevel;
/** The port the web server listens on */
private int port = 8080;
/** The interface to bind to. This is useful for
multi-homed hosts
that want control over which
interfaces accept connections. */
private InetAddress bindAddress;
/** The accept count for this Connector. */
private int acceptCount = 10;
/** The "enable DNS lookups" flag. */
private boolean enableLookups = false;
/** The minimum number of processors to start at
initialization time. */
protected int minProcessors = 5;
/**The maximum number of processors allowed, or <0
for unlimited. */
private int maxProcessors = 20;
/** The JNDI name of the SecurityDomain implementation
binding */
private String securityDomain;
/** The type of connector that Tomcat will run (HTTP or
WARP or Ajp) */
private String connectorType = "http";
/** Any extended configuration information specified via
a conf
[JBoss-dev] [ jboss-Bugs-506549 ] jboss XADatasourceImpl scrollable rs pro
Bugs item #506549, was opened at 2002-01-21 09:54 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=506549&group_id=22866 Category: JBossCX Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mike Park (johnnycannuk) Assigned to: Nobody/Anonymous (nobody) Summary: jboss XADatasourceImpl scrollable rs pro Initial Comment: I'm using jboss2.4.4-tomcat4.0.1 on wint nt 4.0. I have code in my session bean for getting a dynamic list of records. Code looks like this con=this.getConnection();//private method for getting connections PreparedStatement ps=con.prepareStatement (sql,ResultSet.SCROLL_INSENSITIVE,ResultSet.CONCURR_UPD ATEABLE); ResultSet rs=ps.executeQuery(); rs.last(); When this is executed with the oracle datasource configured with the org.jboss.xsXADataSourceImpl (the default in the jcml) it returns a forward-only ResultSet instead of a scroll-insensitive one (like I asked for) I can fix this by changing to the OracleXADatasource class but this causes more problems (like I suddenly can't insert and get a wack of pl/sql errors). Funny, I just tested this again but the version from jboss.2.0_FINAL works fine with the XADataSourceImpl ... So is ther a patch or fix for this? Mike -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=506549&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/jetty/src/main/org/jboss/jetty/session ClusteredHttpSessionData.java ClusteredStore.java
User: jules_gosnell
Date: 02/01/21 13:58:13
Modified:jetty/src/main/org/jboss/jetty/session ClusteredStore.java
Added: jetty/src/main/org/jboss/jetty/session
ClusteredHttpSessionData.java
Log:
split out and publicise data object
move MBean use into an MBeanProxy instance - much easier
Revision ChangesPath
1.4 +16 -241
contrib/jetty/src/main/org/jboss/jetty/session/ClusteredStore.java
Index: ClusteredStore.java
===
RCS file:
/cvsroot/jboss/contrib/jetty/src/main/org/jboss/jetty/session/ClusteredStore.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- ClusteredStore.java 2002/01/19 00:49:50 1.3
+++ ClusteredStore.java 2002/01/21 21:58:13 1.4
@@ -5,198 +5,21 @@
* See terms of license at gnu.org.
*/
-// $Id: ClusteredStore.java,v 1.3 2002/01/19 00:49:50 jules_gosnell Exp $
+// $Id: ClusteredStore.java,v 1.4 2002/01/21 21:58:13 jules_gosnell Exp $
//
package org.jboss.jetty.session;
//
-
-import org.jboss.logging.Logger;
-import java.util.Map;
-import javax.naming.InitialContext;
-import java.net.InetAddress;
-
+import org.jboss.util.MBeanProxy;
import javax.management.*;
-import java.util.List;
-
-import org.jboss.ha.httpsession.interfaces.SerializableHttpSession;
-
-import javax.servlet.ServletContext;
-import javax.servlet.http.HttpSessionContext;
-import java.util.Enumeration;
+import javax.naming.InitialContext;
+import org.jboss.logging.Logger;
+import org.jboss.ha.httpsession.server.ClusteredHTTPSessionServiceMBean;
//
-
-
-class
- ClusteredHttpSessionData
- implements AbstractHttpSessionData, SerializableHttpSession
-{
- String _id;
- long_creationTime;
- long_lastAccessedTime;
- int _maxInactiveInterval;
- Map _attributes;
- boolean _attributesWerePassivated;
-
- // from javax.servlet.http.HttpSession
- public long
-getCreationTime()
-{
- return _creationTime;
-}
-
- public String
-getId()
-{
- return _id;
-}
-
- public long
-getLastAccessedTime()
-{
- return _lastAccessedTime;
-}
-
- public int
-getMaxInactiveInterval()
-{
- return _maxInactiveInterval;
-}
-
- public void
-setMaxInactiveInterval(int maxInactiveInterval)
-{
- _maxInactiveInterval=_maxInactiveInterval;
-}
-
- // extra accessors
- public Map
-getAttributes()
-{
- return _attributes;
-}
-
- public void
-setAttributes(Map attributes)
-{
- _attributes=attributes;
-}
-
- public void
-setId(String id)
-{
- _id=id;
-}
-
- public void
-setCreationTime(long creationTime)
-{
- _creationTime=creationTime;
-}
-
- public void
-setLastAccessedTime(long lastAccessedTime)
-{
- _lastAccessedTime=lastAccessedTime;
-}
-
- // extra attributes
- public boolean
-getAttributesWerePassivated()
-{
- return _attributesWerePassivated;
-}
-
- public void
-setAttributesWerePassivated(boolean attributesWerePassivated)
-{
- _attributesWerePassivated=attributesWerePassivated;
-}
-
- // extras that I don't want/need...
-
- public ServletContext
-getServletContext()
-{
- return null;
-}
-
- public HttpSessionContext
-getSessionContext()
-{
- return null;
-}
-
- public Object
-getAttribute(String name)
-throws IllegalStateException
-{
- return null;
-}
-
- public Enumeration
-getAttributeNames()
-throws IllegalStateException
-{
- return null;
-}
-
- public void
-setAttribute(String name, Object value)
-throws IllegalStateException
-{}
-
- public void
-removeAttribute(String name)
-throws IllegalStateException
-{}
- public Object
-getValue(String name)
-throws IllegalStateException
-{
- return getAttribute(name);
-}
-
- public String[]
-getValueNames()
-throws IllegalStateException
-{
- return null;
-}
-
- public void
-putValue(String name, Object value)
-throws IllegalStateException
-{}
-
- public void
-removeValue(String name)
-throws IllegalStateException
-{}
-
- public void
-invalidate()
-throws IllegalStateException
-{}
-
- public boolean
-isNew()
-throws IllegalStateException
-{
- return false;
-}
-
-
[JBoss-dev] [ jboss-Bugs-506549 ] jboss XADatasourceImpl scrollable rs pro
Bugs item #506549, was opened at 2002-01-21 09:54
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=506549&group_id=22866
Category: JBossCX
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Mike Park (johnnycannuk)
Assigned to: Nobody/Anonymous (nobody)
Summary: jboss XADatasourceImpl scrollable rs pro
Initial Comment:
I'm using jboss2.4.4-tomcat4.0.1 on wint nt 4.0. I
have code in my session bean for getting a dynamic
list of records. Code looks like this
con=this.getConnection();//private method for getting
connections
PreparedStatement ps=con.prepareStatement
(sql,ResultSet.SCROLL_INSENSITIVE,ResultSet.CONCURR_UPD
ATEABLE);
ResultSet rs=ps.executeQuery();
rs.last();
When this is executed with the oracle datasource
configured with the org.jboss.xsXADataSourceImpl
(the default in the jcml) it returns a forward-only
ResultSet instead of a scroll-insensitive one (like I
asked for)
I can fix this by changing to the OracleXADatasource
class but this causes more problems (like I suddenly
can't insert and get a wack of pl/sql errors).
Funny, I just tested this again but the version from
jboss.2.0_FINAL works fine with the
XADataSourceImpl ...
So is ther a patch or fix for this?
Mike
--
>Comment By: Mike Park (johnnycannuk)
Date: 2002-01-21 14:16
Message:
Logged In: YES
user_id=6289
Here is the patch that fixes this:
The old call to con.prepareStatement(sql,int,int)
was implemented like this:
public PreparedStatement prepareStatement(String sql, int
resultSetType, int resultSetConcurrency) throws
SQLException {
return this.prepareStatement(sql);
}
it should be like so:
public PreparedStatement prepareStatement(String sql, int
resultSetType, int resultSetConcurrency) throws
SQLException {
if(con == null) throw new SQLException(CLOSED);
try {
return con.prepareStatement(sql, resultSetType,
resultSetConcurrency);
} catch(SQLException e) {
setError(e);
throw e;
}
}
I have tested this out (although not with the test suite
and it works well.
I have included the minimally changed
XAClientConnection.java file
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=506549&group_id=22866
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Patches-506673 ] Fix for #506549 bug scrollable rs prob
Patches item #506673, was opened at 2002-01-21 14:22
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376687&aid=506673&group_id=22866
Category: JBossCX
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Mike Park (johnnycannuk)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix for #506549 bug scrollable rs prob
Initial Comment:
Here is the patch that fixes this:
The old call to con.prepareStatement(sql,int,int)
was implemented like this:
public PreparedStatement prepareStatement(String sql,
int resultSetType, int resultSetConcurrency) throws
SQLException {
return this.prepareStatement(sql);
}
it should be like so:
public PreparedStatement prepareStatement(String sql,
int resultSetType, int resultSetConcurrency) throws
SQLException {
if(con == null) throw new SQLException(CLOSED);
try {
return con.prepareStatement(sql,
resultSetType, resultSetConcurrency);
} catch(SQLException e) {
setError(e);
throw e;
}
}
I have tested this out (although not with the
testsuite) and it works well - seems like a simple
oversight considering the implementations of
prepareStatment() and prepareCall() around it were
done correctly.
I have included the minimally changed
XAClientConnection.java file
--
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376687&aid=506673&group_id=22866
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/jetty/src/resources/jetty-plugin/META-INF jboss-service.xml
User: jules_gosnell Date: 02/01/21 14:58:43 Modified:jetty/src/resources/jetty-plugin/META-INF jboss-service.xml Log: the gremlins seem to have chewed a hole in this - fixed Revision ChangesPath 1.11 +2 -6 contrib/jetty/src/resources/jetty-plugin/META-INF/jboss-service.xml Index: jboss-service.xml === RCS file: /cvsroot/jboss/contrib/jetty/src/resources/jetty-plugin/META-INF/jboss-service.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- jboss-service.xml 2002/01/20 15:12:58 1.10 +++ jboss-service.xml 2002/01/21 22:58:43 1.11 @@ -12,13 +12,8 @@ | environment. --> - + dummy - jetty.xml webdefault.xml true @@ -33,6 +28,7 @@ + --> ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] CVS update: contrib/jetty/src/main/org/jboss/jetty/session DistributedHttpSessionManager.java
User: jules_gosnell
Date: 02/01/21 14:59:56
Modified:jetty/src/main/org/jboss/jetty/session
DistributedHttpSessionManager.java
Log:
comment out Sacha's stuff for the moment since it causes a runtime, ClassNotFound.
He can comment it back in if he wants to play with it...
Revision ChangesPath
1.6 +4 -4
contrib/jetty/src/main/org/jboss/jetty/session/DistributedHttpSessionManager.java
Index: DistributedHttpSessionManager.java
===
RCS file:
/cvsroot/jboss/contrib/jetty/src/main/org/jboss/jetty/session/DistributedHttpSessionManager.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- DistributedHttpSessionManager.java2002/01/19 00:49:50 1.5
+++ DistributedHttpSessionManager.java2002/01/21 22:59:56 1.6
@@ -5,7 +5,7 @@
* See terms of license at gnu.org.
*/
-// $Id: DistributedHttpSessionManager.java,v 1.5 2002/01/19 00:49:50 jules_gosnell
Exp $
+// $Id: DistributedHttpSessionManager.java,v 1.6 2002/01/21 22:59:56 jules_gosnell
Exp $
// TODO
@@ -67,7 +67,7 @@
//--
/**
*
- * @version $Id: DistributedHttpSessionManager.java,v 1.5 2002/01/19 00:49:50
jules_gosnell Exp $
+ * @version $Id: DistributedHttpSessionManager.java,v 1.6 2002/01/21 22:59:56
jules_gosnell Exp $
* @author [EMAIL PROTECTED]
*/
//
@@ -78,8 +78,8 @@
static AbstractTimeOutManager_scavenger =new
NaiveTimeOutManager(5*1000, new MyTimeOutNotifier(), new MyTimeOutTester());
static { _scavenger.start(); }
- // final AbstractStore _store =new
CoarseDistributedStore();
- final AbstractStore _store =new ClusteredStore();
+ final AbstractStore _store =new
CoarseDistributedStore();
+ // final AbstractStore _store =new
ClusteredStore();
final Logger _log;
final JBossWebApplicationContext _context;
final ServletHandler _handler;
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
symbol : class J2eeDeploymentException
location: class org.jboss.deployment.Installer
throw new J2eeDeploymentException("no deployment descriptor ("+files[0]+",
"+files[1]+", "+files[2]+") found");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:485:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
dest = URLWizzard.downloadAndPackTemporary(src, factory.baseDir.toURL(),
"copy", ".zip");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:489:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
dest = URLWizzard.downloadTemporary(src, factory.baseDir.toURL(), "copy",
".zip");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:527:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
URL localURL = URLWizzard.downloadTemporary(lib, baseDir, "lib",
".jar");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:591:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.Installer
ObjectOutputStream out = new ObjectOutputStream(new FileOutputStream(new
File(baseDir, J2eeDeployer.CONFIG)));
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:94:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
File deployment = new File(files[i], J2eeDeployer.CONFIG);
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:166:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
result = loadConfig(new File(files[i], J2eeDeployer.CONFIG));
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:192:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
File dep = new File(files[i], J2eeDeployer.CONFIG);
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/ejb/EnterpriseContext.java:340:
warning: java.security.Identity in java.security has been deprecated
public boolean isCallerInRole(Identity id)
^
24 errors
4 warnings
BUILD FAILED
/disk/orig/home/lubega/jbossro/jboss-all/server/build.xml:385: Compile failed,
messages should have been provided.
Total time: 1 minute 25 seconds
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 69 Successful tests: 0 Errors:69 Failures: 0 [time of test: 22 January 2002 2:42 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-12] 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. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! 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 easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
symbol : class J2eeDeploymentException
location: class org.jboss.deployment.Installer
throw new J2eeDeploymentException("no deployment descriptor ("+files[0]+",
"+files[1]+", "+files[2]+") found");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:485:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
dest = URLWizzard.downloadAndPackTemporary(src, factory.baseDir.toURL(),
"copy", ".zip");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:489:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
dest = URLWizzard.downloadTemporary(src, factory.baseDir.toURL(), "copy",
".zip");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:527:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
URL localURL = URLWizzard.downloadTemporary(lib, baseDir, "lib",
".jar");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:591:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.Installer
ObjectOutputStream out = new ObjectOutputStream(new FileOutputStream(new
File(baseDir, J2eeDeployer.CONFIG)));
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:94:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
File deployment = new File(files[i], J2eeDeployer.CONFIG);
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:166:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
result = loadConfig(new File(files[i], J2eeDeployer.CONFIG));
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:192:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
File dep = new File(files[i], J2eeDeployer.CONFIG);
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/ejb/EnterpriseContext.java:340:
warning: java.security.Identity in java.security has been deprecated
public boolean isCallerInRole(Identity id)
^
24 errors
4 warnings
BUILD FAILED
/disk/orig/home/lubega/jbossro/jboss-all/server/build.xml:385: Compile failed,
messages should have been provided.
Total time: 54 seconds
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 69 Successful tests: 0 Errors:69 Failures: 0 [time of test: 22 January 2002 2:57 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-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-12] 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. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! 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 easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
symbol : class J2eeDeploymentException
location: class org.jboss.deployment.Installer
throw new J2eeDeploymentException("no deployment descriptor ("+files[0]+",
"+files[1]+", "+files[2]+") found");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:485:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
dest = URLWizzard.downloadAndPackTemporary(src, factory.baseDir.toURL(),
"copy", ".zip");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:489:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
dest = URLWizzard.downloadTemporary(src, factory.baseDir.toURL(), "copy",
".zip");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:527:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
URL localURL = URLWizzard.downloadTemporary(lib, baseDir, "lib",
".jar");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:591:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.Installer
ObjectOutputStream out = new ObjectOutputStream(new FileOutputStream(new
File(baseDir, J2eeDeployer.CONFIG)));
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:94:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
File deployment = new File(files[i], J2eeDeployer.CONFIG);
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:166:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
result = loadConfig(new File(files[i], J2eeDeployer.CONFIG));
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:192:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
File dep = new File(files[i], J2eeDeployer.CONFIG);
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/ejb/EnterpriseContext.java:340:
warning: java.security.Identity in java.security has been deprecated
public boolean isCallerInRole(Identity id)
^
24 errors
4 warnings
BUILD FAILED
/disk/orig/home/lubega/jbossro/jboss-all/server/build.xml:385: Compile failed,
messages should have been provided.
Total time: 2 minutes 12 seconds
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-506774 ] Topic messages not being release
Bugs item #506774, was opened at 2002-01-21 19:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=506774&group_id=22866 Category: JBossMQ Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jason Burton (jason73) Assigned to: Nobody/Anonymous (nobody) Summary: Topic messages not being release Initial Comment: The topic messages I am publishing are being held in memory by JBoss and never released. This eventually leads to an OutOfMemory error. Bug ID #478527 lists a duplicate problem to the one I am having. That bug was closed with no explanation or evaluation. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=506774&group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 69 Successful tests: 0 Errors:69 Failures: 0 [time of test: 22 January 2002 3:17 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] 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. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! 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 easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [AUTOMATED] JBoss compilation failed
=
==THIS IS AN AUTOMATED EMAIL - SEE http://www.lubega.com FOR DETAILS=
=
HERE ARE THE LAST 50 LINES OF THE LOG FILE
symbol : class J2eeDeploymentException
location: class org.jboss.deployment.Installer
throw new J2eeDeploymentException("no deployment descriptor ("+files[0]+",
"+files[1]+", "+files[2]+") found");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:485:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
dest = URLWizzard.downloadAndPackTemporary(src, factory.baseDir.toURL(),
"copy", ".zip");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:489:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
dest = URLWizzard.downloadTemporary(src, factory.baseDir.toURL(), "copy",
".zip");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:527:
cannot resolve symbol
symbol : variable URLWizzard
location: class org.jboss.deployment.Installer
URL localURL = URLWizzard.downloadTemporary(lib, baseDir, "lib",
".jar");
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/Installer.java:591:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.Installer
ObjectOutputStream out = new ObjectOutputStream(new FileOutputStream(new
File(baseDir, J2eeDeployer.CONFIG)));
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:94:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
File deployment = new File(files[i], J2eeDeployer.CONFIG);
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:166:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
result = loadConfig(new File(files[i], J2eeDeployer.CONFIG));
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/deployment/InstallerFactory.java:192:
cannot resolve symbol
symbol : variable J2eeDeployer
location: class org.jboss.deployment.InstallerFactory
File dep = new File(files[i], J2eeDeployer.CONFIG);
^
/disk/orig/home/lubega/jbossro/jboss-all/server/src/main/org/jboss/ejb/EnterpriseContext.java:340:
warning: java.security.Identity in java.security has been deprecated
public boolean isCallerInRole(Identity id)
^
24 errors
4 warnings
BUILD FAILED
/disk/orig/home/lubega/jbossro/jboss-all/server/build.xml:385: Compile failed,
messages should have been provided.
Total time: 1 minute 37 seconds
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 69 Successful tests: 0 Errors:69 Failures: 0 [time of test: 22 January 2002 3:37 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-12] 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. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! 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 easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] carry backtrace to client - use log4j in Proxy classes?
Hi, me again, the guy that wants client-side stack traces. I have a BacktraceCarrier class derived from ServerException that can be used to carry the RuntimeExceptions back to the client and print out a good stack trace by overriding the printStackTrace() methods. But I don't see a good way to handle application and library Exceptions that appear in throws clauses and catch blocks. The proxy can't throw a ServerException, because it needs to throw the same Application Exception that was thrown by the user application on the server. So I need to get the application Exception to print out a stack trace. I can't pass the Throwable.backtrace Object between JVMs, because it has pointers to native stuff. And even though I can know what the stack trace is supposed to look like I can't reconstruct a good Throwable.backtrace Object on the client side without writing native code, which would produce more of a maintenance headache than its worth I imagine. So here is what I'm thinking. When is enabled in jboss.xml, Go ahead and carry the stack trace as a String back to the client, and log the stack trace somewhere (using log4j). Is it ok to use log4j in the proxy classes on the client side, or does that add to the jar files that need to be in the client's CLASSPATH? - rick -- Richard Kilgore [EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Current HEAD
Hello All, I have just tried checking out the current code from CVS and there seems to be missing classes. Can anyone confirm this? One is called J2eeDeployer, another is URLWizzard. Also, the snapshot downloads links from the developers website do not work. Regards, Stephen. ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
