[JBossCache] - Re: Please vote for your favorite issues -- mine :-)
by bela＠jboss.com
"genman" wrote : 880: I know you and Manik don't believe me, but this is a fundamental feature that most cache services provide as part of their basic API, i.e. put(k, v, ttl).
|
| The dev discussion explains this motivation in detail. I already gave about 3 examples (HTTP cache, session cache, geospatial cache), are these not compelling examples?
|
Why can't they be implemented using regions.
Elias, I'm not really against this, but I'm against adding API (or parameters to existing methods) for things that can be achieved in a different way.
Manik: if we can do this using the Options parameter, then I'm fine with Elias' proposal, otherwise still a -1 from me.
anonymous wrote :
| 841: I don't see how you can implement efficient queries (that is better than O(N)) without some sort of indexing, or in this case per-node sorting.
|
Okay, fine as long as we do *not* need to add the 2 proposed methods to the Node interface, but to the OrderedNode *class*. So I assume this requires another enum to let the Node factory know which type of node to create ? However, if you want to use an OrderedNode, you'd have to narrow Node to OrderedNode.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990754#3990754
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990754
19 years, 5 months
[JBoss AOP] - Re: Pls help with a simple Mixin problem
by fabiocsilva
You can remove the archives .class before compiling the sources. I use a modified version of build file. Try:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <project default="run" name="JBossAOP">
| <property name="jboss.aop.root" value="/opt/project/library/jboss-aop"/>
| <property name="jboss.aop.lib50" value="${jboss.aop.root}/lib-50"/>
| <property name="buildpath" value="${basedir}/bin"/>
| <property name="class.main" value="Driver"/>
|
| <target name="prepare">
|
| <path id="jboss.aop.classpath50">
| <fileset dir="${jboss.aop.lib50}">
| <include name="*.jar"/>
| </fileset>
| </path>
|
| <path id="classpath">
| <path refid="jboss.aop.classpath50"/>
| <pathelement path="."/>
| </path>
|
| <property name="aop50jar" value="${jboss.aop.lib50}/jboss-aop-jdk50.jar"/>
|
| <path id="classpath50">
| <path refid="jboss.aop.classpath50"/>
| <pathelement path="."/>
| </path>
|
| <taskdef name="aopc" classname="org.jboss.aop.ant.AopC" classpathref="jboss.aop.classpath50"/>
| </target>
|
| <target name="clean">
| <delete dir="${buildpath}" />
| <mkdir dir="${buildpath}" />
| </target>
|
| <target name="compile" depends="prepare">
| <javac srcdir="."
| destdir="${buildpath}"
| debug="on"
| deprecation="on"
| optimize="off"
| includes="**">
| <classpath refid="classpath"/>
| </javac>
| <aopc compilerclasspathref="classpath" classpathref="classpath" verbose="true">
| <classpath path="${buildpath}"/>
| <src path="."/>
| <aopclasspath path="."/>
| </aopc>
| </target>
|
| <target name="run" depends="clean,compile">
| <java fork="yes" failOnError="true" className="${class.main}">
| <sysproperty key="jboss.aop.class.path" value="."/>
| <classpath refid="classpath"/>
| <classpath path="${buildpath}"/>
| </java>
| </target>
|
| <target name="compile50standalone" depends="prepare">
| <javac srcdir="."
| destdir="."
| debug="on"
| deprecation="on"
| optimize="off"
| includes="**">
| <classpath refid="classpath50"/>
| </javac>
| </target>
|
| <target name="run.50.instrumented" depends="compile50standalone">
| <java fork="yes" failOnError="true" className="${class.main}">
| <sysproperty key="jboss.aop.class.path" value="."/>
| <jvmarg value="-javaagent:${aop50jar}"/>
| <classpath path="${buildpath}"/>
| <classpath refid="classpath50"/>
| </java>
| </target>
|
| </project>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990749#3990749
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990749
19 years, 5 months
[Installation, Configuration & Deployment] - Ports / bind.address in JBOSS 3.2.3
by ulf.hettstedt
Hi
we are merging our application from IBM Websphere to JBOSS. Since I don't know either Websphere nor JBOSS it became my task. (Actually we just had a company merger and since I am responsible for installations at customer sites, I am now desperately trying to learn everything needed for installations for the (new) product in a very short time).
Back to my task, since the application relies on a Versata Logic Server the JBOSS version to use should be 3.2.3 (maybe 3.2.6 is possible too, but nobody looked into that yet -- 4.05 is far too new,if you get my drift). With this version I am observing the use of a port, which I cannot identify and therefore I cannot configure. It is a random port, which will change everytime I start the "run.bat -b 192.168.168.80" - it is in the range between TCP/1500 and TCP/2400 (and maybe higher). For a configuration behind a firewall this range is a nightmare. Can anybody give me a hint, how to identify this port (I marked it bold in the netstat output below) and furthermore configure it?
This port is essential, I tried to block it, which would prevent our client application to connect to the server. Another strange thing ist, that it doesn't bind to the specified address but to every interface on the server (IP-adress 0.0.0.0)
The goal will be to have more instances of JBOSS-Servers behind a firewall. If there is someone who can give me a hint, why I can't pass the -Djboss.bind.address-Parameter to the run.jar I would be most thankful, too. It doesn't work within the run.bat neither with the Javaservice in the run.bat I tried following lines:
--------------------------------------------------------------------
set JAVA_OPTS=%JAVA_OPTS% -Djava.rmi.server.hostname=Host.domain.name
set JAVA_OPTS=%JAVA_OPTS% -Djava.rmi.server.useLocalHostname=false
set JAVA_OPTS=%JAVA_OPTS% -Djboss.bind.address=192.168.168.80
-------------------------------------------------------------------
Z:\>netstat -nao -p TCP
|
| Aktive Verbindungen
|
| Proto Lokale Adresse Remoteadresse Status PID
| TCP 0.0.0.0:2329 0.0.0.0:0 ABHÖREN 5012
| TCP 0.0.0.0:3389 0.0.0.0:0 ABHÖREN 1508
| TCP 0.0.0.0:18350 0.0.0.0:0 ABHÖREN 5348
| TCP 0.0.0.0:49591 0.0.0.0:0 ABHÖREN 2764
| TCP 0.0.0.0:50000 0.0.0.0:0 ABHÖREN 1008
| TCP 127.0.0.1:1063 0.0.0.0:0 ABHÖREN 188
| TCP 127.0.0.1:2310 127.0.0.1:18350 HERGESTELLT 3252
| TCP 127.0.0.1:18350 127.0.0.1:2310 HERGESTELLT 5348
| TCP 192.168.168.80:1073 192.168.168.20:445 HERGESTELLT 4
| TCP 192.168.168.80:1098 0.0.0.0:0 ABHÖREN 5012
| TCP 192.168.168.80:1099 0.0.0.0:0 ABHÖREN 5012
| TCP 192.168.168.80:1117 192.168.168.20:1026 HERGESTELLT 2716
| TCP 192.168.168.80:4444 0.0.0.0:0 ABHÖREN 5012
| TCP 192.168.168.80:4445 0.0.0.0:0 ABHÖREN 5012
| TCP 192.168.168.80:8009 0.0.0.0:0 ABHÖREN 5012
| TCP 192.168.168.80:8080 0.0.0.0:0 ABHÖREN 5012
| TCP 192.168.168.80:8083 0.0.0.0:0 ABHÖREN 5012
Best regards,
Ulf
* if you happen to find a strange expression: English is not my native tongue --- if you find a typo you are allowed to keep it :) *
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990746#3990746
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990746
19 years, 5 months
[Installation, Configuration & Deployment] - Permission Issue
by Xia
Hello Forum
I recently downloaded and installed jboss on a linux centos4.3 server @ /usr/local/jboss* Everything from jboss down is recursively chown'd by root:root EXCEPT the subfolder deploy @ servers/default/deploy where it's chown'd to our application. Our web application cannot run as root, so it's chown'd and it must create many files and folders within the linux file structure on the server in a grand parent folder. I've tried 3 things and all of them have failed:
1. Everything at /usr/local/jboss was chown'd by root:root recursively as the installation default. The application launched successfully, jboss log recorded no errors but our application was unable to create children/grand children folders.
2. Left everything as chown'd by root in jboss installation but in the deploy subfolder I left everything as root except chown'ing our application. Weird result and nothing worked.
3. Chown'd everything in the deploy subfolder to our application group id; although I got some errors, this was yet the closest I got to the desired behavior.
How do others install jboss? Should the deploy folder be owned by root normally or by an application.war file's group id? Our application is consisted of few war and ear files.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990588#3990588
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990588
19 years, 5 months