[JBoss-dev] [ jboss-Bugs-601097 ] Race cond in QueuedPessimisticEJBLock

2002-08-28 Thread noreply

Bugs item #601097, was opened at 2002-08-28 12:45
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=601097&group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Stephen Coy (scoy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Race cond in QueuedPessimisticEJBLock

Initial Comment:
I believe that I have uncovered a race condition in 
QueuedPessimisticEJBLock that
causes the deadlock detector to misfire.

We have an entity bean with interface:

public interface Designation
   extends javax.ejb.EJBObject
{
   public java.lang.String getCode(  ) throws 
java.rmi.RemoteException;

   public java.lang.String getDisplay(  ) throws 
java.rmi.RemoteException;

}

The bean is configured with commit option A and the "get*" 
methods are read-only.

Two threads A and B each begin a new trx and begin iterating over 
a collection of
these beans, calling getCode and getDisplay on each one. Thread 
A is running
slightly ahead of thread B. (we are building a popup menu in a 
JSP).

At some point, thread A is delayed slightly while it loads data 
during its invoke
of getCode and thread B catches up with it. Thread B blocks in
QueuedPessimisticEJBLock.waitForTx because thread A has the 
lock. Prior to
blocking it adds an entry to the BeanLockSupport.waiting 
HashMap.

Thread A completes its invokation of getCode and the following 
methods of
QueuedPessimisticEJBLock get called:
1. endInvocation
2. endTransaction
3. nextTransaction

Amongst other things, nextTransaction sets the lock's tx to that of 
thread B
and wakes up thread B.

This is where the race begins.

Thread A subsequently calls getDisplay on the same bean and 
enters waitForTx.
It's mi tx is now different to the lock's tx, so it enters the wait loop
and adds an entry to the BeanLockSupport.waiting HashMap.
Thread B has not yet run to the end of waitForTx, so it's entry is 
still
sitting in the BeanLockSupport.waiting HashMap.

Thread A runs BeanLockSupport.deadlockDetection and it finds 
thread B's
entry that says it's waiting on thread A's lock, because thread B 
has not
got around to removing it yet.

BeanLockSupport.deadlockDetection throws 
ApplicationDeadlockException, even
though there is no real deadlock present.

I'm going to try and fix it, but I know this is a sensitive area and 
you guys
will probably have your own ideas on the best way.

I'm running MacOS 10.1.5 and the corresponding Apple 1.3.1 
JRE, for what it's worth.


--

>Comment By: Stephen Coy (scoy)
Date: 2002-08-28 17:55

Message:
Logged In: YES 
user_id=463096

This little patch seems to fix it for us.

RCS file: /cvsroot/jboss/jboss/src/main/org/jboss/ejb/plugins/lock/
QueuedPessimisticEJBLock.java,v
retrieving revision 1.9.2.2
diff -r1.9.2.2 QueuedPessimisticEJBLock.java
417c417,421
<  this.tx = thelock.tx;
---
>synchronized (waiting)
>{
>waiting.remove(thelock.tx);
>   this.tx = thelock.tx;
>}

It goes into the nextTransaction method, but it should be reviewed by 
the person who added the comment:

// The new transaction is the next one, important to set it up to avoid 
race with 
// new incoming calls

I could previously generate the problem at will, but it no longer seems to 
happen with this change.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=601097&group_id=22866


---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Change Notes-601185 ] ejb-jar.xml requires a Public ID

2002-08-28 Thread noreply

Change Notes item #601185, was opened at 2002-08-28 11:49
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381174&aid=601185&group_id=22866

Category: JBossServer
Group: v3.2
Status: Open
Priority: 5
Submitted By: Christian Riege (lqd)
Assigned to: Christian Riege (lqd)
Summary: ejb-jar.xml requires a Public ID

Initial Comment:
Any ejb-jar.xml file encountered now *requires* a valid
DOCTYPE Declaration and public Id as per the EJB 1.1 /
2.0 Specs. Acceptable public Id's are:

- "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
1.1" for EJB 1.1

- "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
2.0" for EJB 2.0

if this breaks your deployments, fix your DOCTYPE
declaration that should be all that's necessary.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=381174&aid=601185&group_id=22866


---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-600837 ] Verifier: ejb-jar.xml DOCTYPE required

2002-08-28 Thread noreply

Bugs item #600837, was opened at 2002-08-27 17:20
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600837&group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Dain Sundstrom (dsundstrom)
Assigned to: Christian Riege (lqd)
Summary: Verifier: ejb-jar.xml DOCTYPE required

Initial Comment:
The DOCTYPE declaration in the ejb-jar.xml file is
required, but the verifier does not enforce this.  

EJB 2.0 spec page 161:
All valid ejb-jar deployment descriptors must contain
the following DOCTYPE declaration:

http://java.sun.com/dtd/ejb-jar_2_0.dtd";>

--

>Comment By: Christian Riege (lqd)
Date: 2002-08-28 11:50

Message:
Logged In: YES 
user_id=176671

i've changed this in HEAD and 3.2. See also SF ChangeNote:

http://sourceforge.net/tracker/index.php?func=detail&aid=601185&group_id=22866&atid=381174

if it breaks your deployments don't bitch but change your
DOCTYPE declaration :).

--

Comment By: Christian Riege (lqd)
Date: 2002-08-27 19:04

Message:
Logged In: YES 
user_id=176671

So JBoss should throw a DeploymentException if no valid
DOCTYPE (1.1 or 2.0 at the moment) is found? I'll leave it
at the ApplicationMetaData.java level though as the Verifier
should only kick in after the ejb-jar.xml has been read and
validated. Do you think this should also go into 3.2 release
or should I leave it at 4.0 for the time being?

I have a rough sketch of a re-write of the Verifier for
JBoss 4.0; matter of fact is that I think that we can pull
out a lot of the checking that is currently going on in the
CMR code at run-time into the deployment step. We should
have a close look at this when you start implementing the
CMP/CMR stuff for 4.0 -- i.e. your new engine shouldn't
worry about the data being passed into it as this data will
already have been verified. Does this make sense?

--

Comment By: Dain Sundstrom (dsundstrom)
Date: 2002-08-27 18:46

Message:
Logged In: YES 
user_id=251431

Yes, but the verifier chan check that the document contains
a correct doctype after the document is parsed. 

The ejb 1.1 also requires a doctype declaration, so the code
should sheck that the document has a doctype decl and that
it is either 1.1 or 2.0.

--

Comment By: Christian Riege (lqd)
Date: 2002-08-27 18:22

Message:
Logged In: YES 
user_id=176671

i don't think this is an issue w/ the verifier as the
BeanVerifier gets handed an already parsed ejb-jar.xml ATM.

According to the code in
org.jboss.metadata.ApplicationMetadata i don't see how you
can get 2.0 ejb-jar.xml behaviour w/ no valid 2.0 DOCTYPE
declaration but maybe i'm missing your point?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=600837&group_id=22866


---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-601193 ] jndiView.list Fails with ExternalContext

2002-08-28 Thread noreply

Bugs item #601193, was opened at 2002-08-28 10:09
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=601193&group_id=22866

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Binoy Shah (swatkat)
Assigned to: Nobody/Anonymous (nobody)
Summary: jndiView.list Fails with ExternalContext

Initial Comment:
JBoss Version : Build 3.0.1

OS : Windows 2000 Server

Java version : 1.3.1_03 
Java(TM) 2 Runtime Environment, Standard Edition 
(build 1.3.1_03-b03)
Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed 
mode)

OLD EXTERNAL LDAP CONFIG for JBOSS Version 
2.4.4

--
jboss.jcml
--



external/ldap/practiceit
sscldap.conf
javax.naming.ldap.InitialLdapCont
ext
true


OLD EXTERNAL LDAP CONFIG for JBOSS Version 
2.4.4
--
sscldap.conf
--
java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFac
tory
java.naming.provider.url=ldap://192.9.200.5:389/dc=practi
ceit,dc=net
java.naming.security.principal=cn=SystemManager,dc=p
racticeit,dc=net
java.naming.security.authentication=simple
java.naming.security.credentials=secretpass



WORKING JAVA CODE FOR JNDI ACCESS for 
Version 2.4.4


public String search(String name) 
{
String bId  ="";
try 
{
/* Create an environment for the initial 
directory context.*/
/* Create the initial directory context. */
DirContext drctx = new InitialDirContext
(getInitialLdapContext().getEnvironment());;
/* Set up and perform the search. Find all 
matching in ou=name. */
String base = "o=PracticeVeterinary";
String filter = "(ou="+name+")";
SearchControls constraints = new 
SearchControls();
constraints.setSearchScope
(SearchControls.SUBTREE_SCOPE);
NamingEnumeration results = drctx.search
(base,filter,constraints);
/* Print the search results. */
if (!results.hasMore()) 
{
System.out.println("Nothing found.");
} 
else
{
while (results.hasMore()) 
{
SearchResult sr = (SearchResult) 
results.next();
Attributes attrs = sr.getAttributes();
if (attrs == null)
{
System.out.println("No attributes");
}
else 
{
/* For each attribute of the entry. 
find a custom entry called bid */
Attribute bIdCtx = attrs.get("bid");
bId  = (String)bIdCtx.get(0);
}
}
}
}
catch (NamingException e) 
{
/* Handle any name/directory exceptions. */
}//catch
catch (Exception e) 
{
/* Handle any other types of exceptions. */
}//catch
return bId;
}
public Context getInitialLdapContext()  throws 
NamingException
{
String ldapCtxString = "external/ldap/practiceit";
InitialContext initCtx = new InitialContext();
Context ldapCtx = (Context)initCtx.lookup
(ldapCtxString);
return ldapCtx;
}


JBOSS 3.0.1 SETTINGS 

--
jboss-service.xml
--

  
  
external/ldap/practiceit
/conf/sscldap.conf
javax.naming.ldap.InitialLdapCont
ext
true
  

-
sscldap.conf file in conf folder
-

java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFac
tory
java.naming.provider.url=ldap://192.9.200.5:389/dc=practi
ceit,dc=net
java.naming.security.principal=cn=SystemManager,dc=p
racticeit,dc=net
java.naming.security.authentication=simple
java.naming.security.credential=secretpass

Once i add this reference and start the server the 
jndiView MBean doesnt work
[B]
If i invoke the list() function with (false) it just hangs and 
after around 20 minutes it 
gives out of memory error ( have put 512 M stack)[/B]

2002-08-23 17:36:37,542 WARN  [org.jboss.jbossweb] 
WARNING: Exception for /jmx-console/HtmlAdaptor
RuntimeErrorException: Error in MBean operation 'list
(,boolean)'
Cause: java.lang.OutOfMemoryError
at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invok
e(ReflectedMBeanDispatcher.java:307)
at 
org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:491)
at 
org.jboss.jmx.adaptor.control.Server.invokeOpByName
(Server.java:226)
at 
org.jboss.jmx.adaptor.control.Server.invokeOp
(Server.java:195)
at 
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp
(HtmlAdaptorServlet.java:171)
at 
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processR
equest(HtmlAdaptorServlet.java:77)
at 
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost
(HtmlAdaptorServlet.java:59)
at javax.servlet.http.HttpServlet.service
(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.

[JBoss-dev] JBoss snapshoting and versioning

2002-08-28 Thread Sacha Labourey

Hello,

I've speaking lately with David Jencks about JBoss "state" (configuration)
snapshoting and versioning.

Currently, JBoss running-configuration (RC) and static-configuration (SC)
are two different things. the static-configuration is defined by the set of
files in /conf, /deploy and /lib. The running-config is defined by the base
static-config + any modification that has occured after that:
creation/deletion of MBeans, etc.

For example, dynamically adding a topic through the http interface will not
be a persistent creation: restarting jboss will forget about this topic.
Etc.

This first step is important as it is critical to be able to remotely and
dynamically configure a running jboss instance.

The second step that is possible to reach from there is versionning.

The question is how to get a "snapshot" of a *running-config* of a jboss
instance. This state will incoroporate:
- the mbean definitions (metadata), config, etc. and maybe some other state
- (important) the correct order for the the deployment of these mbeans
(because of the dependencies they have with each other)

Once you have a snapshot, you can persist it anywhere (filesystem, CVS,
etc.) and retrieve it. Maybe then, some kind of central manager (daemon)
that could start/stop different JBoss instances (with different configs)
could also be of use.

Partial snapshot should also be possible (for example, "I want to snapshot
all J2EE applications + Mbeans in the "com.mycompany.*" JMX domain name",
thus only snapshoting applications + related config and not the system)

David's remarks were notably:
- the fact that Service controller, creator, configurator and associated
deployer are too strongly mixed up
- lifecycle management should be moved to mbean interceptors

It seems that some people are working on some of the parts involved in this
proposal. So my questions are:
- What do you think about this feature, how you think it should/not be
implemented, etc.
- If the parts on which you are working can help on this task
- etc.

But remember: KISS ;)

Cheers,



Sacha



---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-425847 ] Stateful session bean problem

2002-08-28 Thread noreply

Bugs item #425847, was opened at 2001-05-21 10:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=425847&group_id=22866

Category: JBossServer
Group: v2.2.1 (stable)
Status: Closed
Resolution: None
Priority: 5
Submitted By: Tim McCune (javajedi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Stateful session bean problem

Initial Comment:
When trying to call a method on a stateful session 
bean, I sometimes get the following exception:

TRANSACTION ROLLBACK EXCEPTION:Application Error: 
tried to enter
Stateful bean with different transaction context; 
nested exception is:
java.rmi.RemoteException: Application Error: tried to 
enter Stateful bean with different transaction context
java.rmi.RemoteException: Application Error: tried to 
enter Stateful bean with different transaction context
at 
org.jboss.ejb.plugins.StatefulSessionInstanceIntercepto
r.invoke(StatefulSessionInstanceInterceptor.java:172)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext
(TxInterceptorCMT.java:133)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti
ons(TxInterceptorCMT.java:263)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke
(TxInterceptorCMT.java:99)
at org.jboss.ejb.plugins.LogInterceptor.invoke
(LogInterceptor.java:195)
at org.jboss.ejb.StatefulSessionContainer.invoke
(StatefulSessionContainer.java:326)
at 
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.
invoke(JRMPContainerInvoker.java:392)
at java.lang.reflect.Method.invoke(Native Method)
at sun.rmi.server.UnicastServerRef.dispatch
(UnicastServerRef.java:241)
at sun.rmi.transport.Transport$1.run
(Transport.java:142)
at java.security.AccessController.doPrivileged(Native 
Method)
at sun.rmi.transport.Transport.serviceCall
(Transport.java:139)
at sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:443)
at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.ru
n(TCPTransport.java:643)
at java.lang.Thread.run(Thread.java:484)

--

Comment By: Jakub Mendys (jmendys)
Date: 2002-08-28 14:04

Message:
Logged In: YES 
user_id=602025

I also got this exception as described by nobody on 2001-08-
23 06:44. Is there any way to avoid this ?

--

Comment By: Tim McCune (javajedi)
Date: 2001-08-23 19:26

Message:
Logged In: YES 
user_id=62441

I figured out that this is caused by accessing a stateful 
session bean from separate threads, which is apparently 
simply not allowed by JBoss.  I don't know whether the spec 
intends it to be possible or not.

--

Comment By: Nobody/Anonymous (nobody)
Date: 2001-08-23 06:44

Message:
Logged In: NO 

I also noticed this Exception. It seems to happen when a 
HTTP request is interrupted by pressing "Stop" while an EJB 
is doing something. When "reloading" the page and executing 
the same operation again I see an exception showing that 
the serialized file cannot be found.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=425847&group_id=22866


---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Bugs-425847 ] Stateful session bean problem

2002-08-28 Thread noreply

Bugs item #425847, was opened at 2001-05-21 10:43
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=425847&group_id=22866

Category: JBossServer
Group: v2.2.1 (stable)
Status: Closed
Resolution: None
Priority: 5
Submitted By: Tim McCune (javajedi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Stateful session bean problem

Initial Comment:
When trying to call a method on a stateful session 
bean, I sometimes get the following exception:

TRANSACTION ROLLBACK EXCEPTION:Application Error: 
tried to enter
Stateful bean with different transaction context; 
nested exception is:
java.rmi.RemoteException: Application Error: tried to 
enter Stateful bean with different transaction context
java.rmi.RemoteException: Application Error: tried to 
enter Stateful bean with different transaction context
at 
org.jboss.ejb.plugins.StatefulSessionInstanceIntercepto
r.invoke(StatefulSessionInstanceInterceptor.java:172)
at org.jboss.ejb.plugins.TxInterceptorCMT.invokeNext
(TxInterceptorCMT.java:133)
at 
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransacti
ons(TxInterceptorCMT.java:263)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke
(TxInterceptorCMT.java:99)
at org.jboss.ejb.plugins.LogInterceptor.invoke
(LogInterceptor.java:195)
at org.jboss.ejb.StatefulSessionContainer.invoke
(StatefulSessionContainer.java:326)
at 
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.
invoke(JRMPContainerInvoker.java:392)
at java.lang.reflect.Method.invoke(Native Method)
at sun.rmi.server.UnicastServerRef.dispatch
(UnicastServerRef.java:241)
at sun.rmi.transport.Transport$1.run
(Transport.java:142)
at java.security.AccessController.doPrivileged(Native 
Method)
at sun.rmi.transport.Transport.serviceCall
(Transport.java:139)
at sun.rmi.transport.tcp.TCPTransport.handleMessages
(TCPTransport.java:443)
at 
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.ru
n(TCPTransport.java:643)
at java.lang.Thread.run(Thread.java:484)

--

Comment By: Jakub Mendys (jmendys)
Date: 2002-08-28 14:06

Message:
Logged In: YES 
user_id=602025

I also got this exception as described by nobody on 2001-08-
23 06:44. Is there any way to avoid this ?
I'm sure in my case it has nothing to do with my external 
threads (i do not have such). Maybe the problem is in Jetty 
server and its threads ?

--

Comment By: Jakub Mendys (jmendys)
Date: 2002-08-28 14:04

Message:
Logged In: YES 
user_id=602025

I also got this exception as described by nobody on 2001-08-
23 06:44. Is there any way to avoid this ?

--

Comment By: Tim McCune (javajedi)
Date: 2001-08-23 19:26

Message:
Logged In: YES 
user_id=62441

I figured out that this is caused by accessing a stateful 
session bean from separate threads, which is apparently 
simply not allowed by JBoss.  I don't know whether the spec 
intends it to be possible or not.

--

Comment By: Nobody/Anonymous (nobody)
Date: 2001-08-23 06:44

Message:
Logged In: NO 

I also noticed this Exception. It seems to happen when a 
HTTP request is interrupted by pressing "Stop" while an EJB 
is doing something. When "reloading" the page and executing 
the same operation again I see an exception showing that 
the serialized file cannot be found.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=425847&group_id=22866


---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] ÍøÂç¹ã¸æ¼°³ÏÑû´úÀíÍøÕ¾¼ÓÃË

2002-08-28 Thread [EMAIL PROTECTED]

Hello: (If you can't read the email,please click here 
http://www.jjyx.com/serve/advertise.htm)   Thank you
 

×ð¾´µÄÏÈÉú/Ůʿ£º(´òÈÅÄúһϣ¬Èô´ËÐŶÔÄúÎÞÓã¬Çëɾ³ý£¬Ð»Ð»£©
 
ÒøºÓÖ®Ðǹã¸æ·þÎñ¼°³ÏÕ÷´úÀíÍøÕ¾ÁªÃË£º
 
¿ÉÔÚÈ«¹úÄËÖÁÊÀ½ç·¶Î§·¢²¼ÐÅÏ¢£¬Í¶·Å¹ã¸æ¡£
 
Ò» 
¹ã¸æÓʼþ£º¿É¸ù¾ÝÄúµÄÐèÒª£¬ÔÚ¹úÄÚÖ¸¶¨ÇøÓò£¬µØµã»òÐÐÒµ½øÐйã¸æÓʼþÐÅÏ¢·¢²¼µÈ¡£ÆäÌصãÊÇ£º·¶Î§¹ã£¬Ê±Ð§¸ß£¬¼Û¸ñµ×¡£10Íò·â¶¨ÏòÓʼþ·¢²¼²Å300£¬1000ÍòÓʼþµØÖ·³öÊÛ½ö150Ôª¡£¹ã¸æÓʼþÏêϸ±¨¼ÛÇëµã»÷£ºhttp://www.jjyx.com/serve/advertise.htm
  
ÎÒÃÇÓµÓа´È«¹úµØÇø£¬ÐÐÒµ·ÖÀàÊýǧÍòÓʼþµØÖ·¼°ÍêÉƵķ¢²¼ÏµÍ³£¬ËæʱΪÄãÌṩÂúÒâµÄ·þÎñ¡£»úÓöÄѵ㬸ϿìÐж¯°É£¬ÈÃÄãµÄÆóÒµ£¬¹«Ë¾Á¢¼´ÕÆÎÕÉÌ»ú´«Ã½µÄÃüÂö--¹ã¸æE-MAIL¡£
 
¶þ 
70ÖÖ×îÐÂÖøÃûÓʼþËÑË÷£¬Èº·¢£¬·Ö¸î£¬ÑéЧÈí¼þ¡£ÈÃÄúÄܶÌʱ¼äÔÚ»¥ÁªÍøÉÏÖ¸¶¨ËѼ¯Èô¸ÉÆóÒµ£¬¹«Ë¾¿Í»§µÄµç×ÓÓʼþ²¢³ÉǧÉÏÍòµÄȺ·¢³ö×Ô¼ºµÄ¹ã¸æÓʼþ£¬°üÀ¿Á˵±´ú×îÓÅÐãµÄEmail¹ã¸æÈí¼þ¡£ÆäÕý°æ×ܼ۸ñ³¬¹ýÍòÔª£¬ÏÖÖ»ÊÛ450Ôª.(È«¹ú×îµ×¾ª±¬¼Û¸ñ£©ÏêÇéÇë¼û£ºhttp://www.jjyx.com/serve/advertise2.htm
 
Èý ËÑË÷ÒýÇæ×¢²á  
°ïÄãµÇ½ȫÇò6000‚€Ó¢ÎÄËÑË÷ÒýÇæ(ÈçYAHOO£¬GOOGLEDµÈ)£¬½ø200¸öÖÐÎÄËÑË÷ÒýÇæ(ÈçÍøÒ×£¬ÑÅ»¢£¬Ïã¸ÛÌí´ïËÑË÷µÈ)¡£ÈÃÄãµÄÍøÕ¾ÏíÓþÈ«Çò¡££¨³¬Öµ·þÎñ£¬ÌػݼÛ400£©
 
ËÄ 
ÍøÂçÐÅÏ¢·¢²¼£ºÒøºÓÖ®ÐÇ¿ÉÒÔ½«ÄúµÄÏúÊÛ£¬¹ºÂò£¬ÕÐÉÌ»òºÏ×÷µÈÉÌÒµÐÅÏ¢×Ô¶¯·¢²¼µ½ÊÀ½çÖªÃûµÄ3300¶à¸öóÒ×¹«¸æ°åºÍ¹úÄÚÉÏǧ¸öBBS£¬ÂÛ̳¹«¸æµÈ¡£×î´óÏÞ¶ÈÌáÉýÄãµÄÉÌÒµ»ú»á¡££¨³¬Öµ¼Û350Ôª£©
 
 
 
µç×ÓÓʼþȺ·¢·þÎñÇë¼û£ºhttp://www.jjyx.com/serve/advertise.htm 
 
µç×ÓÓʼþȺ·¢£¬ËÑË÷Èí¼þ³öÊÛÇë¼û£ºhttp://www.jjyx.com/serve/advertise2.htm
 

³ÏÕ÷´úÀíÍøÕ¾ÁªÃË¡ª¡ªÖÐСÍøÕ¾Ó®ÀûµÀ·
 
ÍøÕ¾´úÀíÓû§£ºÎÞÂÛÄãÍøÕ¾¹æÄ£´óС£¬¾ù¿É´úÀí±¾Õ¾¹ã¸æ·þÎñ¼°Èí¼þ²úÆ·¡£ÎÒÃǽ«Ã¿Ô¶¨ÆÚ½«ÄãÔÚ¸ÃÔµÄÏúÊÛÌá³É½ð¶îͨ¹ýÓʾֵç×Ó»ã¿î»ã¸ø´úÀíÈË¡£
²½Öè¼ò±ã£º
1.Ìî±íÉêÇë±í. 
2.µÃµ½Á´½Ó´úÂë. 
3.ÔÚÄúµÄÍøÕ¾·ÅÈë´ËÁ´½Ó,ʹ¿Í»§¿ÉÒÔͨ¹ý´ËÁ´½ÓÖ¸Ïò±¾Õ¾.
4.¿Í»§¸¶¿îºóÄú¾Í¿ÉÒԵõ½ÏàÓ¦Ó¶½ð. ±¨³ê£½100ÔªÔùËÍ£«½»Ò׶î*25%
5.µ±Ó¶½ð×ܶî´ïµ½200Ԫʱ¾Í¿ÉÒÔµ±ÌìÊÕµ½±¾Õ¾»ã¿îÖ§¸¶Í¨Öª   ±¨³ê£½100ÔªÔùËÍ£«½»Ò׶î*25% 
 
ÏÖÔÚ¼ÓÈë¾ÍÁ¢¼´ÔùËÍ100Ôª£¬Çëµã»÷ÕâÀhttp://www.jjyx.com/serve/daili.htm
 
ÖÂ
Àñ
 
ÒøºÓÖ®ÐÇ
 
 
 

If you can't read the email,please click here http://www.jjyx.com/serve/advertise.htm  
Thank you


---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] New SAO PAULO TRAINING PRICE

2002-08-28 Thread marc fleury

we have bumped the training price down to USD2500, flat price, to take
into account the differences in curencies.  I hope you will show up to
this training.  We got excellent material, all the latest 3.0 stuff
covered from detail to philosophy and if you guys don't show up now you
will not get another opportunity in South America soon,

marc f

xx
Marc Fleury, Ph.D.
President, Founder
JBoss Group, LLC
xx



---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] Automated JBoss(HEAD Matrix2) Testsuite Results: 27-August-2002

2002-08-28 Thread Chris Kimpton

Hi,

Feel free to run it - send the results to the list - especially where the
results are different from the other results.

If you have time - then the best next step would be to get the sourceforge
compile farm doing this work - this makes it more manageable - more people
can access it.

I was supposed to be doing this...

Chris

- Original Message -
From: "Holger Baxmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 27, 2002 7:07 AM
Subject: Re: [JBoss-dev] Automated JBoss(HEAD Matrix2) Testsuite Results:
27-August-2002


> hi chris,
>
> is it of any help if i spend some space and time on a 2 cpu sparc sun
ultra
> 60 for testing ?
>
> bax
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, August 27, 2002 3:33 AM
> Subject: [JBoss-dev] Automated JBoss(HEAD Matrix2) Testsuite Results:
> 27-August-2002
>
>
> >
> > Number of tests run:   886
> >
> > 
> >
> > Successful tests:  860
> > Errors:21
> > Failures:  5
> >
> > 
> >
> > [time of test: 27 August 2002 2:23 GMT]
> > [java.version: 1.3.1_03]
> > [java.vendor: Sun Microsystems Inc.]
> > [java.vm.version: 1.3.1_03-b03]
> > [java.vm.name: Java HotSpot(TM) Client VM]
> > [java.vm.info: mixed mode]
> > [os.name: Linux]
> > [os.arch: i386]
> > [os.version: 2.4.9-34]
> >
> > Useful resources:
> >
> > - http://lubega.com/testarchive/sun_jdk131_03 for the junit report of
this
> test.
> > - http://lubega.com/testarchive/sun_jdk131_03/logs/ for the logs for
this
> test.
> >
> > - http://lubega.com for general test information.
> >
> > 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!
> >
> > 
> >
> >
> >
> > Oh dear - still got some errors!
> >
> >
> >
> > Thanks for all your effort - we really do love you!
> >
> >
> >
> >
> > ---
> > This sf.net email is sponsored by: OSDN - Tired of that same old
> > cell phone?  Get a new here for FREE!
> > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > ___
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
>



---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] [ jboss-Patches-601487 ] Fix new JMX Name Rules for EJB

2002-08-28 Thread noreply

Patches item #601487, was opened at 2002-08-28 19:26
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376687&aid=601487&group_id=22866

Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Corby (corby)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix new JMX Name Rules for EJB

Initial Comment:
As of 3.0.2, you can longer deploy EJBs that are bound 
to local java namespaces, because the container will 
attempt to form an illegal JMX Name.

Here is a simple patch (sorry, can't cvs diff from work). 
Replace org/jboss/ejb/Container.getJmxName() with the 
routine in the enclosed text file.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376687&aid=601487&group_id=22866


---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] XADataSource wrapper for JBoss 4

2002-08-28 Thread Jamie Burns



Im having a go at testing the XADataSource wrapper 
that David Jenks has written for JBoss 4 against MS SQL Server 2000. Ive checked 
out HEAD and built it ok. However, im getting a variety of errors when 
starting JBoss.
 
When JBoss loaded l was getting an error while it 
was deploying jmx-html-adapter.sar. Ive removed it and get a cleaner startup. 
Will removing jmx-html-adapter.sar break JBoss?
 
With jmx-html-adapter.sar out of the picture l only 
get the following error when JBoss starts.
 
ERROR 
[org.jboss.deployment.scanner.URLDeploymentScanner] MBeanException: Exception in 
MBean operation 'checkIncompleteDeployments()'
 
I havent written any MBeans so l cant see that l 
have done anything to cause this. Any clues about what is causing 
this?
 
When my client tries to load my EJB l get the 
following error.
 
20:47:43,187 WARN  [NamingContext] Failed to 
connect to iiop:1099javax.naming.CommunicationException: Failed to connect 
to server iiop:1099.  Root exception 
isjavax.naming.ServiceUnavailableException: Failed to connect to server 
iiop:1099.  Root exception isjava.net.UnknownHostException: 
iiop    at 
java.net.InetAddress.getAllByName0(InetAddress.java:920)
...
 
20:47:48,735 ERROR [STDERR] 
javax.naming.CommunicationException: Receive timed out.  Root exception 
is20:47:48,735 ERROR [STDERR] java.net.SocketTimeoutException: Receive timed 
out
 
 
Is this likely to be related to the MBeanException 
above or the removal of jmx-html-adapter?
 
The EAR lm going to use to test Davids XADataSource 
wrapper is working on JBoss 3.0. Is there anything special l have to do to port 
an EAR across to JBoss 4 alpha?
 
Thanks


Re: [JBoss-dev] XADataSource wrapper for JBoss 4

2002-08-28 Thread Igor Fedorenko

New xa wrapper has problems. With few fixes (to be checked in later 
today) I was able to deploy xa jdbc datasource into 4.0alpha but did not 
get any further yet. However, ServiceUnavailableException looks like 
something independent from these problems.

Jamie Burns wrote:
> Im having a go at testing the XADataSource wrapper that David Jenks has 
> written for JBoss 4 against MS SQL Server 2000. Ive checked out HEAD and 
> built it ok. However, im getting a variety of errors when starting JBoss.
>  
> When JBoss loaded l was getting an error while it was deploying 
> jmx-html-adapter.sar. Ive removed it and get a cleaner startup. Will 
> removing jmx-html-adapter.sar break JBoss?
>  
> With jmx-html-adapter.sar out of the picture l only get the following 
> error when JBoss starts.
>  
> ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] 
> MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
>  
> I havent written any MBeans so l cant see that l have done anything to 
> cause this. Any clues about what is causing this?
>  
> When my client tries to load my EJB l get the following error.
>  
> 20:47:43,187 WARN  [NamingContext] Failed to connect to iiop:1099
> javax.naming.CommunicationException: Failed to connect to server 
> iiop:1099.  Root exception is
> javax.naming.ServiceUnavailableException: Failed to connect to server 
> iiop:1099.
>   Root exception is
> java.net.UnknownHostException: iiop
> at java.net.InetAddress.getAllByName0(InetAddress.java:920)
> ...
>  
> 20:47:48,735 ERROR [STDERR] javax.naming.CommunicationException: Receive 
> timed o
> ut.  Root exception is
> 20:47:48,735 ERROR [STDERR] java.net.SocketTimeoutException: Receive 
> timed out
>  
>  
> Is this likely to be related to the MBeanException above or the removal 
> of jmx-html-adapter?
>  
> The EAR lm going to use to test Davids XADataSource wrapper is working 
> on JBoss 3.0. Is there anything special l have to do to port an EAR 
> across to JBoss 4 alpha?
>  
> Thanks


-- 
Igor Fedorenko
Think smart. Think automated. Think Dynamics.
www.thinkdynamics.com



---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] CVS viewing problem from the web

2002-08-28 Thread Anatoly Akkerman

Hi, guys

I've been trying to look at the files in CVS through the Sourceforge CVS 
view but can't see any files no matter what branch option I chose. Is 
something screwed up with JBoss' CVS tags or Sourceforge viewer is just 
dumb? Any way to view the repository without downloading the whole thing?
-- 
-
Anatoly Akkerman
Computer Science Dept.
Courant Institute of Mathematical Sciences, NYU
715 Broadway, #719  Tel: 212 998-3493
New York, NY 10003  Fax: 212 995-4123
-



---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] XSLSubDeployer for JMSProvider loading

2002-08-28 Thread Michael Bartmann

Hi,

I am just tryaing to (ab-)use the XSLSubDeployer to load a JMS-Provider.
(with Adapter, Loader and Pool to feed into MDB), and my first tests
look quite promising (Branch_3_2).
The bla-jmsp.xml is not much shorter than the ordinary bla-service.xml
(at the moment there are more parameters than with datasources)
but it is less error prone, cause some mbean references are "resolved"
automagically.
And (of course) xsl deployment decouples userspace configuration from
version specific mbean details.

It is a bit difficult to get everything flexible enough for any other
jms-provider (xml-parameters only tested it with my own jms provider),
but as with datasources it copies nested  and such literally.

Do you think such a gadget would fit into the jboss codebase?

My main usecase is deploying of many jms-providers bundled with their 
own MDBs inside their own ear-scope.
To get the above mentioned mbean-references right in a lot
of jboss-service.xml files (you must use different ObjectNames cause
everything lives in the same JMX server) is monkey work and xsl
should help a lot...

Enjoy,
Michael




---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] XSLSubDeployer for JMSProvider loading

2002-08-28 Thread David Jencks

+1000

I'm really glad to see someone is taking advantage of the xsl sub deployer.
 I think more the simplifications/customizations we can make the better.

Do you have any ideas how we can include these customized configuration xml
bits in one file, so you can have both regular mbean config,
, , etc etc. in one file, with each custom
element being processed by its own xsl?

I don't know if this would help, but in jboss 4 you can generate xmbean
configuration including the initial attribute values and include it
"inline" in a *-service.xml file.  This lets you deploy POJO as xmbeans
without needing the standard *MBean interface.

Would you be interested in working on some xsl for jca 1.5 deployment?  I
have most of the server side stuff written, (and some of it even tested)
but havent' started on deployment yet.  I think it can be 99% xsl based,
generating these xmbean configurations for the necessary adapter classes.

Thanks
david jencks

On 2002.08.28 18:56:22 -0400 Michael Bartmann wrote:
> Hi,
> 
> I am just tryaing to (ab-)use the XSLSubDeployer to load a JMS-Provider.
> (with Adapter, Loader and Pool to feed into MDB), and my first tests
> look quite promising (Branch_3_2).
> The bla-jmsp.xml is not much shorter than the ordinary bla-service.xml
> (at the moment there are more parameters than with datasources)
> but it is less error prone, cause some mbean references are "resolved"
> automagically.
> And (of course) xsl deployment decouples userspace configuration from
> version specific mbean details.
> 
> It is a bit difficult to get everything flexible enough for any other
> jms-provider (xml-parameters only tested it with my own jms provider),
> but as with datasources it copies nested  and such literally.
> 
> Do you think such a gadget would fit into the jboss codebase?
> 
> My main usecase is deploying of many jms-providers bundled with their 
> own MDBs inside their own ear-scope.
> To get the above mentioned mbean-references right in a lot
> of jboss-service.xml files (you must use different ObjectNames cause
> everything lives in the same JMX server) is monkey work and xsl
> should help a lot...
> 
> Enjoy,
> Michael
> 
> 
> 
> 
> ---
> This sf.net email is sponsored by: Jabber - The world's fastest growing 
> real-time communications platform! Don't just IM. Build it in! 
> http://www.jabber.com/osdn/xim
> ___
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 
> 


---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] CVS viewing problem from the web

2002-08-28 Thread Dain Sundstrom

Anatoly Akkerman wrote:
> Hi, guys
> 
> I've been trying to look at the files in CVS through the Sourceforge CVS 
> view but can't see any files no matter what branch option I chose. Is 
> something screwed up with JBoss' CVS tags or Sourceforge viewer is just 
> dumb? Any way to view the repository without downloading the whole thing?

I just tried it and it is totally broken.  File a bug report with 
sourceforge.

https://sourceforge.net/tracker/?func=add&group_id=1&atid=21

-- 

Dain Sundstrom
Chief Architect JBossCMP
JBoss Group, LLC




---
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development