[EJB 3.0] - Server restart
by artur.chyzy
Hello.
I'm not sure if this is the right place for my question but i take a shot.
I'm developing app in JBoss Seam but i think it not regarding to Seam.
I want to know is it possible to not restart server (JBoss AS) when changing some ejb3 beans deployed in jar file (which is in ear exactly) and make new version of them to work
Each time i change the EJB3 class restart of app is needed... all beans are reloaded from scratch.. my app has a lot of beans and restart takes about 2 minutes so it is too long for developement... is it possible to reload only changed beans ??
Maybe there are some plans to make this to work ??
Artur
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082878#4082878
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082878
18 years, 7 months
[JBoss Seam] - LazyInitialization and ScopeType.SESSION question
by pwoj
Let's say I have entity class that is also seam component named "account":
@Scope(ScopeType.SESSION)
| @Name("account")
| @Entity
| public class Account implements Serializable{
| private Long id;
| private Collection<Operation> operations;
| ...
| }
During log in operation I read user account object from db and outjected under name "currentAccount":
@Name("authenticator")
| public class Authenticator {
|
| @Out(required=false, scope=ScopeType.SESSION, value="currentAccount")
| private Account account;
|
| public boolean authenticate() {
| account = getUserAccountFromDB();
| }
| ...
|
| }
Now I want to use currentAccount object in diffrent manager(plain pojo), for instance:
| @Name("someManager")
| public class SomeManager () {
| @In Account currentAccount;
|
| public void doSth() {
| for (Operation operation:currentAccount.getOperations()) {
| log.debug(operation);
| }
| }
| }
And now currentAccount.getOperations() will cause org.hibernate.LazyInitializationException the same if I try use use sth like #{currentAccount.operations} directly in view.
I came across :
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85964
where Gavin King posted that It's neccesary to reattach detached object (scoped SESSION) using session.lock() to make it valid to conversation context.
And now my qustions:
1. Do I really have to do this "reattach" in every bean that uses SESSION scoped seam components?
2. If I use many views that displays SESSION scoped objects (complex lazy initialization) I have to make them EAGER ??? (imagine there is outjection at the begginig and then only views that uses SESSION scoped components - no other beans)
3. Why @In does not make this "attach" automatically?
I'm just at the begging of seam developing process and maybe I miss some important point? ;)
Many thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082876#4082876
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082876
18 years, 7 months
[Installation, Configuration & DEPLOYMENT] - Problem with Jboss(Tomcat) caching from my file system
by Boris_Br
Hello,
execuse my it is the repeat of former message, because I forget to activate "notify me when a reply is posted".
I have a problem with Jboss or Tomcat chaching.
I use Jboss 4.0.5, Windows, IE 7.
Here is a part of my code in JSP:
response.setHeader("Expires", "0");
response.setHeader("Cache-Control", "no-store, no-cache, must-revalidate");
// Set IE extended HTTP/1.1 no-cache headers (use addHeader).
response.addHeader("Cache-Control", "post-check=0, pre-check=0");
response.setHeader("Pragma", "No-cache");
response.setDateHeader("Expires", 0);
...
..
I use frames in my JSP-Page and in this frame
I show some files e.g.
jboss-4.0.5.GA\server\default\deploy\appl.ear\appl.war\docs1\1001.html.
My application change the content from this file, but if I click to refresh (F5) Internet Explorer show me sometimes the old version of file 1001.html also after 3-5 sec. . Although I send every time new URL because I have UUID in my URL and it looks like that
URL: /appl/docs1/1001.html?dsessionId=4B4F042B3CCD78F6DC4A5381FBA09D2E&Uuid=b87bfcc6-efc6-4198-b75d-24f1e0029f57
It looks like Jboss or Tomcat have some cache for my file system and don't load the actuall file from the driver, but I don't now how can I configure this cache.
Can somebody help me? Thank you.
By
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082875#4082875
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082875
18 years, 7 months
[Installation, Configuration & DEPLOYMENT] - Problem with Jboss(Tomcat) caching from my file system
by Boris_Br
Hello,
I have a problem with Jboss or Tomcat chaching.
I use Jboss 4.0.5, Windows, IE 7.
Here is a part of my code in JSP:
response.setHeader("Expires", "0");
response.setHeader("Cache-Control", "no-store, no-cache, must-revalidate");
// Set IE extended HTTP/1.1 no-cache headers (use addHeader).
response.addHeader("Cache-Control", "post-check=0, pre-check=0");
response.setHeader("Pragma", "No-cache");
response.setDateHeader("Expires", 0);
...
..
I use frames in my JSP-Page and in this frame
I show some files e.g.
jboss-4.0.5.GA\server\default\deploy\appl.ear\appl.war\docs1\1001.html.
My application change the content from this file, but if I click to refresh (F5) Internet Explorer show me sometimes the old version of file 1001.html also after 3-5 sec. . Although I send every time new URL because I have UUID in my URL and it looks like that
URL: /appl/docs1/1001.html?dsessionId=4B4F042B3CCD78F6DC4A5381FBA09D2E&Uuid=b87bfcc6-efc6-4198-b75d-24f1e0029f57
It looks like Jboss or Tomcat have some cache for my file system and don't take the actuall file from the driver, but I don't now how can I configure this cache.
Can somebody help me? Thank you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082872#4082872
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082872
18 years, 7 months
[JBossCache] - Problem with Jboss(Tomcat) caching from my file system
by Boris_Br
Hello,
I have a problem with Jboss or Tomcat chaching.
I use Jboss 4.0.5, Windows, IE 7.
Here is a part of my code in JSP:
response.setHeader("Expires", "0");
response.setHeader("Cache-Control", "no-store, no-cache, must-revalidate");
// Set IE extended HTTP/1.1 no-cache headers (use addHeader).
response.addHeader("Cache-Control", "post-check=0, pre-check=0");
response.setHeader("Pragma", "No-cache");
response.setDateHeader("Expires", 0);
...
..
I use frames in my JSP-Page and in this frame
I show some files e.g.
jboss-4.0.5.GA\server\default\deploy\appl.ear\appl.war\docs1\1001.html.
My application change the content from this file, but if I click to refresh (F5) Internet Explorer show me sometimes the old version of file 1001.html also after 3-5 sec. . Although I send every time new URL because I have UUID in my URL and it looks like that
URL: /appl/docs1/1001.html?dsessionId=4B4F042B3CCD78F6DC4A5381FBA09D2E&Uuid=b87bfcc6-efc6-4198-b75d-24f1e0029f57
It looks like Jboss or Tomcat have some cache for my file system and don't take the actuall file from the driver, but I don't now how can I configure this cache.
Can somebody help me? Thank you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082871#4082871
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082871
18 years, 7 months
[Tomcat, HTTPD, Servlets & JSP] - Problem with Jboss(Tomcat) caching from my file system
by Boris_Br
Hello,
I have a problem with Jboss or Tomcat chaching.
I use Jboss 4.0.5, Windows, IE 7.
Here is a part of my code in JSP:
response.setHeader("Expires", "0");
response.setHeader("Cache-Control", "no-store, no-cache, must-revalidate");
// Set IE extended HTTP/1.1 no-cache headers (use addHeader).
response.addHeader("Cache-Control", "post-check=0, pre-check=0");
response.setHeader("Pragma", "No-cache");
response.setDateHeader("Expires", 0);
...
..
I use frames in my JSP-Page and in this frame
I show some files e.g.
jboss-4.0.5.GA\server\default\deploy\appl.ear\appl.war\docs1\1001.html.
My application change the content from this file, but if I click to refresh (F5) Internet Explorer show me sometimes the old version of file 1001.html also after 3-5 sec. . Although I send every time new URL because I have UUID in my URL and it looks like that
URL: /appl/docs1/1001.html?dsessionId=4B4F042B3CCD78F6DC4A5381FBA09D2E&Uuid=b87bfcc6-efc6-4198-b75d-24f1e0029f57
It looks like Jboss or Tomcat have some cache for my file system and don't take the actuall file from the driver, but I don't now how can I configure this cache.
Can somebody help me? Thank you.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082870#4082870
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082870
18 years, 7 months
[JBoss Messaging] - 1.4.0.CR2 - Temporary Destinations - Cluster
by aslak
When creating a Temporary destination on a clustered PostOffice,
the temp destination itself is clustered but..
Both nodes in the cluster fail adding a MessageSucker to the temp destination due to a SecurityException.
The node that received the message continues processing it like nothing happened.
1.
Shouldn't the MessageSucker inherit the connections credentials,
or bypass normal security all together being an internal service?
2.
Shouldn't this fail back to the client,
notifying him that we have failed to guaranty his response?
-aslak-
| 09:19:47,094 ERROR [ClusterConnectionManager] Failed to process notification
| javax.jms.JMSSecurityException: User: null is not authorized to read from destination f-3v0q2g6f-1-7izp2g6f-jo1e7e-273333a
| at org.jboss.jms.server.container.SecurityAspect.check(SecurityAspect.java:312)
| at org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect.java:112)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java)
| at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.createConsumerDelegate(SessionAdvised.java)
| at org.jboss.jms.wireformat.SessionCreateConsumerDelegateRequest.serverInvoke(SessionCreateConsumerDelegateRequest.java:100)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
| at org.jboss.remoting.Client.invoke(Client.java:1634)
| at org.jboss.remoting.Client.invoke(Client.java:548)
| at org.jboss.remoting.Client.invoke(Client.java:536)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$createConsumerDelegate$aop(ClientSessionDelegate.java:231)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_8721389917985689973.invokeNext(ClientSessionDelegate$createConsumerDelegate_8721389917985689973.java)
| at org.jboss.jms.client.container.StateCreationAspect.handleCreateConsumerDelegate(StateCreationAspect.java:148)
| at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect67.invoke(StateCreationAspect67.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_8721389917985689973.invokeNext(ClientSessionDelegate$createConsumerDelegate_8721389917985689973.java)
| at org.jboss.jms.client.container.ConsumerAspect.handleCreateConsumerDelegate(ConsumerAspect.java:68)
| at org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect66.invoke(ConsumerAspect66.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_8721389917985689973.invokeNext(ClientSessionDelegate$createConsumerDelegate_8721389917985689973.java)
| at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_8721389917985689973.invokeNext(ClientSessionDelegate$createConsumerDelegate_8721389917985689973.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_8721389917985689973.invokeNext(ClientSessionDelegate$createConsumerDelegate_8721389917985689973.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.createConsumerDelegate(ClientSessionDelegate.java)
| at org.jboss.messaging.core.impl.clusterconnection.MessageSucker.start(MessageSucker.java:154)
| at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.createSucker(ClusterConnectionManager.java:471)
| at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.notify(ClusterConnectionManager.java:329)
| at org.jboss.messaging.core.impl.DefaultClusterNotifier.sendNotification(DefaultClusterNotifier.java:72)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBindingInMemory(MessagingPostOffice.java:2366)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.internalAddBinding(MessagingPostOffice.java:1790)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBindingFromCluster(MessagingPostOffice.java:995)
| at org.jboss.messaging.core.impl.postoffice.BindRequest.execute(BindRequest.java:55)
| at org.jboss.messaging.core.impl.postoffice.GroupMember$ControlRequestHandler.handle(GroupMember.java:620)
| at org.jgroups.blocks.MessageDispatcher.handle(MessageDispatcher.java:610)
| at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:654)
| at org.jgroups.blocks.RequestCorrelator.access$200(RequestCorrelator.java:40)
| at org.jgroups.blocks.RequestCorrelator$Request.run(RequestCorrelator.java:944)
| at org.jgroups.util.ReusableThread.run(ReusableThread.java:234)
| at java.lang.Thread.run(Thread.java:619)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082869#4082869
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082869
18 years, 7 months
[EJB 3.0] - Re: Issues with EJB 3.0/ JBoss 4.0.5
by jaikiran
anonymous wrote : Thanks jaikiran, you remember last thursday you helped me solve the authentication issue.
Ahh... I remember now :) I was sure i had heard about a similar setup, as yours, but wasnt able to recollect where.
"avthosar" wrote : So how can I find out the version?
|
|
If you have access to the server folders, you can look in the MANIFEST.MF file which is present in %JBOSS_HOME%/lib/jboss-system.jar/META-INF folder. It will contain a "Implementation-Version" which mentions the version of JBoss. For my installation of 4.0.5, it shows this:
anonymous wrote : Manifest-Version: 1.0
| Ant-Version: Apache Ant 1.6.2
| Created-By: 1.4.2_09-b05 (Sun Microsystems Inc.)
| Specification-Title: JBoss
| Specification-Version: 4.0.5.GA
| Specification-Vendor: JBoss (http://www.jboss.org/)
| Implementation-Title: JBoss [Zion]
| Implementation-URL: http://www.jboss.org/
| Implementation-Version: 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610
| 162339)
| Implementation-Vendor: JBoss Inc.
| Implementation-Vendor-Id: http://www.jboss.org/
Check what your server installation contains.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4082868#4082868
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4082868
18 years, 7 months