August 2008 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Behavior difference in intra-AS EJB calls

by bstansberry＠jboss.com

An FYI; not necessarily a problem. I'm seeing a difference in behavior when a bean in one AS looks up a bean in another AS and then invokes on it.[1] Previously that call would go remote; now it stays local if the same bean is deployed locally. This is because of the change in how proxy factories are created. Previously they were built on the server and downloaded. Now they are built on the client. Effect is IsLocalProxyFactoryInterceptor.isLocal() will *always* return true. I don't know if this is an acceptable behavior change or not. I do think it should be overridable; for EJB2 beans I often see forum requests wanting to know how to override "local-preference". For EJB2 this can be overridden by writing a simple custom extension of a JBoss class, which can then be configured in on a per-bean basis. For EJB3 the equivalent override would be a bit more complex (customized IsLocalProxyFactoryInterceptor and extension of all the ObjectFactory impls to override createProxyFactoryProxy). But if that's done I don't see any way to configure the new classes on a per-bean basis. The JndiSessionRegistrarBase impls to use are hard coded. [1] e.g. | public VMID getVMIDFromRemoteLookup(String jndiURL, String name) | throws NamingException | { | log.info("Looking up " + jndiURL + "/" + name); | Properties env = new Properties(); | env.setProperty(Context.PROVIDER_URL, jndiURL); | env.setProperty("jnp.disableDiscovery", "true"); | InitialContext ctx = new InitialContext(env); | VMTester tester = (VMTester) ctx.lookup(name); | return tester.getVMID(); | } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172041#4172041 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172041

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by jaikiran

Ok, I will include this in the patch and update the JIRA soon :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172037#4172037 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172037

17 years, 7 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: variable inside task controller

by kukeltje

this might be changed in 4.0, not sure though. 3.x will not be adapted for this. and btw, you can add any element to the pd because of the <xs:sequence> | <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> | </xs:sequence> | If if you retrieve the pd from the database (search the forum for that) you can access those elements and use the values anyway you want View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172021#4172021 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172021

17 years, 7 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: java.io.StreamCorruptedException: invalid stream header

by jfrederic.clere＠jboss.com

That is a JGroups problem: please post in the right forum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4172014#4172014 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4172014

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBoss with spaces in the directory name

by mstruk

I was checking if spaces issue is fixed and it doesn't seem to be. So tracing it back to the source I'm seeing test failures in jboss-common-core: | Running org.jboss.test.util.test.propertyeditor.PropertyEditorsUnitTestCase | file:/C:/path%20with%20space/tst.xml != file:/path with space/tst.xml | Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.155 sec <<< FAILURE! | The failing test is the one testing URL encoding/decoding: | Transform(org.jboss.util.propertyeditor.URLEditor@7e5a9de6) of file:/path with space/tst.xml equals file:/C:/path with space/tst.xml, output=file:/C:/path%20with%20space/tst.xml | As if JBCOMMON-60 has crept back ... - marko View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171999#4171999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171999

17 years, 7 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - java.io.StreamCorruptedException: invalid stream header in J

by aakanksha

Hello, I am getting the following exception in jboss server. 2008-08-22 08:49:44,978 ERROR [org.jgroups.protocols.UDP] exception=java.io.StreamCorruptedException: invalid stream header atjava.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:764) at java.io.ObjectInputStream.(ObjectInputStream.java:277) at org.jgroups.protocols.UDP.handleIncomingUdpPacket(UDP.java:670) at org.jgroups.protocols.UDP$IncomingPacketHandler.run(UDP.java:1332) at java.lang.Thread.run(Thread.java:595) Please reply ASAP. This exception is coming in logs after every second. Please help me to solve this problem.Thank you :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171958#4171958 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171958

17 years, 7 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: problem with jboss profiler 2.0 beta 2 on jboss version

by Huijuan Shao

Please find your localhost's address and bind that when JBoss starts up. In you run in Linux, you can find the address by command: hostname -i View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171942#4171942 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171942

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Cleanup problem with Ejb3Registrar and proxy factories

by ALRubinger

OK, Ejb3Registrar is intended to be an MC Abstraction, so it looks like in hiding MC's notion of a ControllerState I've allowed an object to remain in limbo https://jira.jboss.org/jira/browse/EJBTHREE-1472 S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171934#4171934 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171934

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Cleanup problem with Ejb3Registrar and proxy factories

by bstansberry＠jboss.com

This post is specifically about code in the proxy module, but I think it might point to a general issue with Ejb3McRegistrar. Cutting to the chase, it looks like Ejb3McRegistrar leaves no way to back out a failed bind() call. I had a test with a misnamed deployment descriptor, which led to a failure in proxy factory registration: | 2008-08-21 18:50:39,196 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (RMI TCP Connection(18)-192.168.1.146) Error installing to Start: name=ProxyFactory/ClusteredStatefulRemote state=Create | java.lang.IllegalStateException: Partition Ejb3IsLocalTestPartition not found | at org.jboss.ha.framework.server.HAPartitionLocator.getHAPartition(HAPartitionLocator.java:124) | at org.jboss.ejb3.proxy.clustered.registry.ProxyClusteringRegistry.registerClusteredBean(ProxyClusteringRegistry.java:114) | at org.jboss.ejb3.proxy.clustered.factory.session.stateful.StatefulSessionClusteredProxyFactory.start(StatefulSessionClusteredProxyFactory.java:111) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | ..... | at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:106) | at org.jboss.ejb3.common.registrar.plugin.mc.Ejb3McRegistrar.install(Ejb3McRegistrar.java:309) | at org.jboss.ejb3.common.registrar.plugin.mc.Ejb3McRegistrar.bind(Ejb3McRegistrar.java:163) | at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.registerProxyFactory(JndiSessionRegistrarBase.java:906) | ..... | That's fine; it was a bad deployment. But the problem is the undeploy didn't properly clean up: | 2008-08-21 18:50:39,264 DEBUG [org.jboss.ejb3.stateful.StatefulContainer] (RMI TCP Connection(18)-192.168.1.146) Failed to cleanup after start() failure | org.jboss.ejb3.common.registrar.spi.NotBoundException: Requested value bound at name "ProxyFactory/ClusteredStatefulRemote" is not bound. | at org.jboss.ejb3.common.registrar.plugin.mc.Ejb3McRegistrar.lookup(Ejb3McRegistrar.java:91) | at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.deregisterProxyFactory(JndiSessionRegistrarBase.java:934) | at org.jboss.ejb3.proxy.jndiregistrar.JndiSessionRegistrarBase.unbindEjb(JndiSessionRegistrarBase.java:477) | at org.jboss.ejb3.session.SessionSpecContainer.lockedStop(SessionSpecContainer.java:732) | at org.jboss.ejb3.stateful.StatefulContainer.lockedStop(StatefulContainer.java:324) | at org.jboss.ejb3.stateful.StatefulContainer.lockedStart(StatefulContainer.java:308) | at org.jboss.ejb3.EJBContainer.start(EJBContainer.java:855) The effect of this is the "ProxyFactory/ClusteredStatefulRemote" bean was left registered in the MC, but not in an installed state. When later tests would deploy the same jar, they would all fail with "java.lang.IllegalStateException: ProxyFactory/ClusteredStatelessRemote is already installed". AFAICT, the only way to clean this up is to reboot the server. There's a couple levels of issues here: 1) JndiSessionRegistrarBase.deregisterProxyFactory is doing a Ejb3Registrar.lookup before doing an unbind. It does this so it can make some assertions. Problem is Ejb3McRegistrar implements lookup by calling KernelController.getInstalledContext(). That will return null in this case, because "ProxyFactory/ClusteredStatefulRemote" never made it to ControllerState.INSTALLED. As a result, lookup() throws an exception. 2) If Ejb3McRegistrar.lookup() somehow was changed to get past that problem and find the ControllerContext, I believe it would still fail, because it checks ControllerContext.getError() and throws an exception if it finds one. 3) Even if the JndiSessionRegistrarBase.deregisterProxyFactory's call to Ejb3Registrar.lookup() were eliminated and the method went directly to Ejb3Registrar.unbind(), it would still fail because the first thing Ejb3McRegistrar.unbind() does is call lookup(). :-) Bottom line, it looks like Ejb3McRegistrar leaves no way to back out a failed bind() call. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171931#4171931 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171931

17 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Classloading problem in proxy factories

by bstansberry＠jboss.com

https://jira.jboss.org/jira/browse/EJBTHREE-1471 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4171927#4171927 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4171927

17 years, 7 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-dev-forums August 2008