Thanks. I have already had a look at the TM code and saw that check. Trace
logging is no option for me. This happens randomly and rarely on a production
system.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4106985#4106985
Reply to the post :
That makes sense. I don't know if I can reproduce the problem in a reasonably
small test case. I can try, but I currently lack the time.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4107011#4107011
Reply to the post :
Yes, that's what I expected (that connections are stored in the tx). Hibernate
(EJB3) is the one requesting the connection. I am not doing this explicitly
there. I might open a connection from the same DS explicitly in another place
(within this tx) and then call close() when done. But that
To be done, really. I was hoping to get a comment from a JBoss developer.
Because I really think it is a bad misbehaviour.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4103475#4103475
Reply to the post :
We heavily rely on XA as multiple resource adapters are involved in a tx. Using
local or no-tx connections is absolutely no option. And we already use
track-connection-by-tx because Oracle connections are not capable of sharing
the same connection with multiple XA transactions.
Actually the
No, that's really hard. Because the tx can be set rollback-only at many
different points in the process. So I would need to basically check at every
read operation and then manually suspend the tx - a lot of boilerplate code.
That's too horrible. I rather patch the connection manager.
View the
I have a case where the transaction is marked rollback during the course of a
complex process. But I still have to read from the DB and do some more
processing. During that a new DB connection is opened (for read-only purposes)
behind the scenes and thats where the connection manager complains:
ksdeger, yes, we have commented all pool related stuff from SocketManager. It's
not possible to get rid of it through configuration.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4070407#4070407
Reply to the post :
Hi,
It is a known problem that 4.0.4 and EJB-3 leaks Hibernate lazy proxy classes
generated by Javassist. The cache introduced in Javassist-3.4 (4.0.4 ships with
Javassist-3.2) should solve the problem, but unfortunately doesn't. Probably
because Hibernate uses a different MethodHandler for
Ok, thanks. As the bug was fixed in 4.0.4RC1, we should be safe with 4.0.4GA.
So the pool was introduced as a fix against deadlocks. Okay, but this way the
delivery order of messages is not known anymore (depends on scheduler).
Couldn't that cause more trouble during bursts?
View the original
I have removed the pool from SocketManager. All still works fine and we see no
more excess thread creation.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4059867#4059867
Reply to the post :
A big problem is this code in SocketManager
| // TODO: Check the validity of this config
| pool = new PooledExecutor(5);
| pool.setMinimumPoolSize(1);
| pool.setKeepAliveTime(1000 * 60);
| pool.runWhenBlocked();
| String id = SocketManager.MsgPool@+
|
If you want to monitor thread death, deploy this mbean and watch the log:
public class ThreadCoroner extends ServiceMBeanSupport implements
ThreadCoronerMBean {
| private ThreadMXBean mbean;
| private MapLong, ThreadInfo last;
| private Timer timer;
| private int interval
Thanks for the information, Adrian. Much appreciated.
NIO: At the HttpClient project we have mixed experience with the latest NIO
implementations under Linux. At least NIO in blocking mode it's worse than
legacy IO. In non blocking mode however it is very good. Oleg has tested that
Hi,
We noticed that the UIL2 architecture (SocketManager) uses many threads:
- 2 (read/write) per connection on the server side
- 2 (read/write) per connection on the client side
So if you have like 20 (EJB3) MDBs with a pool size of each 10 each, then UIL2
will create 20 * 10 * 4 = 400 threads
Portability is not much of an issue for me. We are quite committed to using
JBoss, and moving to another appserver would mean lots of man-years of work
anyway. So a JBoss-only solution that is available now is more welcome than a
portable one that is not available. Anyway, JBoss specific code
So we're left with managing our own threads? To be safe, I suppose we should
perform a JAAS logon, manage a client transaction and use remote interfaces
only, basically acting like an application client.
View the original post :
As there is no documentation on WorkManager at all it would be very nice of the
JBoss people to at least respond to forum postings. Can anybody tell me in what
kind of security and transaction context the work thread will run? E.g. will
the task have to authenticate for EJB calls?
View the
In the loop you should check for Thread.interrupted() anyway. Plus you can
register for a JMX notification about the shutdown. See
http://docs.jboss.com/jbossas/javadoc/4.0.4/system/org/jboss/system/server/Server.html
View the original post :
Thomas, I am trying to come up with a patch. I have some questions:
It looks, although a WSDL file is specified, the meta data is still built from
the Java code. Are there any plans to use the WSDL exlusively in that case?
If you have
@WebMethod f(MyBean a)
the JSR181MetaDataBuilder would
Thanks Thomas for fixing the post.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3992229#3992229
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3992229
___
jboss-user mailing list
Happens in
JBoss AS 4.0.4 with WS 1.0.3, 1.0.3SP1,
JBoss AS 4.0.5 with WS 1.0.4
I have the data model classes in ch.logobject.test.model.ws.
=== WSDL ===
Initially generated by JBossWS from the model. Later modified manually,
deployed in META-INF/wsdl and referenced in the @WebService
Damnit. Can someone fix the HTML escaping in this forum? Look at the mess...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3992013#3992013
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3992013
Allright, I wasn't aware of this option! Of course my DS didn't specify that
option. In my situation I wasn't passing security related information, rather
some other kind of options. I thus find the element name a little misleading.
Anyway, thanks for the tip, Weston.
View the original post :
It seems the JBoss connection manager ignores the ConnectionRequestInfo when
allocating new connections. What I do is:
conn1 = mycf.getConnection(abc);
conn2 = mycf.getConnection(def);
The connection factory basically passes the parameter as a
ConnectionRequestInfo to the
To keep the server.log set the append property to true in your Log4J
appender. See conf/log4.xml.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3990110#3990110
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3990110
On 32 bit architecture the JBoss process can allocate at max. 2GB of memory.
You gave it 1GB of heap. Plus some PermGen. The rest is available to stack
space. Every thread allocates its own stack. This may be 256kb to 1MB depending
on your platform (see you JVM documentation). It's a simple
There was a bug in the first 10g Oracle JDBC driver. Fixed in the latest
version!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3990118#3990118
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3990118
There was a bug in the first 10g Oracle JDBC driver. Fixed in the latest
version!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3990120#3990120
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3990120
I wonder what happened to ServiceEndpointInterceptor. It says in the 1.0.4
release notes that it's a drop-in replacement. But I get
2006-11-16 15:51:53,281 [main] WARN org.jboss.ejb.EjbModule - Could not load
the org.jboss.ws.server.ServiceEndpointInterceptor interceptor
javax.jws.WebService is also in ejb3.deployer/jboss-ejb3.jar and this version
is incompatible with the one in jbossws.sar/jboss-jaxws.jar. This leads to
[exec] java.lang.NoSuchMethodError:
javax.jws.WebService.portName()Ljava/lang/String;
[exec] at
Okay, excellent.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3986567#3986567
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3986567
___
jboss-user mailing list
changing the EJB3 package doesn't help:
[exec] org.jboss.ws.WSException: No wrapped types available
[exec] at
org.jboss.ws.jaxrpc.ParameterWrapping.generateWrapper(ParameterWrapping.java:463)
[exec] at
Version: JBoss EJB-3RC8
I have a simple class hierarchy that uses joined inheritance:
| @Entity
| @Inheritance(strategy=InheritanceType.JOINED)
| public class MaterialMaster {
| private String externalId;
| }
|
| @Entity
| @PrimaryKeyJoinColumn(name=ID)
| public class
How hard can it be to figure out which jar file is missing on your classpath?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3966552#3966552
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3966552
from JNDI
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3966553#3966553
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3966553
___
jboss-user mailing list
On http://trailblazer.demo.jboss.com/EJB3Trail/serviceobjects/jmx/index.html
it says public class CalculatorMBean implements Calculator
If I understand JMX correctly the naming conventions are reversed here. See
http://java.sun.com/j2se/1.5.0/docs/guide/jmx/tutorial/essential.html#wp1053106
37 matches
Mail list logo
