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

[Design of JBoss Web Services] - RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

This dev forum topic will accumulate investigation results of research on RM Sender/Receiver as High Available (HA) Components It relates to bug http://jira.jboss.org/jira/browse/JBWS-1976 and was initiated by the following discussion http://www.jboss.org/index.html?module=bb&op=viewtopic&t=126278 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126102#4126102 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126102

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: JBossTS overriding commons-logging discovery mechanism

by jhalliday

The JBossTS code sets its own logger because we have a custom implementation that supports internationalization. As far as I can tell the problem is that all the other AS code expects the log factory to have the default configuration, so is not setting it explicitly. Thus if it runs after the JBossTS code has modified the factory configuration it is getting unexpected results. One simple (although not threadsafe) option may be for the JBossTS code to reset the original factory config when it is done instantiating its own loggers. I'm not clear why other code would be affected by the changing of log level for messages. That code is not part of the custom Log4JLogger, but rather done via a wrapper around it, so it should not get picked up except by the JBossTS logging system. Is there a test case that shows where this level changing is affecting other pats of the AS? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126096#4126096 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126096

18 years, 2 months

1
0
0 / 0

[Design of Management Features on JBoss] - Twiddle SocketTimeoutException

by deadwood

Hello, I apologize if I picked the wrong section or forum. I am just a JBoss plagued sysadmin who isn't into Java or JBoss. So I don't even know the JBoss elementary basics. I simply need to monitor those Jbosses that my HP-UX ServiceGuard cluster nodes host as packages. To this end I urge to script a Nagios or Munin plugin to simply monitor our jbosses and fetch thread counts and memory usage etc. First I tried the JMX URI as I did in my plugins that monitor our Tomcats. But except for the jmx-console where a logged-in admin could watch and change config parameters what isn't the aim of my monitoring plugin, I haven't found anything suitable to parse. Then I somehow discovered that Twiddle script which looked like a simple wrapper to invoke a Java method to possibly get some basic performance data dumped. I checked its contents, especially the environment settings, for proper classpaths and jar files etc and presence of the latter on the cluster nodes. According to the path name we run JBoss 4.0.2 instances. I have no idea if these are still supported or remotely up to date. The OS is HP-UX B.11.11 When I invoke the twiddle.sh with a get call after a few seconds (probably the default timeout) I get the below dumped exception thrown. Not being a Java hacker I hope my interpretation of the call trace is correct in that the connect to a socket (is it a Unix domain socket, as this was run on localhost, or INET?) simply timed out. Looks to me as if this interface hasn't been configured yet. Could you please tell me where and what to configure to make the twiddle command successfully connect and communicate with the JBoss server? Regards | # JAVA_HOME=/opt/java1.5 ./twiddle.sh get jboss.system:type=ServerInfo | 11:29:28,780 ERROR [Twiddle] Exec failed | org.jboss.util.NestedRuntimeException: Receive timed out; - nested throwable: (javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]) | at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:137) | at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:47) | at org.jboss.console.twiddle.command.GetCommand.execute(GetCommand.java:137) | at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:293) | Caused by: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] | at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1302) | at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1382) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579) | at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572) | at javax.naming.InitialContext.lookup(InitialContext.java:351) | at org.jboss.console.twiddle.Twiddle.createMBeanServerConnection(Twiddle.java:244) | at org.jboss.console.twiddle.Twiddle.connect(Twiddle.java:262) | at org.jboss.console.twiddle.Twiddle.access$300(Twiddle.java:56) | at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:133) | ... 3 more | Caused by: java.net.SocketTimeoutException: Receive timed out | at java.net.PlainDatagramSocketImpl.receive0(Native Method) | at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136) | at java.net.DatagramSocket.receive(DatagramSocket.java:729) | at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1272) | ... 11 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126094#4126094 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126094

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: FIELD granularity web session replication tests

by kabir.khan＠jboss.com

AOP of classes from the WEB-INF/classes directory is broken following the changes to the war classloaders, I am looking into it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126087#4126087 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126087

18 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - auto creating queues, security and invaliddestination

by ataylor

We need to decide how security will work with regard to creating queues at a core level and also how this links to when(and how) we should throw InvalidDestination at a JMS level. This is how i think all his should hang together: When a client interacts with a destination at a session level we check to see if they have the CREATE role. This would be a method, probably in MessagingServer, called boolean CheckDestinationSecurity(Destination dest, ServerSessionEndpoint) that would create the destination if it didn't exist and if the client had the correct privileges. If the destination wasn't created then the appropriate return flag would be returned to the user. This would be converted into an InvalidDestination exception on the client side at the JMS level. comments! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126081#4126081 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126081

18 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Identity management docs

by heiko.braun＠jboss.com

anonymous wrote : I don't know yet what the best layer is to plug in the ws security. Well, for the protocol it's the username token profile. The current JBossWS implementation delegates to JAAS as well. So we may just delegate to the jbpm security domain for WS authentication. >From what I understand, the WS facade doesn't need to bother about further authorization, does it? That would be: WS -> WSSE -> JAAS -> JBPM (WSSE is webservice security) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126069#4126069 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126069

18 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Identity management docs

by tom.baeyens＠jboss.com

i don't know yet what the best layer is to plug in the ws security. meaning the SQL/JDBC level or the Java/hibernate level. i would say: whatever is most convenient. i assume that whatever security we use, it will be optional right. cause i think that not all clients will know on behalf of which user they are running the code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126058#4126058 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126058

18 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Identity management docs

by tom.baeyens＠jboss.com

"Who's maintaining that code?" that would be me, i guess :-) the jbpm identity component is pretty straight forward. there are 3 main classes User, Group and Membership. These are mapped to the database to 3 tables. in module jbpm.3/jboss/configuration, there are (per AS version) a number of configuration files. in the login-config.xml there is the declaration of the jbpm security domain. it is a database login module that checks the user name and password in the database. it also extracts the roles from the DB tables as follows: <application-policy name = "jbpm"> | <authentication> | <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" | flag="required"> | <module-option name="dsJndiName">java:/JbpmDS</module-option> | <module-option name="principalsQuery"> | SELECT PASSWORD_ FROM JBPM_ID_USER WHERE NAME_=? | </module-option> | <module-option name="rolesQuery"> | SELECT g.NAME_ ,'Roles' | FROM JBPM_ID_USER u, | JBPM_ID_MEMBERSHIP m, | JBPM_ID_GROUP g | WHERE g.TYPE_='security-role' | AND m.GROUP_ = g.ID_ | AND m.USER_ = u.ID_ | AND u.NAME_=? | </module-option> | </login-module> | </authentication> | </application-policy> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126056#4126056 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126056

18 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: [sim] First tutorial finished

by tom.baeyens＠jboss.com

thanks ! This is great stuff. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126055#4126055 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126055

18 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Potential enhancement to jbpm

by tom.baeyens＠jboss.com

Let's see if i get this right. In jPDL 4 i want to add annotations. Basically, annotations are key-value pairs that you can associate to all process elements. As extensions would like more infomation inside of the process (UI forms, simulation, prediction,...) they can be added in a standard way without the need to write a parser for it. e.g. <task name="ship"> | <annotations> | <string name="task.form" value="ship.xhtml" /> | ... | </annotations> | </task> in jPDL 4, there will be one way on how to write objects in xml. it will be used here for annotations, but also for the configuration file and to specify initial values for variables. alternatively users should be able to write their own parsers to extract the information from a process archive and put that information somewhere in the process definition. does this feature match the requirement that you both are explaining ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126054#4126054 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126054

18 years, 2 months

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 2008