RE: jaspi instance failes to start
by Anil Saldhana
Ignore that target for sometime. It is in flux.
________________________________
From: Jaroslaw Kijanowski
Sent: Friday, September 15, 2006 11:27 AM
To: jboss-development(a)lists.jboss.org
Cc: QA
Subject: jaspi instance failes to start
The testsuite fails while starting the "jaspi" instance in jbossas beta
5:
tests.log:
***************************
tests-security-jaspi-unit:
[echo] creating jaspi config
[copy] Copying 153 files to
/services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/j
boss-5.0.0.Beta/server/jaspi
[echo] Overwriting config descriptors
[copy] Copying 2 files to
/services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/j
boss-5.0.0.Beta/server/jaspi
[server:start] Starting server "jaspi" with command:
[server:start] /opt/jrockit-jdk1.5.0_06/bin/java -cp
/services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/j
boss-5.0.0.Beta/bin/run.jar:/opt/jrockit-jdk1.5.0_06/lib/tools.jar
org.jboss.Main -c jaspi -b localhost
BUILD FAILED
/services/cruisecontrol/checkout/jboss-head-testsuite-1.5/testsuite/buil
d.xml:827: The following error occurred while executing this line:
/services/cruisecontrol/checkout/jboss-head-testsuite-1.5/testsuite/buil
d.xml:2414: Error starting server "jaspi": Server failed to start; see
logs.
**************************
The server.log contains this:
**************************
11:25:01,556 ERROR [AbstractKernelController] Error installing to
Configured: name=jboss.web:service=WebServer state=Instantiated
mode=Manual requiredState=Configured
org.jboss.deployment.DeploymentException: No Attribute found with name:
AuthorizationManagerService for jboss.web:service=WebServer
at
org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:
129)
**************************
AuthorizationManager isn't present in the following files (should be?):
jbossweb-tomcat6.sar\META-INF\webserver-xmbean.xml
\trunk\tomcat\src\main\org\jboss\web\tomcat\tc6\Tomcat6.java
\trunk\tomcat\src\main\org\jboss\web\tomcat\tc6\Tomcat6MBean.java
\trunk\tomcat\src\main\org\jboss\web\tomcat\tc6\TomcatDeployer.java
but is still present in
jbossweb-tomcat6.sar\META-INF\jboss-service.xml
To start the server (jaspi instance) successfully, it's enough to delete
following section in jbossweb-tomcat6.sar\META-INF\jboss-service.xml:
<depends optional-attribute-name="AuthorizationManagerService"
proxy-type="attribute">jboss.security:service=AuthorizationManager
</depends>
The other way is to add following lines to
jbossweb-tomcat6.sar\META-INF\webserver-xmbean.xml:
<attribute access="write-only">
<name>AuthorizationManagerService</name>
<type>org.jboss.security.plugins.AuthorizationManagerServiceMBean</type>
</attribute>
What is the right way to get the testsuite successfully run the
jaspi-instance?
19 years, 7 months
jaspi instance failes to start
by Jaroslaw Kijanowski
The testsuite fails while starting the "jaspi" instance in jbossas beta 5:
tests.log:
***************************
tests-security-jaspi-unit:
[echo] creating jaspi config
[copy] Copying 153 files to /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/jboss-5.0.0.Beta/server/jaspi
[echo] Overwriting config descriptors
[copy] Copying 2 files to /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/jboss-5.0.0.Beta/server/jaspi
[server:start] Starting server "jaspi" with command:
[server:start] /opt/jrockit-jdk1.5.0_06/bin/java -cp /services/cruisecontrol/checkout/jboss-head-testsuite-1.5/build/output/jboss-5.0.0.Beta/bin/run.jar:/opt/jrockit-jdk1.5.0_06/lib/tools.jar org.jboss.Main -c jaspi -b localhost
BUILD FAILED
/services/cruisecontrol/checkout/jboss-head-testsuite-1.5/testsuite/build.xml:827: The following error occurred while executing this line:
/services/cruisecontrol/checkout/jboss-head-testsuite-1.5/testsuite/build.xml:2414: Error starting server "jaspi": Server failed to start; see logs.
**************************
The server.log contains this:
**************************
11:25:01,556 ERROR [AbstractKernelController] Error installing to Configured: name=jboss.web:service=WebServer state=Instantiated mode=Manual requiredState=Configured
org.jboss.deployment.DeploymentException: No Attribute found with name: AuthorizationManagerService for jboss.web:service=WebServer
at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:129)
**************************
AuthorizationManager isn't present in the following files (should be?):
jbossweb-tomcat6.sar\META-INF\webserver-xmbean.xml
\trunk\tomcat\src\main\org\jboss\web\tomcat\tc6\Tomcat6.java
\trunk\tomcat\src\main\org\jboss\web\tomcat\tc6\Tomcat6MBean.java
\trunk\tomcat\src\main\org\jboss\web\tomcat\tc6\TomcatDeployer.java
but is still present in
jbossweb-tomcat6.sar\META-INF\jboss-service.xml
To start the server (jaspi instance) successfully, it's enough to delete following section in jbossweb-tomcat6.sar\META-INF\jboss-service.xml:
<depends optional-attribute-name="AuthorizationManagerService"
proxy-type="attribute">jboss.security:service=AuthorizationManager
</depends>
The other way is to add following lines to jbossweb-tomcat6.sar\META-INF\webserver-xmbean.xml:
<attribute access="write-only">
<name>AuthorizationManagerService</name>
<type>org.jboss.security.plugins.AuthorizationManagerServiceMBean</type>
</attribute>
What is the right way to get the testsuite successfully run the jaspi-instance?
19 years, 7 months
RE: Towards JBoss-4.0.5.GA
by Stan Silvert
Voting was just completed on MyFaces 1.1.4. Looks like they are really
going to release it this time.
http://www.nabble.com/-VOTE--Release-MyFaces-Core-1.1.4-t2253192.html
I've changed this one to Critical priority as I now expect MyFaces 1.1.4
to be in 4.0.5.
http://jira.jboss.com/jira/browse/JBAS-3554
Stan Silvert
JBoss, a division of RedHat
ssilvert(a)jboss.com
> -----Original Message-----
> From: Dimitris Andreadis
> Sent: Wednesday, September 13, 2006 8:28 AM
> To: 'JBoss.org development list'; The Core
> Subject: Towards JBoss-4.0.5.GA
>
> I will be trimming down the list of remaining JIRA tasks for 4.0.5.GA,
so
> if there is anything (library update, bug fix) you want to definitely
see
> into this release, please make sure it is recorded in JIRA with a
Critical
> priority.
>
> Again, the initial target date is Sep/29th, so I don't see the
jbossws-
> 1.0.4 upgrade (due end of Oct) taking place.
>
> If there is any reason you want the release delayed (e.g. we are
> discussing some EJB3 updates) let me know.
>
> If you can work on the 4.0.5.GA remaining tasks, even better ;)
>
http://jira.jboss.com/jira/secure/IssueNavigator.jspa?mode=hide&requestI
d=
> 12310181
>
> Thanks
> /Dimitris
19 years, 7 months
JBossMQ in JBoss5
by Adrian Brock
http://jira.jboss.com/jira/browse/JBAS-2156
plus some others.
JBossMQ will be a part of JBoss5.
I've already had to correct this statement on the WIKI before.
JBoss Messaging will be the default, JBossMQ will be optional
for those that need to keep using their JBossMQ configuration
within JBoss5.
We will remove support for JBossMQ once people have had time
to migrate, i.e. probably JBoss6 or maybe 7 depending upon
when JBoss6 is released.
Development of major new features for JBossMQ by JBoss
has already stopped except for those requested by paying customers,
e.g. XARecovery integration with JBossTM is the latest example.
That does not preclude development by the community.
The example above is a feature provided by the community.
JBoss.com policy towards JBossMQ should not affect this work!
--
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx
19 years, 7 months
Re: JMS tasks from jboss-4.0.5
by Adrian Brock
The only reason for not porting from JBoss5 it is a lack of testing.
I mean the WSMQ enlistment fix in the server session pool,
not the pooling parameters.
That is what JBAS-3183 was designed to do, the same tests
were also apply for the resource adapter inflow (JBAS-1434)
using the abstraction I started in org.jboss.test.messagedriven
The other part of JBAS-3183 is the isSameRM() workaround in JCA.
On Fri, 2006-09-15 at 07:44 -0400, Weston Price wrote:
> Just to clarify:
>
> The StdSessionPool/Server changes currently reside in a patch on the
> 4.0.3SP1 branch for a specific client. These changes have not been ported up
> to JBoss4.0.5CR1. I can fix the transaction branch logic in 4.0.5CR1, as
> well as the JavaDoc.
>
> I had thought that we didn't want to port the new pooling behavior (lazy
> initialization, recycling etc) given the time frame of 4.0.5CR1 and the fact
> that we really want to be focusing on the adapter moving forward.
>
> I had slated this new behavior for 4.0.6. If we want to port his for the
> next release I can do that no problem.
>
> Regards,
>
> Weston
>
>
> On 9/15/06 7:37 AM, "Adrian Brock" <adrian_brock(a)jboss.org> wrote:
>
> > On Fri, 2006-09-15 at 06:09 -0500, Dimitris Andreadis wrote:
> >> We have some 11 JMS related tasks for jboss-4.0.5 that need to be dealt
> >> with or deferred. (I believe only Weston is doing jbas-3183?)
> >>
> >> Since Adrian is buzy with JB5, can someone else (jboss-messaging maybe)
> >> help?
> >>
> >
> > I'm going to spend a couple of days on JBossMQ before 4.0.5 is released.
> > Below is a summary. Most of it should be catered for by Weston's
> > changes to the ServerSessionPool.
> >
> >> Thanks
> >>
> >> JBAS-3183 Integration with WebSphere MQ 5.x
> >
> > Weston is working on this, he knows how to fix the final part,
> > which is really a JCA issue.
> >
> >> JBAS-3597 JBAS-3437 Test error
> >> org.jboss.test.jbossmq.test.JBossMQUnitTest::testTopicSelectorChange
> >
> > I doubt this will get done.
> > I don't have time to rewrite these crappy tests for this release.
> >
> > Ideally, JBoss Messaging and JBossMQ should be sharing a testsuite
> > using the JBossAdmin abstraction I wrote when I integerated the
> > JORAM testsuite.
> >
> >> JBAS-3620 JBossMQ's PersistenceManager RecoveryRetries doesn't work if
> >> failure is creating the schema
> >
> > I will do this.
> >
> >> JBAS-3627 Write test to test rollback of a NACK in 2PC Adrian Brock
> >> Luc Texier
> >
> > This isn't very important, but I will probably do it as part of
> > the related fix that was only partially fixed in 4.0.5RC1 (JBAS-3628)
> >
> >> JBAS-3634 Acknowledgement of transacted message in MessageListener
> >> should be inside delivery lock
> >
> > I will do this.
> >
> >> JBAS-3631 Missing branch in StdServerSession commit logic
> >
> > Weston is working on this.
> >
> >> JBAS-1346 JDBC StateManager
> >
> > This won't get done, it is a feature request that keeps getting bumped.
> > We should probably remove it from the schedule.
> >
> >> JBAS-1908 listMessageCounter issue with JMS subscriptions containing
> >> certain message selector characters
> >
> > This won't get done. The original contributor of this code
> > looks to have orphaned it.
> > This should be removed from the schedule of fixes since the real "fix"
> > is JBAS-2841
> >
> >> JBAS-3468 JMS Connection starts ping thread before ClientID is set
> >> resulting in the ClientMonitorInterceptor to close the connection after
> >> client timeout
> >
> > I'll apply my suggested fix since the user's suggested patch
> > is wrong.
> >
> >> JBAS-3483 The javadoc relating to StdServerSessionPool pooling
> >> parameters is wrong
> >
> > Weston is working on this.
> >
> >> JBAS-1485 JMS ResourceAdapter makes unnecessary temporary delete
> >> requests
> >
> > This won't get done. It is a none issue that just leads to
> > a minor inefficency at session.close()
> > The fix is fairly complicated in comparison, it involves
> > wrapping/unwrapping the destination objects to keep
> > track of their state.
> > In fact, it is already fixed by the new resource adapter
> > stuff I did in the jca prototype project.
>
> --
> Weston Price
>
> Jboss/JCA
> JBoss, a division of RedHat
>
> Telephone: 1-(603) 397-0359
> Skype: wmprice1240
> AIM: wmprice1240
> YIM: weston_p
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx
19 years, 7 months
