[JBossCache] - Re: Please vote for your favorite issues -- mine :-)
by manik.surtani＠jboss.com
Re: 841
Since with 2.0.0, the node is now a top-level construct, I can see the value in adding comparators to the dataset. I'mnot averse to adding stuff to the API provided it is useful and cohesive to the core offering of JBoss Cache. Again, +1 on the idea.
Functors is a nice genericisation for applying transformations to the data in the cache, and is a useful hook for allowing people to do stuff to the data that we *cannot* foresee or is sufficiently domain-specific, but I think sorting is (a) fairly fundamental to many use-cases and (b) fairly core to any system that organises and stores data.
So +1 on the API.
Again, re: the implementation, I don't think JBoss Retro will support JDK6 -> 4 weaving for a while. And there is no way I'm baselining on 6 for some time to come.
Also, I need to be careful of feature-creep in 2.0.0, so I may defer this to 2.1.0. (Adding an API method at that stage will not break the existing 2.0.0 API)
Unless, that is, this feature (complete with comprehensive test suites and full regression against the existing test suite) is contributed in time for 2.0.0. ;-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990803#3990803
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990803
19 years, 7 months
[JBossCache] - Re: Please vote for your favorite issues -- mine :-)
by manik.surtani＠jboss.com
Re: 880:
No, it's not that I am against this idea, just that I think that this should be a custom extenstion (something a user may implement) rather than a part of the core JBoss Cache product.
Then again, there has been some talk about this on the forums and it is useful for some of our core use cases (inc. http session repl).
Regarding implementation, Elias' impl using an 'expiry' attribute in the node's data map is a little hacky and I don't like the fact that it is not typed so there is no way of checking this, but it is easily customised and extended as a result - plus it has very little impact on the overall arch.
So I'm leaning to a +1 for the feature, and a +-1 on the impl. I'd like to hear more from others (especially users on this forum) before I make a clear decision on this though.
Thanks for providing a prototype on this though, Elias, I do appreciate that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990802#3990802
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990802
19 years, 7 months
[JBoss Seam] - RuntimeException when deploying
by codest
Hi Folks!
I'm new to Seam/EJB/JBoss, but pretty enthuasiastic for what I've seen so far. Please forgive if this might be an easy question, but I've searched around and found nothing on the web or in the forums. Additionally, I'm not sure that I understood everything (components and their dependencies) correctly.
I'm getting this error message on the console while I'm trying to deploy my project:
| 12:53:33,015 INFO [EARDeployer] Init J2EE application: file:/home/joerg/jboss-4.0.4.GA/server/default/deploy/easyCV.ear
| 12:53:34,590 INFO [Ejb3DescriptorHandler] adding class annotation org.jboss.annotation.internal.DefaultInterceptorMarker to de.codest.easyCV.logic.InterviewAction org.jboss.annotation.internal.DefaultInterceptorMarkerImpl@a594e1
| 12:53:34,705 INFO [Ejb3DescriptorHandler] adding class annotation org.jboss.annotation.internal.DefaultInterceptorMarker to de.codest.easyCV.logic.WelcomeAction org.jboss.annotation.internal.DefaultInterceptorMarkerImpl@7a6c34
| 12:53:34,718 INFO [Ejb3DescriptorHandler] adding class annotation org.jboss.annotation.internal.DefaultInterceptorMarker to de.codest.easyCV.logic.profile.KurzprofilAction org.jboss.annotation.internal.DefaultInterceptorMarkerImpl@5292e6
| 12:53:34,731 INFO [Ejb3DescriptorHandler] adding class annotation org.jboss.annotation.internal.DefaultInterceptorMarker to de.codest.easyCV.model.profile.CVProfile org.jboss.annotation.internal.DefaultInterceptorMarkerImpl@75d65c
| 12:53:34,841 INFO [Ejb3DescriptorHandler] adding class annotation org.jboss.annotation.internal.DefaultInterceptorMarker to de.codest.easyCV.model.profile.categories.KurzprofilItem org.jboss.annotation.internal.DefaultInterceptorMarkerImpl@14174f9
| 12:53:34,968 WARN [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=easyCV.jar
| java.lang.RuntimeException: bean class has no local, webservice, or remote interfaces defined and does not implement at least one business interface
| at org.jboss.ejb3.ProxyFactoryHelper.getLocalInterfaces(ProxyFactoryHelper.java:105)
| at org.jboss.ejb3.ProxyDeployer.initializeLocalBindingMetadata(ProxyDeployer.java:117)
| at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:71)
| at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:573)
| at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:555)
| at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:536)
| at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:508)
| at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:463)
| at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:125)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
| at sun.reflect.GeneratedMethodAccessor3.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.create(Unknown Source)
| ...
|
My question: Is there a way to find out to which bean class the message is refering to? This would make it a lot easier to dig deeper.
The last thing I did (as far as I remember) was introducing a SFSB:
| @Stateful
| @Name("CVProfile")
| public class CVProfile implements Serializable, CVProfileInterface {
|
with the following interface:
| @Local
| public interface CVProfileInterface {
|
| public abstract int getCurrentRevision();
| public abstract void addCategory(Category cat);
| public abstract Category getCategory(String name);
| public abstract void destroy();
|
| }
|
But I'm not sure if this is somehow connected to the error. Fact is: The application gets deployed, but it cannot build the first view. Trying to access it from a browser brings:
13:11:12,323 ERROR [STDERR] 03.12.2006 13:11:12 com.sun.facelets.FaceletViewHandler handleRenderException
| SCHWERWIEGEND: Error Rendering View[/home.xhtml]
| org.jboss.seam.InstantiationException: Could not instantiate Seam component: interview
| at org.jboss.seam.Component.newInstance(Component.java:735)
| at org.jboss.seam.Component.newInstance(Component.java:1308)
| at org.jboss.seam.Component.getInstance(Component.java:1263)
| at org.jboss.seam.Component.getInstance(Component.java:1246)
| at org.jboss.seam.jsf.SeamVariableResolver.resolveVariable(SeamVariableResolver.java:44)
| at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:134)
| at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:65)
| at com.sun.el.parser.AstValue.getValue(AstValue.java:106)
| at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192)
| at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
| at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:56)
| at javax.faces.component.UIOutput.getValue(UIOutput.java:75)
| at org.apache.myfaces.renderkit.RendererUtils.getObjectValue(RendererUtils.java:195)
| at org.apache.myfaces.renderkit.RendererUtils.getBooleanValue(RendererUtils.java:152)
| at org.apache.myfaces.renderkit.html.HtmlCheckboxRendererBase.encodeEnd(HtmlCheckboxRendererBase.java:60)
| at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:331)
| at org.apache.myfaces.renderkit.RendererUtils.renderChild(RendererUtils.java:450)
| at org.apache.myfaces.renderkit.RendererUtils.renderChildren(RendererUtils.java:427)
| at org.apache.myfaces.renderkit.html.HtmlGroupRendererBase.encodeEnd(HtmlGroupRendererBase.java:62)
| at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:331)
| at org.apache.myfaces.renderkit.RendererUtils.renderChild(RendererUtils.java:450)
| at org.apache.myfaces.renderkit.html.HtmlGridRendererBase.renderHeaderOrFooter(HtmlGridRendererBase.java:127)
| at org.apache.myfaces.renderkit.html.HtmlGridRendererBase.encodeEnd(HtmlGridRendererBase.java:83)
| at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:331)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:242)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239)
| at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:239)
| at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:554)
| at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:352)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:107)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:30)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:45)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: javax.naming.NameNotFoundException: easyCV not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at org.jboss.seam.Component.instantiate(Component.java:774)
| at org.jboss.seam.Component.newInstance(Component.java:731)
| ... 54 more
|
But I didn't change the interview component since it ran fine, so I think this is a consequence from the first error...
Another question that arose: When I'm using own classes (let's say MyClass) as type for attributes in CVProfile (the implementation), does MyClass have to be a component (having a @Name tag, interface...)? This is where I'm a bit confused about which things need to have Seam tags or interfaces.
Thanks a lot in advance for you help!
Regards,
Jörg
PS: If you need further information, please tell me. Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990792#3990792
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990792
19 years, 7 months
[JBoss Portal] - Re: Problem with HelloWorld IPC sample
by joe_the_quick
hi there,
I have faced the same issue as you do.
The quick solution:
Look into the Jboss Portal Reference Guide 2.6 (http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html_single/#ipc). There you find the correct link to the HelloWorldIPC sample:
http://anonsvn.jboss.org/repos/portletswap/portlets/2_4/bundles/HelloWorl...
I've tested the included SAR-File helloworldipcportlet.sar with Jboss-Portal-2.4.0 and it works immediately, no exceptions show up in the log file. In fact, this is really a nice feature to have.
Issues I've found:
Regarding Jboss Portal 2.2.1:
The provided HelloWorldIPC sample mentioned in the Reference Doc (http://labs.jboss.com/file-access/default/members/portletswap/downloads/p...) does not work with Jboss Portal 2.2.1 SP3.
You get the following exception:
java.lang.NoSuchMethodError: org.jboss.portlet.event.node.WindowActionEvent.getParameters()Lorg/jboss/portal/server/util/Parameters;
org.jboss.portlet.hello.HelloWorldPortletB$Listener.onEvent(Unknown Source)
It seems that the sample requires a method which has not been implemented in Jboss-Portal-2.2.1.
I've inspected the source and found that WindowActionEvent derives from WindowEvent, which supports HashMap getParameters(), but not Parameters getParameter(). This is probably the reason, but I don't know how to fix.
Regarding Jboss Portal 2.4-documentation:
However, the IPC chapter has been (apparently accidentally) completely removed from the Jboss Portal 2.4-documentation (http://docs.jboss.com/jbportal/v2.4/reference-guide/en/html_single/#ipc), althougth IPC is mentioned in the feature list at the beginning.
Regarding Jboss Portal 2.6DR:
The sample of HelloWorldIPC for 2.4 works, but only after deployed HOT. If you deploy it before startup, there are definitely lots of classloading-related exceptions.
best regards,
johannes
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990790#3990790
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990790
19 years, 7 months
[JBoss Seam] - Re: Oracle ADF
by lowecg2004
khaliq/Nusa,
I am also getting the cast exception. I was able to create a regular JSF managed bean and bind/cast to it just fine however, binding to a Seam component caused the cast exception:
Caused by: java.lang.ClassCastException: org.apache.myfaces.trinidad.component.core.data.CoreTable cannot be cast to org.apache.myfaces.trinidad.component.core.data.CoreTable
I can only speculate at this point, but I assume it's something to do with AOP mechanisms changing something about the class during the binding process. Generally in Seam one would be injecting classes based on interfaces or entity beans rather than 'raw' object instance. I would appreciate it if someone could explain what's going on here or direct me to some further reading.
The reason I was binding the table to the Seam component was to get a handle on the component before render response so that I could initialise row selection for the <tr:table ... rowSelection="single"> mode. This requires direct access to the component instance after it has been bound to its data. From what I can tell, my efforts were in vein due to the life cycle of Facelets:
* BEFORE_RENDER_RESPONSE event fired;
* facelets build process starts, binding to my seam component occurs;
* getter is called for the component;
* data model factory is called;
* AFTER_RENDER_RESPONSE event fired;
Basically, the last possible hook into this process (that I could find) was with the getter for the component or even the data model factory (yuk!). Since the actual data model binding occurs after this, there is nothing that I can use to set the selected row keys.
As a general comment, I have been able to do this sort of processing easily under the Java Studio Creator 2 application model using the prerender() method on my backing beans. This is essentially a hook invoked during the BEFORE_RENDER_RESPONSE phase. With this in mind, I tried experimenting with Seam "org.jboss.seam.beforePhase" event but this is fired before facelets even starts building its tree. I understand that the JSC2 approach and the facelets approach are very different, but it does seem odd that there is no way to get at the underlying JSF components before they are rendered. I assume that facelets tree is built during this phase? Or perhaps (probably) I'm missing something, but I have searched for the best part of a day on this and not come across anything.
C.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990788#3990788
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990788
19 years, 8 months
[JBoss Seam] - ICEfaces and EL problem
by sjmenden
I installed Icefaces into my app and got it working, however in turn, it broke the EL.
On my index.xhtml I have a login/logout, the logout will be shown on the evaluation of #{loggedIn}
Which worked pre ICEfaces, when I installed ICEFaces the actual icefaces component worked, but part of my EL stopped working, the part that evaluates variables that don't exist.
When I first open the index.seam in the browser the page has #{loggedIn} however, the variable loggedIn is not created until a user actually logs in. Pre ICEfaces, everything worked great, since I am assuming that loggedIn resolved to null, which I assume equates with false.
In the server.log I tracked down the problem to:
could not resolve variable loggedIn
But no more exceptions or anything, that was all I saw in the debug.
Has anyone else had this problem or a solution?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990775#3990775
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990775
19 years, 8 months
[Security & JAAS/JBoss] - Re: JAAS newbie - missing something that should be obvious
by grego＠spiekerpoint.com
"jaikiran" wrote :
| | Change it to:
| |
| | | <?xml version="1.0" encoding="UTF-8"?>
| | | <jboss-web>
| | | <security-domain>SPDB</security-domain>
| | | </jboss-web>
| |
| | and give it a try.
Ok - nice - that worked well! Thank you!!!
One question on the next part. Now the error report from the jboss console says:
14:23:52,491 ERROR [JBossSecurityMgrRealm] Error during authenticate
| javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: SPDB not bound]
|
|
But the login-config.xml file clearly has the SPDB section in it... Do I need to expressly tell JAAS about the new application pollicy? <and I have restarted jboss after adding the section to the login-config.xml file>
Should I be moving the EJB security-domain over to that as well? as in (jboss.xml):
| <jboss>
| <security-domain>java:/jaas/SPDB</security-domain>
| </jboss>
|
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990766#3990766
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990766
19 years, 8 months
[JBoss Portal] - Spring Portlet Instance is not created
by abhilashk_cse
I am facing some problems while deploying Spring portlet in JBoss Portal 2.4. I have created a Spring Portlet in the same way the Books portlet of JBoss Examples have done. I have deployed the war file in the deploy directory and try to access it from main portal. Only the Page is created not the portlet instance.
---------------------------------------------------------------------------------
Error messages:
---------------------------------------------------------------------------------
00:36:34,045 ERROR [AbstractKernelController] Error installing to Start: name=po
rtal:container=Portlet,id=/jboss-salesojects.leads state=Create
org.jboss.portal.portlet.container.PortletInitializationException: The portlet l
eads threw an error during init
00:36:37,607 WARN [InstanceMetaData] The instance LeadsPortletInstance will not
be created because the component referenced is outside of the same web app /jboss-salesobjects.leads
00:36:37,686 WARN [PortletAppDeployment] Failed to create instance LeadsPortlet
Instance of portlet /jboss-salesojects.leads because portlet /jboss-salesojects.
leads is not available
---------------------------------------------------------------------------------
jboss-salesobjects is my war name.
---------------------------------------------------------------------------------
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990765#3990765
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3990765
19 years, 8 months
[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, 8 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, 8 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, 8 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, 8 months