February 2007 - jboss-dev-forums - Jboss List Archives

[Design of the JBoss EJB Container] - Re: org/jboss/util/id/SerialVersion

by opium

Any idea where SerialVersion disappeared in JBoss 4.0.5 GA? ... It was used to allow 4.0.x hosted clients to invoke EJBs in 3.2.x (<3.2.8) beans, through the use of -Dorg.jboss.j2ee.LegacySerialization. Now there is no mention of such a flag in the code, and thus I'm having problems getting my 4.0.5 GA hosted client to connect without serialization exceptions to a 3.2.6 container (due to serialVersion incompatibilities). Any clue? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015606#4015606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015606

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: jboss-messaging-1.2.0.Beta2 failing with Oracle

by ovidiu.feodorov＠jboss.com

We're pushing to get out CR1 in a couple of days. Then, you'll have access to all different persistence configuration files we're supporting. Beta2 is "crippled" in this respect, it only works with MySQL. Stay tuned. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015581#4015581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015581

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: jboss-messaging-1.2.0.Beta2 failing with Oracle

by timfox

If you want to take a look at the completed configs, they're in TRUNK, but you won't find them in any release yet. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015580#4015580 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015580

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: jboss-messaging-1.2.0.Beta2 failing with Oracle

by timfox

That's because in 1.2.0 beta 2 the only persistence manager config that has been completed is the mysql one. For CR1 we will support Oracle, sybase, postgresql, mysql and sql server. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015569#4015569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015569

19 years, 1 month

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Remote Classloading Service Redesign - JBAS-2075

by tom.elrod＠jboss.com

Seems to me should be handled at the invoker level (i.e. UnifiedInvoker) and use a service like the org.jboss.web.WebService we currently have. The WebService actually looks fairly good to me to what is needed (i.e. downloading classes). Maybe add another configuration attribute for what type of class files can be downloaded (i.e. "com.acme.domain.*") and should be sufficient? Also, where is the client code for downloading classes from the WebService? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015548#4015548 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015548

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - jboss-messaging-1.2.0.Beta2 failing with Oracle

by jeffdelong

I tried to run jboss-messaging-1.2.0.Beta2 with Oracle10g and got the following exception on system startup: 2007-02-12 19:09:49,109 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/C:/jboss-ps/jboss-4.0.5.GA/server/messaging/deploy/jboss-messaging.sar/oracle-persistence-service.xml | org.jboss.deployment.DeploymentException: org.jboss.messaging.core.plugin.JDBCPersistenceManager.<init>(); - nested throwable: (java.lang.NoSuchMethodException: org.jboss.messaging.core.plugin.JDBCPersistenceManager.<init>()) | at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196) | at org.jboss.system.ServiceController.install(ServiceController.java:226) | 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:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.install(Unknown Source) | at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249) | at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) | at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | 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:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) | at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) | at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.start(Unknown Source) | at org.jboss.system.ServiceController.start(ServiceController.java:417) | at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy4.start(Unknown Source) | at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) | 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:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy5.deploy(Unknown Source) | at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) | at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) | at org.jboss.Main.boot(Main.java:200) | at org.jboss.Main$1.run(Main.java:490) | at java.lang.Thread.run(Thread.java:595) | Caused by: java.lang.NoSuchMethodException: org.jboss.messaging.core.plugin.JDBCPersistenceManager.<init>() | at java.lang.Class.getConstructor0(Class.java:2647) | at java.lang.Class.getConstructor(Class.java:1629) | at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1232) | at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:286) | at org.jboss.system.ServiceCreator.install(ServiceCreator.java:193) | at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:449) | at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:171) | ... 82 more | 2007-02-12 19:09:49,109 DEBUG [org.jboss.deployment.SARDeployer] Unregistering service UCL=jmx.loading:UCL=578dfb | 2007-02-12 19:09:49,109 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(false) org.jboss.mx.loading.UnifiedClassLoader3@578dfb{ url=file:/C:/jboss-ps/jboss-4.0.5.GA/server/messaging/deploy/jboss-messaging.sar/ ,addedOrder=11} | Oracle worked with the 1.0.1.GA version. FYI I am using an XADatasource. This is on an EJB3 configuration of JBoss 4.0.5.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015539#4015539 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015539

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: WireFormat and flushes

by timfox

Personally I wouldn't worry too much about optimising the HTTP transport for now. People who use the HTTP transport will know it is not designed to be the fastest. We should concentrate on optimising for the default transport, which is going to be the bisocket. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015495#4015495 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015495

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: WireFormat and flushes

by clebert.suconic＠jboss.com

ok... I"m just brain storming about a possible optimization. But I was thinking of the HTTP indeed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015492#4015492 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015492

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: WireFormat and flushes

by timfox

We only ever send one message at a time. (If you forget the http transport for a moment) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015489#4015489 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015489

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: WireFormat and flushes

by clebert.suconic＠jboss.com

As I said before... When I/we do some profiling we will investigate possibilities of optimizations. I don't think there is a problem now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015487#4015487 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4015487

19 years, 1 month

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 February 2007