October 2006 - jboss-user - Jboss List Archives

[Performance Tuning] - Re: Jar Isolation Not Working

by wcydaip

Thanks. Sorry 'bout the forum, seemed right at the time. That http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration reads abit clunky, but, makes sense after the hundreth time. So, basically, you just need to add the meta-inf/jboss-app.xml to a deployment and at least the ear isolation is achieved. | <jboss-app> | <loader-repository> | myapp:loader=myapp.ear | </loader-repository> | </jboss-app> | Thanks again, I was about to give up and fully resent the modules I created. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976124#3976124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976124

19 years, 7 months

1
0
0 / 0

[EJB 3.0] - Re: Automatic Destroy State in Stateful Session Bean

by grdzeli_kaci

ok, I find another problem : 1.i have interface | package com.magti.businesslayer.ejb3entity.oracle; | | import javax.ejb.Remote; | | @Remote | public interface MyState { | public void initialize(); | } | 2. Implementation : | package com.magti.businesslayer.ejb3entity.oracle; | | import javax.ejb.Remote; | import javax.ejb.Stateless; | | @Stateless | @Remote(MyState.class) | public class StateBean implements MyState | { | String name = null; | | public void initialize() | { | if (name == null) | { | System.out.println("Null"); | name = "Initialize"; | } | else | { | System.out.println("Not Null -> "+name); | } | } | } | 3. Test Client package com.magti.businesslayer.ejb3entity.oracle; import java.util.Properties; import javax.naming.Context; import javax.naming.InitialContext; public class TestMain { public static void main(String[] args) { try { Properties jndiProps = new Properties(); jndiProps.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); jndiProps.setProperty(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interface"); jndiProps.setProperty(Context.PROVIDER_URL, "jnp://192.168.9.136:1099"); InitialContext ctx = new InitialContext(jndiProps); MyState state = (MyState) ctx.lookup("StateBean/remote"); state.initialize(); } catch (Exception e) { e.printStackTrace(); } } } | | when i run client fierst time i get this result : | 21:47:33,652 INFO [STDOUT] Null | | second time : | 21:47:34,652 INFO [STDOUT] Null | | third time : | 21:47:35,652 INFO [STDOUT] Initialize | | forth time | 21:47:36,652 INFO [STDOUT] Initialize | | fifth time : | 21:47:37,652 INFO [STDOUT] Initialize | | ..... | ..... | | | can anybody explain me why ? | | this session bean is stateless. | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976122#3976122 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976122

19 years, 7 months

1
0
0 / 0

[JBoss jBPM] - Re: SOAP Fault Exception - BPEL ATM Example

by KVAK_TNT

Hi again! I have upgraded to beta2 and still got the "Premture end of file error"... But now I get it allways I have successfully started an operation in the wsdl. 20:00:15,488 ERROR [STDERR] [Fatal Error] :-1:-1: Premature end of file. Any suggestions - or maybe I have missunderstood your statement above... (I think it is in this way harmless... but I' a little bit careful as It appears now every time...) Greetings Claus View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976121#3976121 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976121

19 years, 7 months

1
0
0 / 0

[JBoss Seam] - Issues with JBoss Application Server

by jpemmasani

Hi, I am very new to JBOSS. I have created war file and deployed in jboss-4.0.2. Once I deployed I am not seeing any where the exapandable directory of the war file and also I could not find the application log file. I really appreciate all the help. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976119#3976119 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976119

19 years, 7 months

1
0
0 / 0

[JBossWS] - Re: How do I logout on a JSR 181 endpoint?

by sappenin

Ok, I solved my problem. As it turns out, I had a bug in my code on the Flex side that was adding a WSSE header every time I logged out/logged in (but never removing the headers, and re-using the WebService object used to make calls to the JBossWS). So, while I did have the new credentials to login as, I still had the old credentials in the Webservice object, which were getting passed to JBoss. So, after correcting for this error on my part, I can now send multiple WS requests as different users without shutting down my browser, exiting the Flash client, or "invalidating" anything on the server side. Apparently, all JbossWS calls are stateless. (Ahem). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976118#3976118 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976118

19 years, 7 months

1
0
0 / 0

[JBossCache] - Re: PojoCacheMBean getObject(fqn); throws java.lang.Ille

by sting_hz

Hi Brian , Thank you very much! The error is because I also copied and overided the jboss-j2ee.jar to the /server/all/lib. Now it runs! :) Steven View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976117#3976117 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976117

19 years, 7 months

1
0
0 / 0

[JBossCache] - Re: PojoCacheMBean getObject(fqn); throws java.lang.Ille

by bstansberry＠jboss.com

Well, the line numbers in your stack trace above are from a 4.0.3 version of jboss-jmx.jar, not the 4.0.4.GA version. So, there's any extra copy of that jar somewhere. Perhaps you copied it to server/all/lib? The only thing to do to upgrade 4.0.4.GA to use JBC 1.4.0.SP1 is to replace jboss-cache.jar in server/all/lib. If you put any other jars from the JBC distribution on the classpath anywhere, you should undo that change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976113#3976113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976113

19 years, 7 months

1
0
0 / 0

[JBossWS] - Re: How do I logout on a JSR 181 endpoint?

by sappenin

Ok, so I recognize that while using BASIC auth, the browser controls the login session, and nothing on the server side can logout a "BASIC" authenticated client. Just FYI, I'm calling a JBoss webservice from an Adobe FLEX Flash application running in the browser. So, I turned BASIC auth OFF on my webservices EJB endpoint, and am now using WSSE UsernameToken to authenticate the Flash client to my JSR 181 EJB endpoint. However, for whatever reason, if I make some WS calls as User A, then make some WS calls as User B (essentially, changing the WSSE username/password tokens), Jboss still thinks I'm user A. I did some digging on my JBoss server (DEBUG mode), and noticed that the WSSE client calls are happening via Http POST. Since my username is being "remembered" by the JBoss server, there must be some sort of session getting established? (This seems to be functioning a lot like FORM-based authentication). In a typical servlet, I could simply "logout" by invalidating the session. HOW does one do that with an EJB? I don't see anyway to get access to the Session....so I don't know how to invalidate it. Any ideas? Thanks! David View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976111#3976111 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976111

19 years, 7 months

1
0
0 / 0

[Tomcat, HTTPD, Servlets & JSP] - Re: Struts Mystery

by shadowrunner

NM. It was a problem with my form validation. Doh!!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976110#3976110 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976110

19 years, 7 months

1
0
0 / 0

[Persistence, JBoss/CMP, Hibernate, Database] - Re: Entity beans not autodeployed : javax.ejb.EJBException:

by ALRubinger

In my case, the error was due to a change in the build process. a "persistence.xml" file found its way into the JAR containing one of my services, and therefor this service was injecting the wrong persistence unit, leading to the errors above. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976109#3976109 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976109

19 years, 7 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-user October 2006