June 2009 - jboss-user - Jboss List Archives

[JBoss Messaging] - Re: Cannot find session during shutdown

by timfox

I'm not familiar with this stopDelivery method - I guess this is something added by the EJB team. Like Howard says, perhaps it is doing something illegal, but without seeing the code for it, it would be hard to tell. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234523#4234523 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234523

16 years, 11 months

1
0
0 / 0

[JBoss Messaging] - Re: Cannot find session during shutdown

by gaohoward

Sorry, actually the second case I supposed (shared connection) is unlikely to happen. As if it happened, there wouldn't be error messages like you have got. It should be detected by other clients before reaching that point. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234522#4234522 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234522

16 years, 11 months

1
0
0 / 0

[JBoss Messaging] - Re: Cannot find session during shutdown

by gaohoward

Hi, I think 'session cannot be found' can happen as I explained. To further verify my reasoning, you can try to find in the server's server.log if there is something like: "A problem has been detected with the connection to remote client xxxxxxxxx, jmsClientID=xxxxxxxx. It is possible the client has exited without closing its connection(s) or the network has failed. All associated connection resources will be cleaned up." If not, then I think the connection is probably shared by two or more threads, and one of the thread closed the connection without waiting for other threads finish their work with it. That should be viewed as an application level issue from JBM angle. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234520#4234520 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234520

16 years, 11 months

1
0
0 / 0

[Security & JAAS/JBoss] - Security Features of JBoss AS 5.1

by anil.saldhana＠jboss.com

http://anil-identity.blogspot.com/2009/06/jboss-as-51-security-features.html View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234518#4234518 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234518

16 years, 11 months

1
0
0 / 0

[Beginners Corner] - Re: Transaction not active Error sticks to the Thread causin

by jhalliday

Call UserTransaction.commit or .rollback, which you should be doing in a finally block anyhow. Unless it's CMT, in which case this is a container bug. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234517#4234517 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234517

16 years, 11 months

1
0
0 / 0

[JNDI/Naming/Network] - Re: spi.NotBoundException

by kwesy

I think that EJB3 is not in INSTALLED state but I don't understand why? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234516#4234516 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234516

16 years, 11 months

1
0
0 / 0

[JBoss Cache: Core Edition] - 1.4.1.SP3 - Node availability during nodeRemoved(pre)

by skaffman

Folks, In 1.4.1.SP3, when my treecache listener has its nodeRemove(Fqn, pre, isLocal) is called with pre=true, should the node to which the event refers still be present in the cache? I'm seeing behaviour where the node has already gone by the time nodeRemove(pre=true, isLocal=true) is called. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234514#4234514 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234514

16 years, 11 months

1
0
0 / 0

[JBoss Messaging] - Re: Cannot find session during shutdown

by philipdodds

We have continued to work on this one - and have upgraded to the latest JBoss 5.1.0GA release. This appears to have resolved the problem with the XA transaction - however we are using the stopDelivery method on the EJB3 MDB MBean and are getting a "session cannot be found" during the stopDelivery processing. I'm not certain if it is a problem in the MDB container or the JBoss Messaging configuration, I have opened a discussion over on the EJB3 forum, see: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155887 I really didn't want to cross post stuff but I was wondering if any JBM guys could spot something in the trace, it looks like it rolls back ok - and we are trying to work out whether this is a problem that we need to look into or just the way things are when you stop delivery. Thanks again for all the help View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234511#4234511 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234511

16 years, 11 months

1
0
0 / 0

[JNDI/Naming/Network] - Re: spi.NotBoundException

by kwesy

Hi, all I have the same problem too. I try to retrieve a SessionBean from a service (SAR) at startup time. >From a Web Controller | InitialContext ctx = new InitialContext(); | GroupManagerLocal groupEJB = (GroupManagerLocal) ctx.lookup(GroupManagerLocal.JNDI_NAME); jboss-service.xml <depends>jboss.j2ee:jar=Middleware.jar,name=UserManagerBean,service=EJB3</depends> | <depends>jboss.j2ee:jar=Middleware.jar,name=GroupManagerBean,service=EJB3</depends> | STACK TRACE 17:24:37,274 ERROR [AbstractKernelController] Error installing to Start: name=mib:service=MibScheduleService state=Create mode=Manual requiredState=In | stalled | org.jboss.ejb3.common.registrar.spi.NotBoundException: Object is bound at key jboss.j2ee:jar=Middleware.jar,name=GroupManagerBean,service=EJB3, but is | not fully installed, instead of state: ControllerState@d8bf42{Start} View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234510#4234510 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234510

16 years, 11 months

1
0
0 / 0

[Beginners Corner] - Transaction not active Error sticks to the Thread causing is

by ravichittari

In my application, When the database is stressed I am getting the following error. I believe the txn is getting time out. Caused by: javax.resource.ResourceException: Transaction is not active: tx=TransactionImple < ac, BasicAction: 7f000101:9fd1:4a23167a:263 status: ActionStatus.ABORTED > I am looking into why DB is stressed and figuring that problem out. But the real issue is, once I get this error in the thread, that thread continues to give this error for its life. I am using Jboss 4.2.2 which should work properly for this case. What am I doing wrong? How do I get my thread out of this state? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234509#4234509 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234509

16 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user June 2009