Re: [jboss-user] [JBoss Messaging] - MDBs using RemoteJMSProvider seem to stop under large number of MDBs
by Mike Miller
Mike Miller [http://community.jboss.org/people/mikemil] replied to the discussion
"MDBs using RemoteJMSProvider seem to stop under large number of MDBs"
To view the discussion, visit: http://community.jboss.org/message/552627#552627
--------------------------------------------------------------
fyi... for anyone that may find my initial post:
I think we have worked thru our problem, which at this point we will categorize as 'bad architecture'. We had a hub & spoke architecture with over 800 spokes. The hub had a remote MDB pointing to each spoke and each spoke had an remote MDB pointing to the hub. The main problem mostly at the hub - using Messaging w/Remoting bisocket - this meant that, if all spokes were connected to the hub, we ended up with over 2400 threads (800 hubs each getting a Connection Consumer thread, along with 2 separate control socket thread (firewall between hub and spokes)) along with everything else our hub server was trying to do.
Data flowed correctly for some time, then things appeared to break and apparently we were getting networking problems on port 4457. We have changed our architecture to no longer use the remote MDBs and seem to be much more stable.
Not sure exactly what in the flow was broken but things are much more stable w/o the remote mdbs - may just too many remote mdbs....
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552627#552627]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months
Re: [jboss-user] [JBoss Remoting] - Remote MDBs seem to stop after marshalling exception
by Mike Miller
Mike Miller [http://community.jboss.org/people/mikemil] replied to the discussion
"Remote MDBs seem to stop after marshalling exception"
To view the discussion, visit: http://community.jboss.org/message/552626#552626
--------------------------------------------------------------
Thanks for the update Ron - looks like 4th of July weekend was time for you to respond to forum posts because I saw a lot of responses.
I think we have worked thru our problem, which at this point we will categorize as 'bad architecture'. We had a hub & spoke architecture with over 800 spokes. The hub had a remote MDB pointing to each spoke and each spoke had an remote MDB pointing to the hub. The main problem mostly at the hub - using Messaging w/Remoting bisocket - this meant that, if all spokes were connected to the hub, we ended up with over 2400 threads (800 hubs each getting a Connection Consumer thread, along with 2 separate control socket thread (firewall between hub and spokes)) along with everything else our hub server was trying to do.
Data flowed correctly for some time, then things appeared to break and apparently we were getting networking problems on port 4457. We have changed our architecture to no longer use the remote MDBs and seem to be much more stable.
Not sure exactly what in the flow was broken but things are much more stable w/o the remote mdbs - may just too many remote mdbs....
Thanks again!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552626#552626]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months
[Beginner's Corner] - Random "Security Context is null" after using SecurityClient
by Nathan Ciliberto
Nathan Ciliberto [http://community.jboss.org/people/snacker] created the discussion
"Random "Security Context is null" after using SecurityClient"
To view the discussion, visit: http://community.jboss.org/message/552620#552620
--------------------------------------------------------------
We have converted most of our ejb's from 2.1 to 3.0.
In order to get the client security to work we had to use the following code to setup the client's context for the ejb3:
SecurityClient client = SecurityClientFactory.getSecurityClient();
client.setSimple( username, password );
client.setVmwideAssociation( true );
client.login();
Once that code has been executed and the ejb invoked we start seeing random errors such as this:
15:01:01,035 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
java.lang.IllegalStateException: Security Context is null
at org.jboss.web.tomcat.security.SecurityAssociationActions$PopRunAsRoleAction.run(SecurityAssociationActions.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.web.tomcat.security.SecurityAssociationActions.popRunAsIdentity(SecurityAssociationActions.java:302)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:193)
at org.jboss.web.tomcat.service.session.ClusteredSessionValve.handleRequest(ClusteredSessionValve.java:135)
at org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:94)
at org.jboss.web.tomcat.service.session.LockingValve.invoke(LockingValve.java:62)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
The error is "random"... and it occurs on any of the servlets that we have configured.
For example we've had 32,000 requests (according to http://myserver:8090/status?full http://myserver:8090/status?full) but only 99 of these errors.
It happens for the servlets/jsps whether they are called directly from the server or via apache by way of mod_jk (ajp3).
Does anyone know why this would happen?
Do we have to setup some "default" security for the servlets/jsps?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552620#552620]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months
[EJB 3.0] - Problem with NotEligibleForDirectInvocationException
by Manu Osten
Manu Osten [http://community.jboss.org/people/argonist] created the discussion
"Problem with NotEligibleForDirectInvocationException"
To view the discussion, visit: http://community.jboss.org/message/552602#552602
--------------------------------------------------------------
Hello,
i want to test with JUnits the methods from session-bean, but the invoke to the methods is not working. I have no idea?
Session-Bean "AccountingBean":
@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
@SuppressWarnings("unchecked")
public Collection<InstitutionType> getInstitutionTypeList() {
final Query query = manager.createQuery("from InstitutionType");
return (Collection<InstitutionType>) query.getResultList();
}
Testcase for getInstitutionTypeList()
@Test
public void testGetInstitutionTypeList() {
if(session == null) {
System.out.println("session is Null");
} else {
System.out.println("session is Not Null");
System.out.println(session.toString());
}
Collection<InstitutionType> typeList = null;
try {
typeList = session.getInstitutionTypeList();
} catch (Exception e) {
e.printStackTrace();
}
Assert.assertNotNull(typeList);
Assert.assertEquals(typeList.size(), 7);
}
Error-Message:
DEBUG [main] (ProxyObjectFactory.java:98) - org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory servicing request for PonteSeam-ear/AccountingBean/remote
DEBUG [main] (MicroSocketClientInvoker.java:253) - SocketClientInvoker[77ff92f5, socket://localhost:3873] constructed
DEBUG [main] (MicroRemoteClientInvoker.java:240) - SocketClientInvoker[77ff92f5, socket://localhost:3873] connecting
DEBUG [main] (MicroSocketClientInvoker.java:735) - Creating semaphore with size 50
DEBUG [main] (MicroRemoteClientInvoker.java:245) - SocketClientInvoker[77ff92f5, socket://localhost:3873] connected
DEBUG [main] (ClientSocketWrapper.java:169) - reset timeout: 0
DEBUG [main] (InvokerRegistry.java:595) - removed SocketClientInvoker[77ff92f5, socket://localhost:3873] from registry
DEBUG [main] (MicroSocketClientInvoker.java:286) - SocketClientInvoker[77ff92f5, socket://localhost:3873] disconnecting ...
DEBUG [main] (SocketWrapper.java:123) - ClientSocketWrapper[Socket[addr=/127.0.0.1,port=3873,localport=45285].b8c3679] closing
DEBUG [main] (SessionProxyObjectFactory.java:130) - Created Proxy of type $Proxy14 for EJB3 Business Interface: de.kirchedlau.ponteseam.sessions.AccountingInterface
lookup
session is Not Null
Proxy to jboss.j2ee:ear=PonteSeam-ear.ear,jar=PonteSeam-ejb.jar,name=AccountingBean,service=EJB3 implementing [interface de.kirchedlau.ponteseam.sessions.AccountingInterface]
DEBUG [main] (SessionProxyInvocationHandlerBase.java:187) - Couldn't handle invocation directly within org.jboss.ejb3.proxy.impl.handler.session.SessionRemoteProxyInvocationHandler@5421e554: Current invocation "public abstract java.util.Collection de.kirchedlau.ponteseam.sessions.AccountingInterface.getInstitutionTypeList()" is not eligible for direct handling by org.jboss.ejb3.proxy.impl.handler.session.SessionRemoteProxyInvocationHandler@5421e554
DEBUG [main] (SecurityAssociation.java:147) - Using ThreadLocal: false
DEBUG [main] (MicroSocketClientInvoker.java:253) - SocketClientInvoker[7e859a68, socket://localhost:3873] constructed
DEBUG [main] (MicroRemoteClientInvoker.java:240) - SocketClientInvoker[7e859a68, socket://localhost:3873] connecting
DEBUG [main] (MicroSocketClientInvoker.java:735) - Creating semaphore with size 50
DEBUG [main] (MicroRemoteClientInvoker.java:245) - SocketClientInvoker[7e859a68, socket://localhost:3873] connected
DEBUG [main] (ClientSocketWrapper.java:169) - reset timeout: 0
java.lang.NullPointerException
at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:379)
at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:53)
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:61)
at $Proxy16.invoke(Unknown Source)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
at $Proxy15.getInstitutionTypeList(Unknown Source)
at de.kirchedlau.ponte.ejb.sessions.AccoutingBeanTest.testGetInstitutionTypeList(AccoutingBeanTest.java:46)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:61)
at $Proxy16.invoke(Unknown Source)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
at $Proxy15.getInstitutionTypeList(Unknown Source)
at de.kirchedlau.ponte.ejb.sessions.AccoutingBeanTest.testGetInstitutionTypeList(AccoutingBeanTest.java:46)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
DEBUG [main] (InvokerRegistry.java:595) - removed SocketClientInvoker[7e859a68, socket://localhost:3873] from registry
DEBUG [main] (MicroSocketClientInvoker.java:286) - SocketClientInvoker[7e859a68, socket://localhost:3873] disconnecting ...
DEBUG [main] (SocketWrapper.java:123) - ClientSocketWrapper[Socket[addr=/127.0.0.1,port=3873,localport=45286].37722456] closing
What is wrong?
Manu
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552602#552602]
Start a new discussion in EJB 3.0 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months
[jBPM] - How to start/spawn 'n' subprocesses for 'n' users using JBPM-4.3.
by Felix Jose
Felix Jose [http://community.jboss.org/people/FelixKJose] created the discussion
"How to start/spawn 'n' subprocesses for 'n' users using JBPM-4.3."
To view the discussion, visit: http://community.jboss.org/message/552599#552599
--------------------------------------------------------------
Hi All,
I am facing a big problem and my requirement I am giving below. Please anybody help me on the same.
Ours is a web application.We are handling the flow of the application by using JBPM.
In a web page we are having a result set of 3 sub users and we can select any number of them using the select button.
If we select 3 of those sub users then it should start 3 JBPM subprocesses for them from the main JBPM process.
And when that 3 selected users logins to the application from different web browsers at the same time,then each JBPM subprocess's state nodes
should be transitioned according to the actions performed by the corresponding users on their respective web sessions/pages.
My doubts are:
1. How to start/spawn 'n' subprocess depending on the selection of 'n' sub users from the result set.( For each sub user there should be a subprocess)
2. How to map each subprocess with each selected sub user's Id. This is for transitioning the corresponding subprocess's state nodes when the respective user
I will be grateful to you if you help me.
Thank you and Regards,
Felix K Jose
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552599#552599]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months
[JBoss AOP] - AOP Instrumentor failed to transform
by M G
M G [http://community.jboss.org/people/mpgong%40lmco] created the discussion
"AOP Instrumentor failed to transform"
To view the discussion, visit: http://community.jboss.org/message/552596#552596
--------------------------------------------------------------
Hello
I'm in the process of upgrading from JBoss AS 5.0 to 5.1 and previously our app was working fine, but after getting things to start up properly, we get the following error and i'm not sure why it is happening. This didn't happen before in 5.0.
Does anyone know why it would not be able to find the org.jboss.aop.Advised?
Thanks
ERROR [org.jboss.aop.instrument.Instrumentor] (pool-12-thread-13) [warn] AOP Instrumentor failed to transform org.nfunk.jep.function.Modulus
javassist.NotFoundException: org.jboss.aop.Advised
at javassist.ClassPool.get(ClassPool.java:436)
at org.jboss.aop.classpool.BaseClassPool.get(BaseClassPool.java:112)
at org.jboss.aop.instrument.Instrumentor.forName(Instrumentor.java:889)
at org.jboss.aop.instrument.Instrumentor.isAdvised(Instrumentor.java:166)
at org.jboss.aop.instrument.Instrumentor.shouldNotTransform(Instrumentor.java:717)
at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:734)
at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:119)
at org.jboss.aop.SuperClassesFirstWeavingStrategy.instrumentClass(SuperClassesFirstWeavingStrategy.java:202)
at org.jboss.aop.SuperClassesFirstWeavingStrategy.translate(SuperClassesFirstWeavingStrategy.java:69)
at org.jboss.aop.AspectManager.translate(AspectManager.java:1071)
at org.jboss.aop.AspectManager.transform(AspectManager.java:1015)
at org.jboss.aop.standalone.AOPTransformer.aspectTransform(AOPTransformer.java:87)
at org.jboss.aop.standalone.AOPTransformer.transform(AOPTransformer.java:75)
at sun.instrument.TransformerManager.transform(TransformerManager.java:169)
at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:365)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552596#552596]
Start a new discussion in JBoss AOP at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months