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

[Design of JBossCache] - Re: Should users be notified of replication failures via a c

by bela＠jboss.com

Here's the use case: - Node A and B - A made a modification, sends the replication *asynchronously* to B. Can also be synchronous, just *no* TX - B cannot apply it, e.g. because some other TX has locked the data - The lock acquisition timeout on B kicks in and we don't apply the change on B - A will have applied the change, but not B - This is without TXs, or even with a TX but in async mode - It would be good if we had a callback that was called on B if the replication could not be applied successfully. - A cache exception does not work here, as the caller doesn't wait, and even if it did, we cannot throw an exception if we send the modification to B,C,D, and only B fails View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033181#4033181 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033181

17 years, 1 month

1
0
0 / 0

[Design of JBossCache] - Re: Should users be notified of replication failures via a c

by bstansberry＠jboss.com

This confused me. Is this meant to be done on the replication recipient side? In that case I understand the callback idea, as an Exception will just propagate back to the RPC handler and be dropped. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033177#4033177 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033177

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Javabean xml test are failing

by adrian＠jboss.org

The tests are failing because the 2.0 schema is not registered in the JBossEntityResolver only the 1.0 schema is there | registerEntity("urn:jboss:javabean:1.0", "javabean_1_0.xsd"); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033169#4033169 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033169

17 years, 1 month

1
0
0 / 0

[Design of JBossCache] - Should users be notified of replication failures via a call

by manik.surtani＠jboss.com

This thread is for JBCACHE-1015. My opinion is that cluttering up the listener is not how I would ideally like to do this - I'd prefer to throw a CacheException as it is an exceptional circumstance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033165#4033165 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033165

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by bill.burke＠jboss.com

Quit ranting. EJB3 is an integration project. Its not our fault that the things we interface with don't have any SPIs!!! What exact integration work is EJB3 doing besides providing its own MEP and queue/topic creation(which we removed in head)? What exact constraints are you talking about that EJB3 places on other projects? What code is forked? Are you still living in 2006? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033161#4033161 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033161

17 years, 1 month

1
0
0 / 0

[Design of JBoss Internal Benchmarking] - Missing files problem with jboss-specjAppserver2004 setup

by sudheer_pisces

I have been trying to setup SPECjAppserver2004 on Jboss, I have used jboss version 4.05-GA and the jboss-specj kit version 1.3.7 for the setup. The emulator, SUT and the database server are on different machines. On the emulator machine, Jboss server fails to start, it says that the jboss-service.xml file is missing. I have found that some files are not created by ant in the $JBOSS_EMULATOR_HOME/server/$JBOSS_EMULATOR_SERVER_NAME directory. The error message that I get is as follows : ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /usr/local/jboss-4.0.5.GA JAVA: /usr/java/jdk1.6.0/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: /usr/local/jboss-4.0.5.GA/bin/run.jar:/usr/java/jdk1.6.0/lib/tools.jar ========================================================================= 15:06:32,865 INFO [Server] Starting JBoss (MX MicroKernel)... 15:06:32,867 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) 15:06:32,870 INFO [Server] Home Dir: /usr/local/jboss-4.0.5.GA 15:06:32,871 INFO [Server] Home URL: file:/usr/local/jboss-4.0.5.GA/ 15:06:32,873 INFO [Server] Patch URL: null 15:06:32,873 INFO [Server] Server Name: emulator 15:06:32,873 INFO [Server] Server Home Dir: /usr/local/jboss-4.0.5.GA/server/emulator 15:06:32,874 INFO [Server] Server Home URL: file:/usr/local/jboss-4.0.5.GA/server/emulator/ 15:06:32,874 INFO [Server] Server Log Dir: /usr/local/jboss-4.0.5.GA/server/emulator/log 15:06:32,875 INFO [Server] Server Temp Dir: /usr/local/jboss-4.0.5.GA/server/emulator/tmp 15:06:32,876 INFO [Server] Root Deployment Filename: jboss-service.xml 15:06:33,487 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc. 15:06:33,487 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0-b105,Sun Microsystems Inc. 15:06:33,487 INFO [ServerInfo] OS-System: Linux 2.4.20-8smp,i386 15:06:33,916 INFO [Server] Core system initialized Failed to boot JBoss: org.jboss.deployment.DeploymentException: url file:/usr/local/jboss-4.0.5.GA/server/emulator/conf/jboss-service.xml could not be opened, does it exist? at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:214) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:781) 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:597) 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 $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:619) 15:06:33,951 INFO [Server] Runtime shutdown hook called, forceHalt: true 15:06:33,952 INFO [Server] JBoss SHUTDOWN: Undeploying all packages 15:06:33,964 INFO [Server] Shutdown complete Shutdown complete Halting VM The jboss-MySQL-run.properties file on the machine is as follows: #-------------- #SPECJ home #-------------- JAS_HOME=/usr/local/SPECjAppServer2004-1.05 #-------------- #Driver configuration #-------------- TXRATE=50 OUTDIR=/usr/local/SPECjAppServer2004-1.05/output DUMPDIR=/tmp/specj TRIGGERTIME=50 RAMPUPTIME=600 STDYSTATETIME=1800 RAMPDOWNTIME=300 #-------------- #SUT configuration #-------------- JBOSS_HOME=/usr/local/jboss-4.0.5.GA JBOSS_URL=http://10.107.26.6:8080 APPLICATION_HOST=10.107.26.6 APPLICATION_PORT=8080 server-name=specj2004 #-------------- #Emulator configuration #-------------- JBOSS_EMULATOR_HOME=/usr/local/jboss-4.0.5.GA JBOSS_EMULATOR_HOST=10.107.26.23 JBOSS_EMULATOR_PORT=8080 JBOSS_EMULATOR_SERVER_NAME=emulator #-------------- #specj2004 database #-------------- JDBC_URL=jdbc:mysql://10.107.26.43/specj2004 JDBC_DRIVER=com.mysql.jdbc.Driver JDBC_USER=specj2004 JDBC_PASSWORD=specj2004 JDBC_DATASOURCE_NAME=SpecjDS JDBC_DATASOURCE_NAME_RC=SpecjDS_RC JDBC_DATASOURCE_NAME_RR=SpecjDS_RC JDBC_DATASOURCE_NAME_RC.MIN=0 JDBC_DATASOURCE_NAME_RC.MAX=500 JDBC_DATASOURCE_NAME_RR.MIN=0 JDBC_DATASOURCE_NAME_RR.MAX=500 #-------------- #jms database #-------------- JMS_JDBC_URL=jdbc:mysql://10.107.26.43/jbossjms JMS_JDBC_DRIVER=com.mysql.jdbc.Driver JMS_JDBC_USER=jbossjms JMS_JDBC_PASSWORD=jbossjms JMS_JDBC_DATASOURCE_NAME=SpecjJMSDS #-------------- #Datasources configuration #-------------- JDBC_DATASOURCE_MAPPING=mySQL #DRIVER_JAVA_PARAMETERS= server-database=mySQL -- Regards, sudheer_pisces View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033151#4033151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033151

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by adrian＠jboss.org

In general we should be trying to simplify the platform. We should be letting each area get on with what it does best. EJB3 is not an integration api, JCA is. The JBoss EJB3 implementation is still doing far too much integration work itself which is continually a problem both in terms of not reusing code that is known to work, but also in terms of the portablity as these integration details change. In some cases, constraints are being imposed on other projects where EJB3 is using api that was never intended for external use. Webservices has the exact same problem which is why I was complain about them breaking the build all the time. It should be the AS (or in future "JBoss Embedded") that defines a portable integration api for EJB3/Webservices to hook into not EJB3/Webservices each doing their own "broken" integrations with every other project including the AS itself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033107#4033107 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033107

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Implicit container dependencies

by adrian＠jboss.org

This thread is really getting off topic. :-) EJB3 should be doing anything with JBoss Messaging. If anything should be doing this, it is the resource adapter. e.g. there should be an activation spec property called "createDestination" The resource adapter could then be updated to use the admin class, or my preference would be something like this: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033100#4033100 which should really be in the JMS spec. This approach maps to other inbound adapters like AMPQ which does define a portable management api. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033104#4033104 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033104

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Managing JMS using JMS

by adrian＠jboss.org

I suggested this before, but I don't think I wrote it up fully in the forums so here goes. It should be possible to manage JMS using JMS, i.e. create queues, topics, connection factories by sending messages to a management queue (which is suitably secured). It would then possible to do something like: | queue = (Queue) jndi.lookup(JBossJMS.ManagementQueueName): | QueueRequestor r = new QueueRequestor(session, queue); | Message request = session.createMessage(); | request.setStringProperty(JBossJMS.OPERATION, JBossJMS.CREATE_QUEUE); | request.setStringProperty(JBossJMS.DESTINATION_NAME, "myQueue"); | request.setIntegerProperty(JBossJMS.QUEUE_DEPTH, 1000); | // etc. | Message response = r.request(m); | // check the response | More likely would create a class that does all this boiler plate for you, e.g. | manager = new JBossJMSManagement(session); | QueueTemplate template = manager.createQueueTemplate(); | template.setQueueDepth(1000); | manager.createQueue("myQueue", template); | Once this is done, JBossMQ could also implement a queue that handles the same requests which would provide portability across releases. This is superior to the JMX approach since it will also work "remotely". In fact, the location of the jms server is transparent and automatic based on the connection factory the user looks up. If this had been done when I first requested it, people could have already been using it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033100#4033100 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033100

17 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - logout from my portal instance

by psalvadori

Hi all, I'm an old user of the 2.2 version of the JBoss Portal. I'm studing the new version (2.6) and I found a problem. I created a new portal instance directly from web interface, with the admin tools. Then I created a new role and a new User to access to the new portal instance. After this I Signed in in my new portal instance and all was OK. But when I signed out, I was redirected automatically to the default page of the default portal, instead of the current page of my portal instance. I'd like to know if it is a bug of the alpha version or if there is a way to redirect where I want to. Thanks, Paolo. my configuration Linux Fedora Core 5 jboss-portal-2.6-bundled View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033094#4033094 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033094

17 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2007