[Installation, Configuration & Deployment] - Startup errors on Ubuntu, can't access localhost:8080
by rup
I installed jboss on Ubuntu 6.06 LTS -Dapper Drake, using jems-installer-1.2.0.GA.jar. I have jdk1.6.0 in /usr/lib/jvm. Starting jboss using run.sh gives me the following errors, under four headings. I am posting the relevant portions of the error log. Can somebody tell me how to solve this problem?
------------------------------------------------------------------------------------------------------------
Packages waiting for a deployer
http-invoker.sar/invoker.war/
jbossws14.sar/jbossws-context.war
jms/jbossmq-httpil.sar/jbossmq-httpil.war/
management/console-mgr.sar/web-console.war/
jmx-console.war/
Incompletely deployed packages
jmx-console.war/
MBeans waiting for other MBeans
ObjectName: jboss.web:service=WebServer
ObjectName: jboss.ws:service=WebServiceDeployerJSE
ObjectName: jboss.ws:service=DeployerInterceptorNestedJSE
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
ObjectName: jboss.cache:service=TomcatClusteringCache
ObjectName: jboss:service=DefaultPartition
ObjectName: jboss.ha:service=HASingletonDeployer
ObjectName: jboss:service=FarmMember,partition=DefaultPartition
MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM
ObjectName: jboss.cache:service=TomcatClusteringCache
ObjectName: jboss:service=DefaultPartition
------------------------------------------------------------------------------------------------------------
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026664#4026664
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026664
19Â years, 1Â month
[EJB/JBoss] - Just a question
by tinico
Hello all, sorry for my english, I'm french !!
I've a comprehension problem !
I had a problem to find an EJB from a web application. To find it I made :
| Context ctx = new InitialContext();
| EjbExemple home = (EjbExempleHome)PortableRemoteObject.narrow( ctx.lookup(?ejbname?), EjbExempleHome.class );
| ejb = home.create();
|
This lines works only if my client is a simple jsp. If my client was my web application, this don't work. I've solve thi problem with this lines :
| properties = new Properties();
| properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
| properties.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
| properties.put(Context.PROVIDER_URL, "localhost:1099");
|
So, I find my EJB with :
Context ctx = new InitialContext(properties);
And it work !
My EJB interact with an Oracle database, so I ahve to find the connection with EJB. To do that, I use :
Context ic = new InitialContext();
| ds = (DataSource) ic.lookup(?connectionname?);
It Work !!! Without properties !
So, here, my question :
Why the jsp work without context properties whereas my web app need it ?
And, Why I don't need the context properties to find my connection whereas I need it to find EJB ??
My application work, but, it's a question which I would like to have the answer.
Thx
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026663#4026663
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026663
19Â years, 1Â month
[Security & JAAS/JBoss] - Insufficient permissions
by luker74
Hi all, i've got this message on jboss 3.2.8sp1:
Insufficient method permissions, principal=null, ejbName=UserAdmin, method=create, interface=LOCALHOME, requiredRoles=[ruolo1], principalRoles=[]
I'm trying to access a local ejb from a struts action servlet made by me.
I put this line in jboss.xml file :
<security-domain>java:/jaas/storename</security-domain>
then this is my jboss-web.xml file:
<jboss-web>
<security-domain>java:/jaas/storename</security-domain>
<ejb-local-ref>
<ejb-ref-name>ejb/UserAdmin</ejb-ref-name>
<jndi-name>storename/UserAdmin</jndi-name>
</ejb-local-ref>
</jboss-web>
and this is the ejb-jar.xml:
<ejb-jar>
....
<display-name>Name for UserAdmin</display-name>
<ejb-name>UserAdmin</ejb-name>
<local-home>it.ausystems.progettoejb.interfaces.UserAdminLocalHome</local-home>
it.ausystems.progettoejb.interfaces.UserAdminLocal
<ejb-class>it.ausystems.progettoejb.ejb.UserAdminCMP</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
False
<cmp-version>2.x</cmp-version>
<abstract-schema-name>UserAdmin</abstract-schema-name>
<cmp-field >
<field-name>username</field-name>
</cmp-field>
<cmp-field >
<field-name>passwd</field-name>
</cmp-field>
<primkey-field>username</primkey-field>
<security-role-ref>
<role-name>ruolo1</role-name>
<role-link>ruolo1</role-link>
</security-role-ref>
<security-identity>
<run-as>
<role-name>ruolo1</role-name>
</run-as>
</security-identity>
<query-method>
<method-name>findByPrimaryKey</method-name>
<method-params>
<method-param>java.lang.String</method-param>
</method-params>
</query-method>
<ejb-ql/>
<!-- Write a file named ejb-finders-UserAdmin.xml if you want to define extra finders. -->
....
<assembly-descriptor>
<security-role>
<role-name>ruolo1</role-name>
</security-role>
<!-- method permissions -->
<!--
To specify additional method-permission elements, add a file in the merge
directory called ejb-method-permissions.ent that contains them.
-->
<method-permission >
<role-name>ruolo1</role-name>
<ejb-name>UserAdmin</ejb-name>
<method-name>*</method-name>
</method-permission>
</assembly-descriptor>
can anyone help me?
thanx
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026659#4026659
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026659
19Â years, 1Â month
[JBoss Messaging] - Re: Resource GC problem
by Kevin.Connerï¼ jboss.com
The following is a copy of the email I sent to our group earlier today.
Kev
-----------------------------------------------------------------------------
>From what I can see the issue appears to be related to two things
- The way the current codebase repeatedly creates connections
- The way JBoss Remoting works
One cause appears to be the timers used by remoting. From what I can
see there are three in play
- ConnectionValidator
- BisocketServerInvoker$ControlMonitorTimerTask
- LeasePinger$LeaseTimerTask
Each one of these timers has indirect access to the majority of the heap.
The big culprit in the timers appears to be LeasePinger$LeaseTimerTask.
When connections are closed this task is cancelled but unfortunately
cancelling j.u.TimerTask does *not* remove the task from the queue, all
it does is mark it as cancelled. The consequence of this is that every
instance referenced by the task *cannot* be garbage collected until the
timer would normally fire (and the task is then removed from the queue).
Referenced from each LeasePinger instance is a BisocketClientInvoker
which contains a ClientSocketWrapper. Each ClientSocketWrapper
references a Socket, a DataInputStream (containing BufferedInputStream)
and a DataOutputStream (containing BufferedOutputStream). Each BIS/BOS
contains a 64k array! In my tests these instances amount to a
cumulative size of about 1/3 of the heap.
Another cause appears to be the use of hash maps. There are numerous
hashmaps referenced from BisocketServerInvoker and BisocketClientInvoker
which do not appear to be garbage collected. One reason is the above
timers but a second is that BisocketServerInvoker holds on to
BisocketServerInvoker references in a static map called
listenerIdToServerInvokerMap. This map currently contains an instance
of BisocketServerInvoker for every iteration of the loop.
This has all been discovered from examining profile information, not
source code. It may be that this analysis is completely wrong and that
examination of the source code will highlight other issues.
Kev
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026657#4026657
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026657
19Â years, 1Â month