kpandey, what exactly did you change?
We are having trouble to connect to the JBoss JVM running on Linux. I
investigated http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6209663
but changes to /etc/hosts didn't help.
I tried to set in run.conf
JAVA_OPTS="$JAVA_OPTS -Djboss.bind.address=LOCALIP"
I get the same exception. I suppose it has a root cause, which is a cycle in
page-redirection. But I wonder why the root-cause is not logged.
As you can draw from the stacktrace, we are using Icefaces (1.6.1).
Btw., the ApplicationUser-class is not the problem.
2008-01-18 09:51:02,984 ERROR
[com
But why does this not work for a WAR-archive?
I can successfully query the war-deployment on JMX via JMX Agent View.
However, when I add this to the depends-list like
|
jboss.management.local:J2EEApplication=app.ear,J2EEServer=Local,j2eeType=WebModule,name=web.war
|
then the SAR is never
We are binding an LDAP-server into the JNDI-context.
It works properly until redeployment.
After redeployment the connection is lost and no new connection is being
established.
How to specify to auto-reconnect after connection was lost??
|
| external/ldap/acme
|
"jaikiran" wrote : See this
http://wiki.jboss.org/wiki/Wiki.jsp?page=HowCanAnMBeanDependOnASessionBean
Excellent! Ty.
That's much better than starting a thread in the MBean to wait for the
EJB-archive to finish deployment!
View the original post :
http://www.jboss.com/index.html?module=bb&op=v
I fixed it and the sar is deployed successfully.
Now how can I change the order the archives are deployed without modifying the
global URLDeploymentScanner defined in conf/jboss-server.xml ?
The problem is that the SAR depends on the deployed EJB-archive.
I suppose I need some declaration, but
Now I get a CNF, even thou the class is existing the sar-archive:
Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for:
pkg.ImportStartupService
| at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:306)
| at
org.jboss.mx.loading.RepositoryClassLoa
ty, that's not mentioned in the JBoss-docs and neither in the
HelloWorld-example.
My MBean definition looks like this:
so what exactly is required in the tag ?
both "importStartupService" and "myservice.sar" (name of the folder of the
exploded sar directly under the ear-folder) appear not to
I have a simple service.sar residing redirectly in myapp.ear.
The sar is not being deployed and I don't understand why.
I cannot even find an exception in log-file.
Any hint?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118238#4118238
Reply to the post :
"[EMAIL PROTECTED]" wrote : 22 times over what period? Where is it defined it
should be called once?
over the period of one HTTP-request.
I have no idea what might be the purpose of injecting a static value (like a
request parameter) more than once into the component.
Maybe there is something wr
hello Seam architects
I have a session-scoped SFSB with a method annotated like this:
@RequestParameter("orderNumber")
The method is being called properly.
But why is it called 22 times? What is the purpose of calling it multiple times?
According to its defined purpose, it should be called onc
| @DataModelSelection
| Item item
|
| @Create
| init() {
|item = new Item(1);
| }
The item-variable appears to get overwritten by Seam with the first item of the
@DataModel-annotated list. How to define a particular initial item?
View the original post :
http://www.jboss.co
ty for this insight
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103563#4103563
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103563
___
jboss-user mailing list
jboss-user@
cross-post from http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103434
Has anybody successfully retrieved SFSB-instances on a web-deployment via JNDI?
We fail with this (see above thread for details)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103
"ALRubinger" wrote :
| Try again with doing one lookup, placing that stub in the HttpSession, and
paste your code if you're still having problems?
|
| S,
| ALR
I followed your advise and implemented a filter to retrieve the SFSB-proxy once
the HTTP-session is created:
public void doFi
"waynebaylor" wrote : when you save the sfsb are you using the same attribute
name for all clients?
yes, I used the same string for saving the SFSB-instance in the HTTP-session.
This is the job of the web-container to seperate web-sessions against each
other and should not be involved in this pr
ty for your input.
yes, now I look up the SFSB with every HTTP-request.
Before I tried looking it up once and and then having save the instance in
HTTP-session, just like you suggest.
However, the result does not differ as in both cases the instance acquired on
the web-tier/WAR-deployment is not
We continue having trouble to acquire correct SFLB-instance to the
web-deployment (in an EAR on JBoss 4.2.1). It appears the web-session is not
identical with the client-session on the EJB-tier, hence JNDI delivers a new
instance of that SFLB instead of the one already assigned to this user.
be
ty. yes, Icefaces also supports the requiredMessage attribute.
Practically, this means that the error-message needs to be specified twice,
once in the bean-annotation, and second in the JSF-component requiredMessage
attribute.
How to sell this as an effective and innovative software design? ...
Following the Seam-manual we are experiencing trouble to get validation running
with Seam 2.0.CR2/Icefaces 1.6.1
JSF:
|
|
|
Bean-class:
@NotNull
| @Pattern(regex="^[a-zA-Z.-]+", message="Fehlender oder ungültiger Nachname")
| @Override
| public String getFirstName() {
| re
"nickarls" wrote : Could there be a non-required outjection somewhere that
could overwrite it before the call?
The applicationUser is @Out-jected only once, that is in the authenticator
class, which has EVENT-scope and should not be called.
@Name("authenticator")
| @Scope(ScopeType.EVENT)
|
a few debug lines before the error occurs, Seam logs
DEBUG [org.jboss.seam.Component] trying to inject with hierarchical context
search: applicationUser
| DEBUG [org.jboss.seam.contexts.Contexts] found in session context:
applicationUser
Unfortunely the message doesn't refer to the component
thanks for your input.
the component declaration surely doesn't need to be an interface.
I added @Name("applicationUser") to my ApplicationUser class, but still it is
not being injected. And anyway, the component "applicationUser" IS in fact
existing in the Seam session-ctx (according to Seam de
in one particular case the @In annotation is not working here.
| @Stateful
| @Name("shopTree")
| @Scope(ScopeType.SESSION)
| public class ShopTreeBean implements ShopTree {
| @In
| private ApplicationUser applicationUser; <-- ALWAYS NULL
|
I have verified that Application
We need a custom servlet that is completely independent from the application.
The problem ist that the Seam-filter is configured to intervene in every
request:
|
| Seam Filter
| /*
|
What is best practise to make the Seam-filter ignoring a certain pattern?
Vie
We get an exception after not using the JNDI-connection for a few minutes:
javax.naming.CommunicationException: connection closed [Root exception is
java.io.IOException: connection closed];
|
How can I instruct the MBean to reconnect automatically?
|
| external/ldap/swm
|
"icruz" wrote : Hello,
|
| ... and when I try to create the timer it fails with a "duplicate key"
exception from MySQL driver
|
| Thanks in advance,
| Isaac
I wonder where in the JMX-console could you cancel the timer??
I was unable to find it.
View the original post :
http://www.j
Since I did not yet figure out how to change the Timer persistencePolicy, all
(frequent) Timer's ever started on this AS-instance continue to run again and
again.
How is possible to cancel Timers using web-console or twiddle-tool?
View the original post :
http://www.jboss.com/index.html?mod
ty, it was the SCOPE indeed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095891#4095891
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095891
___
jboss-user mailing list
jb
I am struggling a little bit with the logic of the Seam context.
Currently we get "RequiredException: @In attribute requires non-null value"
messages after the user has logged in.
Requirement:
on authentication, an ApplicationUser object should be made available to
Seam-context for later usage.
We simply want JBoss/logj to use WARNING as the threshold.
This is the default config in conf/jboss-log4j.xml and we did not even touched
it. (see below)
Yet we get countless DEBUG-messages from all kinds of categories in the
server.log !
How comes? We don't have any additional logging-config-fi
AS 4.2.1 appears to not use TimerServiceImpl anymore, but
org.jboss.ejb3.timerservice.jboss.TimerServiceFacade instead, which doesn't
offer any setters for the persistencePolicy.
Chapter 10.8 from the Guide also doesn't mention the persistencePolicy.
Is it possible to configure the MBean org.jb
YES, it is a classical classloader problem.
I was putting the class mypgk.ImportManager not only in the ejb.jar, but also
in mywar.war/WEB-INF/lib.
After removing the class from WEB-INF/lib, no ClassCastException anymore.
I am fully aware of the type-incompatibility when loaded from different
c
"jaikiran" wrote :
| Try this:
|
| context.lookup("java:comp/env/ejb/ImportManagerBean");
thanks for the hint. using the absolute JNDI-path
"java:comp/env/ejb/ImportManager" I am getting the same proxy-instance like
with "kportal/ImportManagerBean/local"
This proxy is not type-compatibl
there was a typo in web.xml. It should look like this:
ejb/ImportManagerBean
Session
mypkg.ImportManager
mypkg.ImportManager
ImportManager
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093914#4093914
Reply to the post :
http://www.jboss.com/inde
I am still having trouble to resolve the SLSB on the web-client (running on the
same VM inside the same EAR on AS 4.2.1):
jboss-web.xml
ejb/ImportManagerBean
ImportManager
web.xml
ejb/ImportManagerBean
The location of persistence.xml is specified by the JPA standard, so - AFAIK -
it is impossible to specify another location.
However, you are always free to deploy your archives in exploded form. Then you
can easily edit the persistence.xml and redeploy the corresponding jar.
View the origina
We have an EAR deployed on AS 4.2.1
In the webapp (war-archive), we need to access an SLSB (EJB3).
MyBeanLocal bean = (MyBeanLocal) context.lookup("java:comp/env/ejb");
But this context is not existing! How comes?
We can access the Bean-proxy using JNDI-path "myapp/MyBean/local", but this
obje
I understand that due to JBoss' sophisticated class-loading system it's not
possible to hot-deploy single classes like it is possible e. g. in tomcat.
However, even when I touch the ejb-jar.xml, the EJB-archive is not reployed.
touch
jboss-4.2.1.GA/server/default/deploy/kportal.ear/kportal.jar/
I have no idea how you happen to have the NT-Login-name available in the
session. In our configuration the NT-Login is passed as an attribute of the
HTTP-request (and availble via request.getRemoteUser()).
I am using Seam 2 and I have added the authentication logic in my annotaded
authenticatio
We need also NTLM authentication and the configuration is quite apparent.
However to me is not clear how to obtain the HTTP-request-headers from my
authenticator.autenthicate() EJB3 bean-method in order to call
request.getRemoteUser().
Seam provides Annotation for @RequestParameter, but I don't
I could not find any architecture whitepaper explaining how JBossWS 2.0 is
built. Anybody has a link?
I am trying to figure out whether HTTP 1.1 DIGEST authentication is supported
by JBossWS 2.0 on the client side. I could not find any hint in the user manual
nor in the Wiki. The FAQ has one li
I tried now to run generate-entities using Seam 1.2.1.
Surprisingly here is the same result.
connection pool is initialized and immediately destroyed without having any
code generated.
I see from Ant-debug-output that the JDBC-driver is delivering some result-set,
but either it doesnt find anythi
I am experiencing the same problem with 2.0.0.beta1. seam generate-entities
runs thru without any exception but is not generating anything. The driver is
loaded and hbm2java is being configured, but the actual code generation is not
being triggered.
Anybody has found out the problem?
View th
'seam generate-entities' is not generating anything using Seam 2.0.0.BETA1.
The task is running thru without any exceptions, the JDBC driver is recognized,
build.properties is read properly. But it seems the database (MSSQL) is not
even being connected.
Anybody having an idea?
View the origina
Where can I find instructions how to build the sar that contains a tomcat6
distrubution?
thanks.
Marc
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077264#4077264
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=407726
46 matches
Mail list logo
