September 2009 - jboss-user - Jboss List Archives

[JBoss Portal Users] - Re: Removing Dashboard Feature

by PeterJ

The default-object.xml file is used only the first time your run the portal - the data in that file is loaded into a database and from then on the database is used to define the portal layout. Well, that is somewhat of an oversimplification, but sufficient to explain what happened. Since you are running the Portal + AS bundle it is using the Hypersonic database which keeps its data in the server/xxx/data directory. You can start from scratch by removing that directory. So do this: 1) stop the app server 2) remove the server/xxx/data directory 3) edit default-object.xml as I suggested earlier 4) start the app server View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257182#4257182 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257182

15 years

3
2
0 / 0

[Management, JMX/JBoss] - Jmx port automatic binding

by remnet

hi, i try to launch multiple jboss servers, each one with a jmx (rmi) different port. i found the JAVA_OPT setings to activate and bind the agent to one specific port (JAVA_OPTS -Dcom.sun.management.jmxremote.port=xxxxx) but i'd like to know if i can (and how to) use the binding services to proceed like any over default port with a constant port offset like many other services. thx View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243265#4243265 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243265

15 years

2
2
0 / 0

[JBoss Remoting Users] - Re: No ping on secondaryBindPort

by ron.sigal＠jboss.com

What you want to do turn on the following parameters in remoting-bisocket-service.xml: |  | (taken from the recent JBossMessaging release 1.4.0.SP3_CP09), upgrade to Remoting release 2.2.3.SP1 in which the "generalizeSocketException" parameter is introduced, and (possibly - I'm not sure if it's necessary) upgrade JBossMessaging. That should work around the firewall killing idle connections. See JIRA issue JBMESSAGING-1733 "Update settings in remoting-bisocket-service.xml" at https://jira.jboss.org/jira/browse/JBMESSAGING-1733. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258019#4258019 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258019

15 years, 2 months

1
0
0 / 0

[JBoss Remoting Users] - Re: JNDI Lookup Fails, Causes Failed EJB2 MDB

by ron.sigal＠jboss.com

It's certainly not a Remoting issue. I'm going to suggest posting to the "EJB 3.0 Users" forum at http://www.jboss.org/index.html?module=bb&op=viewforum&f=221 . View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258018#4258018 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258018

15 years, 2 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Unable to access WebConsoleMonitoring and WebConsoleSnap

by threecuptea

I found the answer. Java applet console was not installed on Firefox of my Linux box. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258017#4258017 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258017

15 years, 2 months

1
0
0 / 0

[JBoss Remoting Users] - Re: J2EE remote client HTTP tunneling

by ron.sigal＠jboss.com

"bwarren" wrote : | Is JBoss Remoting the way to go here? | Well, as it happens, JBossRemoting is the way you've already gone. EJBs, EJB3s, and JBossMessaging connections all, by default, use JBossRemoting as their transport layer, each, again by default, with their own Remoting servers listening on ports other than 80. However, one of the primary design principles of Remoting is the ability to swap one Remoting transport for another. In your case, you can get closer to your goal with the servlet transport, in which all of the various proxies connect to a Remoting servlet, which then passes the invocations to the appropriate subsystem. Of course, you would need a servlet container (i.e., a JBossWeb (aka Tomcat) connector) listening on port 80. Can you do that? Or will the network powers open up, say, 8080 (the default JBossWeb port in the Application Server - see $JBOSS_HOME/server/$CONFIG/deploy/jboss-web.deployer/server.xml)? The configuration details are given in the wiki entry "EJB, JMS and JNDI over HTTP with Unified Invoker" at http://www.jboss.org/community/wiki/EJBJMSandJNDIoverHTTPwithUnifiedInvoker. What do you think? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258016#4258016 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258016

15 years, 2 months

1
0
0 / 0

[JBoss Remoting Users] - Re: Help Me

by ron.sigal＠jboss.com

I would need more information to know precisely what's going wrong. I'm guessing that the exception occurs in the context of a JBossMessaging connection, where the JBossMessaging server is trying to send some messages to a consumer client. For some reason, the attempt to write the messages to the connection fails. It could be because the client closed unexpectedly. It could be because of a network failure. It could be because a firewall has killed an idle connection. Do any of these sound plausible? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258011#4258011 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258011

15 years, 2 months

1
0
0 / 0

[JBoss Remoting Users] - Re: Infinite lock in MicroSocketClientInvoker

by ron.sigal＠jboss.com

Hi Mayank, "mayankmit2002" wrote : | I'am just unable to set the socket time out at the client end | The timeout isn't set in the initial context call. If you look in $JBOSS_HOME/server/$CONFIG/deploy/ejb3.deployer/META-INF/jboss-service.xml, you'll see the MBean definition | <mbean code="org.jboss.remoting.transport.Connector" | name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"> | <depends>jboss.aop:service=AspectDeployer</depends> | <attribute name="InvokerLocator">socket://${jboss.bind.address}:3873</attribute> | <attribute name="Configuration"> | <handlers> | <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler> | </handlers> | </attribute> | </mbean> | If you add "timeout" to the InvokerLocator attribute, it will be used by the Remoting server defined by the MBean and also by all of its clients: | <mbean code="org.jboss.remoting.transport.Connector" | name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3"> | <depends>jboss.aop:service=AspectDeployer</depends> | <attribute name="InvokerLocator">socket://${jboss.bind.address}:3873/?timeout=10000</attribute> | <attribute name="Configuration"> | <handlers> | <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler> | </handlers> | </attribute> | </mbean> | For more information about Remoting configuration, see Chapter 5 of the Remoting Guide: http://jboss.org/jbossremoting/docs/guide/2.2/html/index.html. -Ron View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258010#4258010 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258010

15 years, 2 months

1
0
0 / 0

[EJB 3.0 Users] - Re: SFSB cycle dependency

by misqu23

"ebu" wrote : Please disregard this stupid question... i've completely forgotten about setters... I have the same problem. Putting @EJB annotation before setter don't work. Do you have some suggestions ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258009#4258009 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258009

15 years, 2 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Unable to access WebConsoleMonitoring and WebConsoleSnapshot

by threecuptea

Hi: I am using Jboss AS: jboss-eap-4.3. I can access web-console using web-console login domain. However, I can only get a bare bone web console. There is no link to see tree view. Definitely, there is no drop down shortcut for WebConsoleMonitoring or WebConsoleSnapshots. How I access WebConsoleMonitoring or WebConsoleSnapshots. in web console? Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258006#4258006 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258006

15 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user September 2009